Re: Bug#242374: gnome-volume-manager: does not receive any messages
On Di, Apr 06, 2004 at 02:31:09 +0200, Sjoerd Simons wrote:
> > manager.c/733: unhandled dbus message: ServiceAcquired from
> > org.freedesktop.DBus
> > manager.c/581: New Device: /org/freedesktop/Hal/devices/block_11_1-disc
> > manager.c/613: Changed: /dev/scsi/host2/bus0/target0/lun0/cd
> > mount: can't find /dev/scsi/host2/bus0/target0/lun0/cd in /etc/fstab or
> > /etc/mta
> > Should I file a separate bug? Or is this a known issue?
> gvm just tries to mount your device using the mount command. So you need
> an fstab entry for the device. This is not a gvm bug.
Well, then it is a kernel bug. Anyway, g-v-m is bound to fail if anyone
uses devfs device naming style together with compatibility link. Well,
you might want to add a note to a (yet nonexisting) README.debian.
> > > Please let me know if this is indeed the problem, so i can reassign it
> > > to udev or start digging somewhat further.
> > You might want to reassing & merge with #242283
> Ok, thanks.
Another question - І wonder if this is still related or a separate
issue: Shouldn't nautilus display the volume label once it has mounted a
removable media (just as it did without g-v-m)? On my box, it uses the
name of the mount point instead, ie. the desktop icons are called
"cdrom" and "Brenner" (=burner) instead of [CD-ROM Label]
Now, is this also caused by poor communication between dbus-1 and udev?
Or is nautilus itself to blame?