gnome-volume-manager 1.5.14 fails to start

[Gregory Oschwald]

Binary package hint: gnome-volume-manager

(See the comments below for more insight on this problem. The description needs to be updated based on what I found out below.)

I just installed a DVD drive on a box that I previously upgraded from Breezy to Dapper. When I place a CD-ROM in the drive, it fails to automatically mount. I have "Mount removable media when inserted" checked, and this line in my fstab:

/dev/hdc /media/cdrom0 udf,iso9660 user,noauto 0 0

I can mount the drive manually fine.

Here is the drive information from dmesg:

[4294675.444000] hdc: LITE-ON DVDRW SHW-160P6S, ATAPI CD/DVD-ROM drive
[4294676.057000] ide1 at 0x170-0x177,0x376 on irq 15
[4294676.082000] hda: max request size: 1024KiB
[4294676.098000] hda: 234441648 sectors (120034 MB) w/8192KiB Cache, CHS=16383/255/63, UDMA(100)
[4294676.098000] hda: cache flushes supported
[4294676.099000] hda: hda1 hda2 < hda5 >
[4294676.116000] hdc: ATAPI 48X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(66)
[4294676.116000] Uniform CD-ROM driver Revision: 3.20

Any help would be appreciated.

[Gregory Oschwald (osch0001)]

Here is the hal.log as specified in https://wiki.ubuntu.com/DebuggingRemovableDevices

[Gregory Oschwald (osch0001)]

On further inspection, gnome-volume-manager isn't running at all on this machine and when I try to start it manually, it just returns to the terminal.

[Gregory Oschwald (osch0001)]

To the last comment, I should add that it returns to the terminal and the process doesn't show up in the process list. It does the same thing with the -n flag.

[Gregory Oschwald (osch0001)]

lshal's output

[Gregory Oschwald (osch0001)]

After som further testing, I have discovered that gnome-volume-manager up to 1.5.13-0ubuntu3 work fine, but none of the 1.5.14 versions work. They just exit to the command line immediately (even with -n).

[Martin Pitt (pitti)]

Thanks for your great testing so far!

Does 'gnome-volume-manager --no-daemon' output anything at all? Does it segfault? If you do

  $ gdb --args gnome-volume-manager --no-daemon
  (gdb) run

does it return normally or halts in a segfault or so? In the latter case, can you do 'bt' and give the output here?

If it just exits due to some condition it does not like, it's necessary to build a debug version and gdb through it. Maybe you can give me ssh access to your box so that I can do it? Or are you able to do it yourself?

Thanks!

[Gregory Oschwald (osch0001)]

Hi Martin,

It seems to return normally.

Using gnome-volume-manager 1.5.15-0ubuntu7, it seems that it is exiting
at the "exit 1" on line 3490. Here are the last several steps it made:

3449 bind_textdomain_codeset (PACKAGE, "UTF-8");
3450 textdomain (PACKAGE);
3452 program = gnome_program_init (PACKAGE, VERSION,
LIBGNOMEUI_MODULE, argc, argv,
3457 if (print_version) {
3462 if (daemon_arg != NULL) {
3468 fprintf (stdout, _("Unrecognized
--daemon argument: %s\n"), daemon_arg);
3471 if (no_daemon)
3474 if (secret_mode)
3477 if (daemonize && daemon (0, 0) < 0) {
3482 client = gnome_master_client ();
3483 if (gvm_get_clipboard () && gvm_user_at_console ()) {
3486 gnome_client_set_restart_style (client,
GNOME_RESTART_NEVER);
3487 if (gvm_user_at_console ())
3488 warn ("already running");
3547 }
0xb7408ea2 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6

It seems to mistakenly think that it is already running (which it is not).

Please let me know if this is what you wanted, if not I can give you
more information or possibly give you an account on the machine.

Greg

[Guy Van Sanden (gvs)]

I can second this bug. I marked my bugreport as a duplicate of this one.

[Martin Pitt (pitti)]

Hi Greg,

thanks for the gdb rundown, that was very helpful. gvm_user_at_console() fails for you.

What does

  ls -l /var/run/console

say for you? There should be a file like 'greg:7', where 'greg' is your user name, and '7' the console X runs at (7 is the default). This will only exist for local logins, not for remote X sessions.

What does

  dpkg -s libpam-foreground

say?

Thanks!

[Gregory Oschwald (osch0001)]

> What does
>
> ls -l /var/run/console
>
> say for you?

Hmm, /var/run/console doesn't exist for some reason. I notice that in
the bug that was marked as a duplicate of this one, the machine was
using LDAP for authentication, which my machine is as well. However,
this is not occurring on all machines in our network, even though those
are using LDAP as well.

> What does
>
> dpkg -s libpam-foreground
>
> say?
>
Status: install ok installed
Priority: required
Section: misc
Installed-Size: 56
Maintainer: Matthew Garrett <email address hidden>
Architecture: i386
Version: 0.2
Description: create lockfiles describing which users own which console
 This PAM module creates a lockfile whenever a user logs in, specifying the
 username and the console. This allows software to check whether the user
 making a request is on the current foreground console or not.

[Guy Van Sanden (gvs)]

Same here, /var/run/console does not exist, yet pam-foreground is installed.

pam-foreground isn't listed in /etc/pam.d/* though, maybe that is the problem?

[Martin Pitt (pitti)]

Guy,

indeed that's the problem then. I close this bug as duplicate of bug 34063. Can you please attach your PAM configuration to that bug?