GNOME Bugzilla – Bug 162327
Play Disc no working
Last modified: 2006-07-13 19:56:28 UTC
1) launch totem 2) click Movie->Play Disc Error alert shows complaining about the drive not having a mount point in /etc/fstab. The disc should play fine without the fstab entry. It plays fine on insertion with gvm running totem --play dvd:// without the entry so should do from the menu as well. I am using the xine-lib backend.
Can you give the exact error? is your mountpoint a symlink?
The actual error is: "Failed to play Audio/Video Disc Failed to find mountpoint for device /dev/hdc in /etc/fstab" It is a normal directory, /media/hdc
Can you give the contents of /etc/fstab?
/dev/hda1 / ext3 defaults 0 1 /dev/hda5 none swap defaults 0 0 none /sys sysfs defaults 0 0 none /proc proc defaults 0 0 /dev/hda8 /usr/local ext3 defaults 0 0 /dev/hda7 /mnt/games ext3 defaults 0 0 hdc not being there as it is mounted via gvm/pmount. /etc/mtab has /dev/hdc /media/hdc udf ro,noexec,nosuid,nodev,uid=1000,gid=1000,umask=007 0 0 in it though.
Could you try adding a line to src/totem-disc.c, line 172: g_message ("pdev %s pdev2 %s", pdev, pdev2); And send us the output of "src/disc-test /dev/hdc"?
It doesn't appear to get that far, infact gnome_vfs_volume_monitor_get_connected_drives() doesn't seem to be giving any results. hdc does appear in nautilus / the file selector though. May not be a totem bug after all.
Is that the gnome-vfs bug if gnome-vfs is not built against HAL?
no, I've just rebuilt gnome-vfs against HAL and its still showing the same problem
Could you attach your /etc/mtab, /etc/fstab and /proc/mounts in a tarball to this bug? I'll move it to gnome-vfs now.
Created attachment 36737 [details] requested tarball contains /etc/fstab /etc/mtab and /proc/mounts
This happens to me also at work. I have there a haldaemon from rawhide working from /usr prefix, and libhal jhbuilt in /home/fer/gnome2, so when compiling gnome-vfs with hal support, the gnome-vfs-dameon doesn't get the right info from the haldaemon.
Experienced this issue once, resolved it by recompiling gnomevfs (I did not see anything except 'Filesystem' in 'Computer' folder as well)
I guess this has been fixed. If I am mistaken please feel free to reopen this bug. Marking FIXED.