iso does not exist

And I am on a 64-bit system. I also created a ~/tmp folder.

The ISO image needs to be accessible by root in order to loopback mount it, which is necessary so files can be extracted from the ISO.

There are at least two known scenarios where this fails - one is encrypted directories and the other one is NFS mounted file systems.

Can you please verify that a comand like "sudo mount -o loop /home/alien/Music/ubuntu-10.04.1-desktop-amd64.iso /mnt" works as expected?

Thank you, Wolf
   Here's what I get running sudo mount -o loop /home/alien/Music/ubuntu-10.04.1-desktop-amd64.iso /mnt in a terminal:

mount: according to mtab /home/alien/Music/ubuntu-10.04.1-desktop-amd64.iso is already mounted on /mnt as loop

   I didn't encrypt my /home or any other directories as far as I know. I'm not sure about NFS. I don't use it, and a quick search of Synaptic for NFS shows the following programs as being installed:

liblockfile1
manpages (this is the general manpages installation, not just NFS)

and some other general utilities.

Any other information I can provide, let me know.

Chris

I assume the message from the mount command comes from executing the command twice - usually there should not be any output (except, maybe, that the filesystem was mounted readonly). -- Make sure you "sudo umount /mnt" again before you continue.

From what I understand the problem must be in the system UCK runs on, so could you please provide the release and
kernel architecture of your host system (e.g. something like Kubuntu Lucid on x86_64)?

Another useful thing would be to run the offending command (i.e. zenity from the looks of it) from a command line like in
       zenity --info --text "hello world"
and report, whether this shows the error.

Another information that could be useful to isolate the error: Which kind of shell are you running, i.e. do an "ls -l /bin/sh" and an "ls -l /bin/bash" and report the output, please.

And finally: could you please run "uck-gui" directly from the command line - maybe there is some useful information there that gets thrown away when you run the GUI from the application menu.

Wolf;
    Ran the sudo umount /mnt command. No change in UCK's behavior.
   After running the unmount command, I ran zenity --info --text "hello world" from the command line. A dialog box popped up, with " hello world " in it. The terminal output when I ran it showed:

 zenity --info --text "hello world"

progname=zenity; RGBA=on
/home/alien/.gtkrc-2.0:1: Invalid color constant '#'
/home/alien/.gtkrc-2.0:1: error: invalid string constant "#", expected valid string constant
/home/alien/.themes/Black-Diamond/gtk-2.0/gtkrc:92: Murrine configuration option "gradients" is no longer supported and will be ignored.

   The information about the theme is standard with any program I run with gksu.

alien@DQ965GF:~$ ls -l /bin/sh
lrwxrwxrwx 1 root root 4 2010-08-14 08:04 /bin/sh -> dash

Which is surprising...I thought bash was my shell.

alien@DQ965GF:~$ ls -l /bin/bash
-rwxr-xr-x 1 root root 970048 2010-04-18 22:16 /bin/bash

was the result of the next command you suggested.

Running uck-gui gave me (I'm omitting the theme and .gtkrc info:

alien@DQ965GF:~$ uck-gui

progname=zenity; RGBA=on
progname=zenity; RGBA=on
progname=zenity; RGBA=on
progname=zenity; RGBA=on

Note: Doing the above also had the gui pop-up, and it behaved as if I'd launched it from the Menu. Took info, went thru 2 language selection screens, the "Select items from the list page" (I selected en), and the page asking for the desktop environment (I choose gnome). Finally, the same failure at the "Select ISO image" screen.

System info: I'm running Ubuntu 10.04.1 x86_64, with 2.6.32-25-generic as the kernel.

Aganin, any more information you need, feel free to ask. And thank you for your time in fixing this.

Chris

Ok - on to the next lower layer... ;-)

I'm getting to the point to believe that your desktop configuration might have something to do with it - please check the following:

1) make sure you run bash in a terminal
      gnome-terminal -x bash

2) source /usr/lib/uck/gui.sh
      . /usr/lib/uck/gui.sh

3) run the file-chooser library function
      dialog_choose_file "this is the title"
    and select some arbitrary file (e.g. your iso)

4) Confirm your choice with the "Accept" button.
    The dialog should go away and the full path of the file you selected
    should be displayed in the terminal you started this from.

5) Check the exit status of the chooser command
      echo $?
    -> This should print
      0

Any other status means something went wrong (which is my current working hypothesis).
You can then try to run
    zenity --title "this is the title" --file-selection "`pwd`/"
to nail it down even further - it should behave exactly like dialog_choose_file and return
the pathname and a zero exit status as well. Also
    gksudo -- zenity --title "this is the title" --file-selection "`pwd`/"
should behave the same (print the file name and exit with status 0)

Taking it point by point:

1) gnome-terminal -x bash opened up a terminal. All subsequent commands were run from there.

2) I wasn't sure by what this command meant. I ran:

alien@DQ965GF:~$ source /usr/lib/uck/gui.sh
alien@DQ965GF:~$ . /usr/lib/uck/gui.sh
alien@DQ965GF:~$ source /usr/lib/uck/gui.sh . /usr/lib/uck/gui.sh
alien@DQ965GF:~$
alien@DQ965GF:~$ source /usr/lib/uck/gui.sh ./usr/lib/uck/gui.sh

No results. The next thing I tried was cd'ing to /usr/lib/uck, and running gui.sh:

alien@DQ965GF:~$ cd /usr/lib/uck/gui.sh
bash: cd: /usr/lib/uck/gui.sh: Not a directory
alien@DQ965GF:~$ cd /usr/lib/uck/
alien@DQ965GF:/usr/lib/uck$ . /usr/lib/uck/gui.sh
alien@DQ965GF:/usr/lib/uck$ . /usr/lib/uck/gui.sh
alien@DQ965GF:/usr/lib/uck$ gui.sh
gui.sh: command not found
Hmm, gui.sh exists and is executable -- not sure what went wrong

Tried it under sudo:
alien@DQ965GF:/usr/lib/uck$ sudo sh !!
sudo sh gui.sh
[sudo] password for alien:

And again, no result

Finally cd'd out and went to 3),4) and 5)

 alien@DQ965GF:/usr/lib/uck$ cd
alien@DQ965GF:~$ dialog_choose_file "Ubuntu 10.04.1 x86_64" /home/alien/Music/ubuntu-10.04.1-desktop-amd64.iso

progname=zenity; RGBA=on
/home/alien/.gtkrc-2.0:1: Invalid color constant '#'
/home/alien/.gtkrc-2.0:1: error: invalid string constant "#", expected valid string constant
/home/alien/.themes/Black-Diamond/gtk-2.0/gtkrc:92: Murrine configuration option "gradients" is no longer supported and will be ignored.
/home/alien/Music/ubuntu-10.04.1-desktop-amd64.iso
alien@DQ965GF:~$ echo $?
0
alien@DQ965GF:~$ zenity --title "this is the title" --file-selection "`pwd`/"

progname=zenity; RGBA=on
/home/alien/.gtkrc-2.0:1: Invalid color constant '#'
/home/alien/.gtkrc-2.0:1: error: invalid string constant "#", expected valid string constant
/home/alien/.themes/Black-Diamond/gtk-2.0/gtkrc:92: Murrine configuration option "gradients" is no longer supported and will be ignored.
/home/alien/Music/ubuntu-10.04.1-desktop-amd64.iso
alien@DQ965GF:~$ echo $?
0
alien@DQ965GF:~$ gksudo -- zenity --title "this is the title" --file-selection "`pwd`/"
/home/alien/.gtkrc-2.0:1: Invalid color constant '#'
/home/alien/.gtkrc-2.0:1: error: invalid string constant "#", expected valid string constant
/home/alien/.themes/Black-Diamond/gtk-2.0/gtkrc:92: Murrine configuration option "gradients" is no longer supported and will be ignored.
/home/alien/Music/ubuntu-10.04.1-desktop-amd64.iso
alien@DQ965GF:~$

It could be the desktop configuration. I have an overly tweaked setup. If I didn't do something properly in your second point, please let me know-I'd never seen the source command before.

Again, many thanks
Chris

As for 'sourcing': I meant the second line, but the first will work as well. The net result of either line is to add the functions in gui.sh to the current shell. No output is produced. That dialog_choose_file was found indicates that you did the right thing.

I'm a bit surprised that the output and status looks ok, so the last thing I can think of is that maybe one of the error messages becomes part of the output. In order to verify this hypothesis please run:
  x=$(gksudo -- zenity --title test --file-selection "`pwd`/" 2>/dev/null)
  echo ">$x<"
The only thing between > and < should be the filename.

All right, here we go, running in a terminal started with gnome-terminal -x bash
alien@DQ965GF:~$ x=$(gksudo -- zenity --title test --file-selection "`pwd`/" 2>/dev/null) echo ">Ubuntu 10.04.1 x86_64<"
>Ubuntu 10.04.1 x86_64<
alien@DQ965GF:~$

File dialog box came up, labeled "test". I selected the iso. File dialog box disappeared. No further terminal output.

As always, more info on request.

Chris

And if it is the desktop configuration, I'm willing to delete some files, or do whatever needs to be done to reset them.

Hi Chris,

The test you did is not quite what I need - you need to leave the ">$x<" alone. Just copy&paste the following two lines into a terminal and then enter the password and select your file in the dialogs displayed:

x=$(gksudo -- zenity --title test --file-selection "`pwd`/" 2>/dev/null)
echo ">$x<"

This defines&sets a variable called x to the output of the zenity command and then prints the contents of the variable; The assumption here is that we will see *more* than just the path name between the >< and the additional text in there will give us a pointer on where the problem is. I.e. the needed/expected outcome would be:
    >/home/alien/Music/ubuntu-10.04.1-desktop-amd64.iso<
and I suspect the outcome is similar to:
    >/home/alien/.gtkrc-2.0:1: Invalid color constant '#'
/home/alien/Music/ubuntu-10.04.1-desktop-amd64.iso<

The whole text between >< is used by UCK as the name of the ISO to mount, so if it contains more than just the expected path it is going to fail with precisely the error message you are reporting.

Success!!!
  UCK is now running in a terminal window...got past the troublesome window.
  For the record, I had followed the instructions here: http://www.whttp://www.webupd8.org/2010/05/enable-rgba-transparency-in-ubuntu-910.html , except I had NOT enabled the particular repository mentioned. The fix was to change the settings in gnome-color-chooser NOT to provide RGBA support, then remove gtk2-module-rgba and gnome-color-chooser. I then rebooted.

And I wouldn't call you "dumb" - Linux has a mathematical elegance to it, but there are still many interconnected parts. I never would have thought something like the RGBA model was causing the problem.

Many, many thanks Wolf. I'm marking this as solved.

P.S. And thank you for your work on UCK

Chris

Thanks Wolf Geldmacher, that solved my question.