Breezy can't automount DVD-ROM

[azteech]

In Hoary I was able to have the DVD-ROM automount when I inserted a cd or dvd.

I upgraded to Breezy, doing a clean install (Ubuntu 5.10, built on
20050317ubuntu15) and now automounting for the DVD-ROM doesn't work.
Additionally, I have been doing apt-get update && apt-get upgrade (as well as
apt-get dist-upgrade) on a regular basis - including those for today - to ensure
I maintain everything up to date.

When I put in a cd or a dvd, nothing happens. In Nautilus, I can see the
standard empty "CD-ROM/DVD-ROM Drive" icon, but it does not change to the cd/dvd
icon when a disk is inserted. When I try to mount it, I receive the following
message:

    Unable to mount the selected volume.
    Error: given UDI is not a mountable volume

DVD-ROM is the slave device. The master device is a CD-RW Drive - both of which
are on the IDE Secondary interface.
The master is identified as IDE4816, the slave is identified as a Samsung
DVD-ROM SD-608.

I am able to successfully use a audio or data CD in the CD-RW drive. When I
place the same disk(s) in the DVD-ROM drive, I always get the above error.

[John Tanner (jdtanneratgmaildotcom)]

I'm having exactly the same problems here with my cdrom and my usb flashdisk. I
can issue the command "mount /media/cdrom" to mount the drive, but this isn't
ideal.

[sk545 (khu)]

It used to be that if you inserted a dvd or cd into your drive, a icon would come up on the
desktop which will let you browse the dvd/cd or even start playing it. That has stopped happening
after i upgraded to breezy from hoary. It looks like the dvd gets mounted if i look at dmesg:

"UDF-fs INFO UDF 0.9.8.1 (2004/29/09) Mounting volume 'movie_name', timestamp 2005/07/19 02:24
(1f10)"

However, i get no cd icon on the desktop.

I do have everything pertinent checked off in the "Removable Drives and media preferences".

Thx.

Relevant forum threads:

http://ubuntuforums.org/showthread.php?t=77141

http://ubuntuforums.org/showthread.php?t=76858

[MichaelIhde (mike-ihde)]

I'm having the same problem with my Ipod and my USB flash reader on a fresh
install of Breezy. Oddly enough everything works on my laptop (which has a
Breezy RC install with the most recent updates). I found that if I run "hald
--retain-priveleges" the devices automounts (but does not showup on the desktop).

[MichaelIhde (mike-ihde)]

Things are working now...I added hal to the cdrom & plugdev groups, then killed
all gnome-volume-managers and now things work.

[Matt Zimmerman (mdz)]

(Please don't confirm your own bugs; the purpose of that feature is for someone
else to independently verify your bug)

[John Tanner (jdtanneratgmaildotcom)]

(In reply to comment #4)
> Things are working now...I added hal to the cdrom & plugdev groups, then killed
> all gnome-volume-managers and now things work.

Further to the above comment, this does not help matters with my install. It
appears that this is affecting many users of removeable media, all the way
through from internal cd-rom drives right up to external floppy usb disks. Many
people are seeing the "Unable to mount the selected volume. Error: given UDI is
not a mountable volume" error, and this is being followed up by a drive icon not
appearing on the desktop. It seems that this behaviour is exhibited for both
upgrade and fresh installs of breezy.

Cheers

[Johannes Hessellund (osos)]

(In reply to comment #6)
> Many people are seeing the "Unable to mount the selected volume. Error: given
UDI is
> not a mountable volume" error, and this is being followed up by a drive icon not
> appearing on the desktop. It seems that this behaviour is exhibited for both
> upgrade and fresh installs of breezy.

I see the same problem with both usb-harddisk and usb-stick.
The usb-stick appears in Nautilus "Machine" but cannot be mounted.

The usb-harddrive doesn't add up in Nautilus. But dmesg reports scsi disk connected.

Both worked fine 2 days ago...

[hva (francesco-hv-a)]

I am experimenting same problem since i upgraded to breezy 10 days ago.
I can get rid of it if i do the following:
restart dbus (sudo /etc/init.d/dbus restart)
restart gnome-volume-manager
restart gnome-panel (if u use automunt applet, with 'killall gnome-panel')
restart nautilus ('killall nautilus')
after that it all works perfectly, like it is supposed too. floppy, cd, dvd and
usb devices are mountable and
unmountable both from applet and nautilus, and icons correctly appear on desktop.

[Jamie Wilkinson (jaq-spacepants)]

Fresh install of breezy from the i386 ISO yesterday, onto an IBM Thinkpad X40:

* attaching a USB CDROM, gets detected

* inserting a blank cdrom, I do not get asked if i'd like to create a cd.

* manually running the CD creator app works

* ejecting and reinserting the newly burnt cd, does not automount

The comment regarding adding hal to cdrom,plugdev groups is invalid; this is
already set up on my machine.

[Jamie Wilkinson (jaq-spacepants)]

(In reply to comment #8)
> I am experimenting same problem since i upgraded to breezy 10 days ago.
> I can get rid of it if i do the following:
> restart dbus (sudo /etc/init.d/dbus restart)
> restart gnome-volume-manager
> restart gnome-panel (if u use automunt applet, with 'killall gnome-panel')
> restart nautilus ('killall nautilus')
> after that it all works perfectly, like it is supposed too. floppy, cd, dvd and
> usb devices are mountable and
> unmountable both from applet and nautilus, and icons correctly appear on desktop.

I can confirm that restarting dbus, g-v-m, g-p, and nautilus now causes the
correct behaviour to occur.

[sk545 (khu)]

(In reply to comment #10)
> (In reply to comment #8)
> > I am experimenting same problem since i upgraded to breezy 10 days ago.
> > I can get rid of it if i do the following:
> > restart dbus (sudo /etc/init.d/dbus restart)
> > restart gnome-volume-manager
> > restart gnome-panel (if u use automunt applet, with 'killall gnome-panel')
> > restart nautilus ('killall nautilus')
> > after that it all works perfectly, like it is supposed too. floppy, cd, dvd and
> > usb devices are mountable and
> > unmountable both from applet and nautilus, and icons correctly appear on desktop.
>
>
> I can confirm that restarting dbus, g-v-m, g-p, and nautilus now causes the
> correct behaviour to occur.
>

The above method does not survive a reboot, so its not a ideal solution. Plus, it does not launch
applications automatically. The only other error i get is when i run 'gnome-volume-manager'
manually, then insert a disk. The console spits out this:

manager.c/1258: mounting /org/freedesktop/Hal/devices/volume_label_...
manager.c/696: executing command: /usr/bin/pmount-hal /org/freedesktop/Hal/devices/volume_label_
Warning: device /dev/hdc is already handled by /etc/fstab, supplied label is ignored

Not really sure if the above "Warning" is anything to worry about.

[azteech (stevep.)]

(In reply to comment #5)
> (Please don't confirm your own bugs; the purpose of that feature is for someone
> else to independently verify your bug)

Sorry Matt. Didn't know that - this is the 1st bug I ever submitted for Ubuntu.
Thought if I could reconfirm that the problem exhisted,
after I had done several things, like described by others here, then that could
be reason enough to change status.

Might I suggest a change then to bugzilla. If the originator should not be the
one to change the status for the reported bug,
then all follow-on options shuld be greyed out for that person whom submitted
the bug. Therefore ensuring that the submitter
not able to throw in additional (and un-needed) confussion.

[Johannes Hessellund (osos)]

(In reply to comment #10)
> (In reply to comment #8)
> > I am experimenting same problem since i upgraded to breezy 10 days ago.
> > I can get rid of it if i do the following:
> > restart dbus (sudo /etc/init.d/dbus restart)
> > restart gnome-volume-manager
> > restart gnome-panel (if u use automunt applet, with 'killall gnome-panel')
> > restart nautilus ('killall nautilus')
> > after that it all works perfectly, like it is supposed too. floppy, cd, dvd and
> > usb devices are mountable and
> > unmountable both from applet and nautilus, and icons correctly appear on
desktop.
>
>
> I can confirm that restarting dbus, g-v-m, g-p, and nautilus now causes the
> correct behaviour to occur.
>

Didn't help me.

When I plugin a usb-stick or usb-hdd.
ps -A gives me this:
 6253 ? 00:00:00 scsi_eh_1
 6254 ? 00:00:00 usb-storage
 6339 ? 00:00:00 hald-addon-storage

sometimes an icon appears in nautilus, but I can't mount it:
Error: given UDI is not a mountable volume

[Johannes Hessellund (osos)]

A reinstall brought this to work again.

Meaning that some packet I installed must have broken it.

Now it is exiting when it breaks again!

[Matt Zimmerman (mdz)]

(In reply to comment #12)
> Might I suggest a change then to bugzilla. If the originator should not be the
> one to change the status for the reported bug,
> then all follow-on options shuld be greyed out for that person whom submitted
> the bug. Therefore ensuring that the submitter
> not able to throw in additional (and un-needed) confussion.

The fact that Bugzilla allows this is a bug, but since we are moving to a
different bug tracking system, we will not be spending resources on fixing bugs
in Bugzilla.

[sk545 (khu)]

Alright, so anyone in the dev team confirm this bug? Or is this something that will take months to fix?

[Martin Pitt (pitti)]

(In reply to comment #16)
> Alright, so anyone in the dev team confirm this bug? Or is this something
that will take months to fix?

Fixing is usually easy after we know the source of the problem. This works fine
on all boxes I upgraded to hoary.

Can you guys please do the steps described on the first half of

  http://wiki.ubuntu.com/DebuggingRemovableDevices

and attach the logs here?

Thanks!

[John Tanner (jdtanneratgmaildotcom)]

(In reply to comment #17)
> (In reply to comment #16)
> > Alright, so anyone in the dev team confirm this bug? Or is this something
> that will take months to fix?
>
> Fixing is usually easy after we know the source of the problem. This works fine
> on all boxes I upgraded to hoary.
>
> Can you guys please do the steps described on the first half of
>
> http://wiki.ubuntu.com/DebuggingRemovableDevices
>
> and attach the logs here?
>
> Thanks!

Can I just add that this isn't limited to removeable devices...the original
poster was talking about an internal cd/dvd drive.

Cheers,
JohnT

[sk545 (khu)]

Created an attachment (id=4701)
gvm.log

[sk545 (khu)]

Created an attachment (id=4702)
lshal.txt

[sk545 (khu)]

Created an attachment (id=4703)
devices.txt

[sk545 (khu)]

Created an attachment (id=4704)
dmesg.txt

[sk545 (khu)]

output from 'id':

uid=1000(me) gid=1000(me) groups=4(adm),20(dialout),24(cdrom),25(flopp y),29(audio),30(dip),
44(video),46(plugdev),107(lpadmin),108(scanner),109(admin), 1000(me)

[sk545 (khu)]

Created an attachment (id=4705)
hal.log

[sk545 (khu)]

(In reply to comment #24)
> Created an attachment (id=4705) [edit]
> hal.log
>

I used a usb pendrive to do the above attachments, let me know if a cd/dvd test is needed also.
One question: does g-v-m run all the time in the background? I mean, don't ever see it with 'ps -
aux' unless i connect a pendrive or insert a cd/dvd.

thx.

[Martin Pitt (pitti)]

(In reply to comment #19)
> Created an attachment (id=4701) [edit]
> gvm.log

manager.c/1258: mounting /org/freedesktop/Hal/devices/volume_part1_size_64405504...
manager.c/696: executing command: /usr/bin/pmount-hal
/org/freedesktop/Hal/devices/volume_part1_size_64405504

This looks pretty successful - are you sure that the device was not mounted?
Does /dev/sda1 occur in the output of "mount"? If not, please send the output of

  pmount -d /dev/sda1

[sk545 (khu)]

(In reply to comment #26)
> (In reply to comment #19)
> > Created an attachment (id=4701) [edit] [edit]
> > gvm.log
>
> manager.c/1258: mounting /org/freedesktop/Hal/devices/volume_part1_size_64405504...
> manager.c/696: executing command: /usr/bin/pmount-hal
> /org/freedesktop/Hal/devices/volume_part1_size_64405504
>
> This looks pretty successful - are you sure that the device was not mounted?
> Does /dev/sda1 occur in the output of "mount"? If not, please send the output of
>
> pmount -d /dev/sda1

The issue is not that it doesn't mount, but that there is no icon on the desktop and nor does an
application launch automatically when a dvd is inserted. It mounts just fine:

$ mount
/dev/sda1 on /media/usbdisk type vfat (rw,noexec,nosuid,.............)

Output from pmount:

$ pmount -d /dev/sda1

resolved /dev/sda1 to device /dev/sda1
mount point to be used: /media/sda1
no iocharset given, current locale encoding is UTF-8
locale encoding uses UTF-8, setting iocharset to 'utf8'
Cleaning lock directory /var/lock/pmount/_dev_sda1
Error: device /dev/sda1 is already mounted to /media/usbdisk
policy check failed

Thx.

[Martin Pitt (pitti)]

> The issue is not that it doesn't mount, but that there is no icon on the
desktop and nor does an
> application launch automatically when a dvd is inserted. It mounts just fine:

Ah, I see. I'm a bit puzzled about that one. Does this work with a freshly
created user (i. e. without a pre-existing home directory?)

[sk545 (khu)]

(In reply to comment #28)
> > The issue is not that it doesn't mount, but that there is no icon on the
> desktop and nor does an
> > application launch automatically when a dvd is inserted. It mounts just fine:
>
> Ah, I see. I'm a bit puzzled about that one. Does this work with a freshly
> created user (i. e. without a pre-existing home directory?)
Whats the proper way to add a user/password, then delete it all after checking?

[sk545 (khu)]

(In reply to comment #29)
> (In reply to comment #28)
> > > The issue is not that it doesn't mount, but that there is no icon on the
> > desktop and nor does an
> > > application launch automatically when a dvd is inserted. It mounts just fine:
> >
> > Ah, I see. I'm a bit puzzled about that one. Does this work with a freshly
> > created user (i. e. without a pre-existing home directory?)
> Whats the proper way to add a user/password, then delete it all after checking?

Nevermind, i figured out how to add/del users. After adding a new user, there is no change in
behaviour: The item (cd/dvd, usb drive) get mounted, but there is no icon on desktop nor does a
application automatically launch itself.
>

[John Tanner (jdtanneratgmaildotcom)]

Can I suggest that this may be linked to bug number 17562?

JohnT

[sk545 (khu)]

(In reply to comment #31)
> Can I suggest that this may be linked to bug number 17562?
>
> JohnT

It looks like it is...but, the fix on 17562 was uploaded to dapper and not breezy??

[Martin Pitt (pitti)]

(In reply to comment #32)
> (In reply to comment #31)
> > Can I suggest that this may be linked to bug number 17562?
> >
> > JohnT
>
> It looks like it is...but, the fix on 17562 was uploaded to dapper and not
breezy??

Are you really sure that the new pmount fixes this problem? I don't see the
connection, but if it helps, let's try it out: Can you please download

  http://archive.ubuntu.com/ubuntu/pool/main/p/pmount/pmount_0.9.6-1_i386.deb

install it with

  sudo dpkg -i pmount_0.9.6-1_i386.deb

and check if it works?

[sk545 (khu)]

(In reply to comment #33)
> (In reply to comment #32)
> > (In reply to comment #31)
> > > Can I suggest that this may be linked to bug number 17562?
> > >
> > > JohnT
> >
> > It looks like it is...but, the fix on 17562 was uploaded to dapper and not
> breezy??
>
> Are you really sure that the new pmount fixes this problem? I don't see the
> connection, but if it helps, let's try it out: Can you please download
>
> http://archive.ubuntu.com/ubuntu/pool/main/p/pmount/pmount_0.9.6-1_i386.deb
>
> install it with
>
> sudo dpkg -i pmount_0.9.6-1_i386.deb
>
> and check if it works?
>

Tried it just now, it didn't work. One thing you might want to know is that after inserting a
disc in the drive, then going to Places > Computer and then clicking on the CDRW icon, it just
gives this:

Warning: device /dev/hdc is already handled by /etc/fstab, supplied label is ignored
mount: /dev/hdc already mounted or /media/cdrom0 busy
mount: according to mtab, /dev/hdc is already mounted on /media/cdrom0
Error: could not execute pmount

I am not sure if the above message is related in any way to this bug here. The above happens with
any pmount i have installed (the new one you gave, and the current one in breezy repos).

[Martin Pitt (pitti)]

Alright, it seems that you encountered the same bug as in #18394. Please add
your user to the plugdev group to get full access to removable media. You can do
this in the users-admin tool (System -> Administration -> Users and groups).

This bug has been marked as a duplicate of bug 24528.

[sk545 (khu)]

Created an attachment (id=4790)
/etc/group

[sk545 (khu)]

(In reply to comment #36)
> Created an attachment (id=4790) [edit]
> /etc/group
>

I didn't see the group plugdev in System -> Administration -> Users and groups.
 But the plugdev group is in /etc/group. Do i have to make another plugdev
group in System > Administration? I am attaching the /etc/group file, if you
want to look at it. With that setting, the problem does not go away.

Thx.

[Rodrigo Virote Kassick (kassick)]

Check if "Show all users and groups" is checked in the "Groups" tab.

I've been having the same problems and I definitively am in plugdev group.

(In reply to comment #37)
> (In reply to comment #36)
> > Created an attachment (id=4790) [edit] [edit]
> > /etc/group
> >
>
> I didn't see the group plugdev in System -> Administration -> Users and groups.
> But the plugdev group is in /etc/group. Do i have to make another plugdev
> group in System > Administration? I am attaching the /etc/group file, if you
> want to look at it. With that setting, the problem does not go away.
>
> Thx.

[Rodrigo Virote Kassick (kassick)]

Besides,
Bug 24528 is about devices not beeing mounted.
The behavior here is that nautilus/volume-manager/vfs2 ain't noting that the
device is already mounted.

(In reply to comment #38)
> Check if "Show all users and groups" is checked in the "Groups" tab.
>
> I've been having the same problems and I definitively am in plugdev group.
>
>
> (In reply to comment #37)
> > (In reply to comment #36)
> > > Created an attachment (id=4790) [edit] [edit] [edit]
> > > /etc/group
> > >
> >
> > I didn't see the group plugdev in System -> Administration -> Users and groups.
> > But the plugdev group is in /etc/group. Do i have to make another plugdev
> > group in System > Administration? I am attaching the /etc/group file, if you
> > want to look at it. With that setting, the problem does not go away.
> >
> > Thx.

[sk545 (khu)]

(In reply to comment #39)
> Besides,
> Bug 24528 is about devices not beeing mounted.
> The behavior here is that nautilus/volume-manager/vfs2 ain't noting that the
> device is already mounted.
>
> (In reply to comment #38)
> > Check if "Show all users and groups" is checked in the "Groups" tab.
> >

Yep, i am in there alright. This bug needs to be re-opened.
> > I've been having the same problems and I definitively am in plugdev group.
> >
> >
> > (In reply to comment #37)
> > > (In reply to comment #36)
> > > > Created an attachment (id=4790) [edit] [edit] [edit] [edit]
> > > > /etc/group
> > > >
> > >
> > > I didn't see the group plugdev in System -> Administration -> Users and groups.
> > > But the plugdev group is in /etc/group. Do i have to make another plugdev
> > > group in System > Administration? I am attaching the /etc/group file, if you
> > > want to look at it. With that setting, the problem does not go away.
> > >
> > > Thx.
>
>

(In reply to comment #38)
> Check if "Show all users and groups" is checked in the "Groups" tab.
>
> I've been having the same problems and I definitively am in plugdev group.
>
>
> (In reply to comment #37)
> > (In reply to comment #36)
> > > Created an attachment (id=4790) [edit] [edit] [edit]
> > > /etc/group
> > >
> >
> > I didn't see the group plugdev in System -> Administration -> Users and groups.
> > But the plugdev group is in /etc/group. Do i have to make another plugdev
> > group in System > Administration? I am attaching the /etc/group file, if you
> > want to look at it. With that setting, the problem does not go away.
> >
> > Thx.

[Martin Pitt (pitti)]

Closing as a dup was not justified, sorry; I should have looked more closely.

[dirk luesebrink (ubuntu-com-sebrink)]

(In reply to comment #41)
> Closing as a dup was not justified, sorry; I should have looked more closely.

i also have trouble with mounting, that relates to pmount is not executing. BUT,
pmount is not executing because it thinks i'm not in the plugdev group which is
wrong. i did add myself to quite a couple of groups, but NONE of my groups is
showing up when doing a "prompt: id --groups" to list my groups.

the system seems to ignore the /etc/group file completly.

bizarre,

the lack of proper groupmember ship does prevent me from actually administrating
the machine as non-root user. and i would prefer not log into my X Desktop as root.

any help is appreciated.

cherio
dirk

[azteech (stevep.)]

(In reply to comment #41)
> Closing as a dup was not justified, sorry; I should have looked more closely.

Okay, I am finally able to automount the DVD-ROM and, have it playing DVD's or
read audio/data CD-Rom disks.

For what ever the reason, my user ID and those of my other users, were not in
the plugdev group (id 46). Looks like during the upgrade, plugdev did not
populate (for whatever reason).
After adding my UID to the plugdev group, the DVD-Rom became automountable. What
remains a mystery to me, is if this was the fix, then why would the CD R/W
automount/autoplay?

[Martin Pitt (pitti)]

(In reply to comment #43)
> For what ever the reason, my user ID and those of my other users, were not in
> the plugdev group (id 46).

Both the first user, and all subsequent users created with users-admin (with the
"Desktop" profile, which is the default) are in plugdev. Do you use remote
authentication?

> Looks like during the upgrade, plugdev did not
> populate (for whatever reason).

Group memberships are not automatically changed on upgrades, this would be scary
security-wise.

> After adding my UID to the plugdev group, the DVD-Rom became automountable. What
> remains a mystery to me, is if this was the fix, then why would the CD R/W
> automount/autoplay?

Breezy's gnome-vfs now uses pmount to mount removable devices to get nicer
device labels. However, only plugdev users are allowed to execute pmount.

So your problem *is* in fact a dup of #18394.

So let's devote this bug to khurram who obviously has a different problem.

[Martin Pitt (pitti)]

(In reply to comment #42)
> (In reply to comment #41)
> > Closing as a dup was not justified, sorry; I should have looked more closely.
>
> i also have trouble with mounting, that relates to pmount is not executing. BUT,
> pmount is not executing because it thinks i'm not in the plugdev group which is
> wrong. i did add myself to quite a couple of groups, but NONE of my groups is
> showing up when doing a "prompt: id --groups" to list my groups.
>
> the system seems to ignore the /etc/group file completly.

Guys, please file a separate report for every separate bug. This bug already
became confusing enough.

So what is the output of "id", "getent group plugdev", and "getent passwd $(id
-un)" for you?

[Martin Pitt (pitti)]

So, for everybody:

 - Please check that the output of "id" contains "plugdev". If not, it's a dup
of #18394. Just add yourself to plugdev to get you going.
 - If you already are in group plugdev, and CDs are not automatically mounting,
attach the debugging output from http://wiki.ubuntu.com/DebuggingRemovableDevices.
 - If you have a different problem, please file a separate bug.

Thanks!

[sk545 (khu)]

(In reply to comment #46)
> So, for everybody:
>
> - Please check that the output of "id" contains "plugdev". If not, it's a dup
> of #18394. Just add yourself to plugdev to get you going.
> - If you already are in group plugdev, and CDs are not automatically mounting,
> attach the debugging output from http://wiki.ubuntu.com/DebuggingRemovableDevices.
> - If you have a different problem, please file a separate bug.
>
> Thanks!

Thanks for reopening the bug, Martin.

> - Please check that the output of "id" contains "plugdev". If not, it's a dup
> of #18394. Just add yourself to plugdev to get you going.

Yep, looks like i am part of it:

$ id
uid=1000(khurram) gid=1000(khurram) groups=4(adm),20(dialout),24(cdrom),25(floppy),29(audio),30(dip),44(video),46(plugdev
),107(lpadmin),108(scanner),109(admin),1000(khurram)

>So what is the output of "id", "getent group plugdev", and "getent passwd $(id
>-un)" for you?

$ getent group plugdev
plugdev:x:46:khurram,hal

$ getent passwd $(id -n)
id: cannot print only names or real IDs in default format
root:x:0:0:root:/root:/bin/bash
daemon:x:1:1:daemon:/usr/sbin:/bin/sh
bin:x:2:2:bin:/bin:/bin/sh
sys:x:3:3:sys:/dev:/bin/sh
sync:x:4:65534:sync:/bin:/bin/sync
games:x:5:60:games:/usr/games:/bin/sh
man:x:6:12:man:/var/cache/man:/bin/sh
lp:x:7:7:lp:/var/spool/lpd:/bin/sh
mail:x:8:8:mail:/var/mail:/bin/sh
news:x:9:9:news:/var/spool/news:/bin/sh
uucp:x:10:10:uucp:/var/spool/uucp:/bin/sh
proxy:x:13:13:proxy:/bin:/bin/sh
www-data:x:33:33:www-data:/var/www:/bin/sh
backup:x:34:34:backup:/var/backups:/bin/sh
list:x:38:38:Mailing List Manager:/var/list:/bin/sh
irc:x:39:39:ircd:/var/run/ircd:/bin/sh
gnats:x:41:41:Gnats Bug-Reporting System (admin):/var/lib/gnats:/bin/sh
nobody:x:65534:65534:nobody:/nonexistent:/bin/sh
postfix:x:100:103::/var/spool/postfix:/bin/false
syslog:x:105:105::/home/syslog:/bin/false
klog:x:106:106::/home/klog:/bin/false
khurram:x:1000:1000:khurram,,,:/home/khurram:/bin/bash
messagebus:x:101:110::/var/run/dbus:/bin/false
cupsys:x:102:107::/:/bin/false
fetchmail:x:103:65534::/var/run/fetchmail:/bin/sh
saned:x:113:113::/home/saned:/bin/false
dhcp:x:115:115::/nonexistent:/bin/false
hplip:x:107:7:HPLIP system user,,,:/var/run/hplip:/bin/false
gdm:x:104:114:Gnome Display Manager:/var/lib/gdm:/bin/false
hal:x:111:111:Hardware abstraction layer,,,:/var/run/hal:/bin/false

> - If you already are in group plugdev, and CDs are not automatically mounting,
> attach the debugging output from http://wiki.ubuntu.com/DebuggingRemovableDevices.

Already did that, let me know if you need anything else.

Thx.

[sk545 (khu)]

One thing i didn't mention was the fact that i am using a custom kernel from kernel.org (2.6.14). Is this automount/hal
feature very dependent on the kernel? I mean, maybe i don't have something turned "on" in the cutom kernel that the
breezy kernel has on by default.

Just a thought, might as well give all the info i can think of.

[Martin Pitt (pitti)]

(In reply to comment #48)
> One thing i didn't mention was the fact that i am using a custom kernel from
kernel.org (2.6.14). Is this automount/hal
> feature very dependent on the kernel?

*headdesk* Yes, it is. 2.6.14 has drastic changes in the hotplug architecture.
Breezy's hotplug/udev do not work with 2.6.14. Dapper will switch to 2.6.14 and
the new udev version soon.

Please use the standard Breezy kernel.

[sk545 (khu)]

(In reply to comment #49)
> (In reply to comment #48)
> > One thing i didn't mention was the fact that i am using a custom kernel from
> kernel.org (2.6.14). Is this automount/hal
> > feature very dependent on the kernel?
>
> *headdesk* Yes, it is. 2.6.14 has drastic changes in the hotplug architecture.
> Breezy's hotplug/udev do not work with 2.6.14. Dapper will switch to 2.6.14 and
> the new udev version soon.
>
> Please use the standard Breezy kernel.

Well, i suppose that clears it up. I wonder if all the people with this same problem were using custom kernels. I just
upgraded to kernel 2.6.14 like yesterday though, and was using 2.6.13.x before and all the time i had this "bug". 2.6.13.
x has drastic changes also? Well, i'll try the standard breezy kernel and see what happens. I apologize for not saying
this thing about the kernel before, its just that sometimes you get caught up, and you can't remember to put in all the
info. I'll get back to this bug if i still have problems after using the standard breezy kernel.

Thx again.

[Martin Pitt (pitti)]

(In reply to comment #50)
> I apologize for not saying
> this thing about the kernel before, its just that sometimes you get caught up,
and you can't remember to put in all the
> info.

Don't worry. I added the kernel version output to the DebuggingRemovableDevices
wiki page, so that we will immediately see this in the future.

Thanks!

[sk545 (khu)]

(In reply to comment #51)
> (In reply to comment #50)
> > I apologize for not saying
> > this thing about the kernel before, its just that sometimes you get caught up,
> and you can't remember to put in all the
> > info.
>
> Don't worry. I added the kernel version output to the DebuggingRemovableDevices
> wiki page, so that we will immediately see this in the future.
>
> Thanks!
>

Alright, after installing kernel ubuntu 2.6.12-9-386, i can confirm that this was not a bug (at least for me). All the
removable drives now show up on the desktop with a icon and the respective applications launch by themselves.

Thanks for all the time, and hopefully people that were having trouble have to just use the default brezzy kernel(s).

[azteech (stevep.)]

(In reply to comment #50)
>
> (In reply to comment #49)
> > (In reply to comment #48)
> > > One thing i didn't mention was the fact that i am using a custom kernel from
> > kernel.org (2.6.14). Is this automount/hal
> > > feature very dependent on the kernel?
> >
> > *headdesk* Yes, it is. 2.6.14 has drastic changes in the hotplug architecture.
> > Breezy's hotplug/udev do not work with 2.6.14. Dapper will switch to 2.6.14 and
> > the new udev version soon.
> >
> > Please use the standard Breezy kernel.
>
> Well, i suppose that clears it up. I wonder if all the people with this same
problem were using custom kernels. I just
> upgraded to kernel 2.6.14 like yesterday though, and was using 2.6.13.x before
and all the time i had this "bug". 2.6.13.
> x has drastic changes also? Well, i'll try the standard breezy kernel and see
what happens. I apologize for not saying
> this thing about the kernel before, its just that sometimes you get caught up,
and you can't remember to put in all the
> info. I'll get back to this bug if i still have problems after using the
standard breezy kernel.
>
> Thx again.
>

Just for the record, I am using the standard kernel, not a custom one.

[John Tanner (jdtanneratgmaildotcom)]

I'm using the standar kernel as well, but the updated pmount allows me to
manually mount my dvd/cd drive using "Computer" without the UDI problem.
Automounting for USB devices now works, but the CD/DVD still doesn't automount
and appear on the desktop :-(

[Luis Carlos Cobo (luiscarlos)]

Created an attachment (id=4911)
devices.txt (Luis Carlos)

[Luis Carlos Cobo (luiscarlos)]

Created an attachment (id=4912)
dmesg.txt (Luis Carlos)

[Luis Carlos Cobo (luiscarlos)]

Created an attachment (id=4913)
gvm.log (Luis Carlos)

[Luis Carlos Cobo (luiscarlos)]

Created an attachment (id=4914)
lshal.txt (Luis Carlos)

[Luis Carlos Cobo (luiscarlos)]

I use standard kernel, and my problem relates just to CD (usb works flawlessly
by now). First thing, to avoid the "Error: given UDI is not a mountable volume"
error I have to do the setps from comment #8 (isn't there anything more elegant
to fix it?). Then I can mount cds by introducing them and then clicking on the
CD icon on "Computer", but automount does not work. I attach everything stated
in DebuggingRemovableDevices.

Please note:
   - This was a fresh install. Both hal and my user are in plugdev and cdrom groups.
   - The error that appears on gvm.log is thrown before I insert the cd, as soon
as I run g-v-m, I guess it is because it tries to mount the usb disk, which is
already mounted. All the text in that file appears before I insert the cd. When
I insert the cd there isn't any additional output.
   - On step 11, instead of restarting gnome, I run the removable media config
dialog, which runs g-v-m in the proper way.
   - !!!! In ls-hal, note this:
           udi = '/org/freedesktop/Hal/devices/storage_model_HL_DT_STCD_RW
           (....) Many other lines referring to this udi, the only cd drive I have.
           storage.media_check_enabled = false (bool) <---- Isn't this the
problem???

As additional data, my laptop is an Inspiron 8200. I just came to Ubuntu from
Gentoo, and in my former distribution, when I first tried hal long time ago, I
had to manually deactivate the polling of the cd-drive because my specific cd
drive had some kind of problem with hal which caused the polling to take a lot
of resources and almost freeze the computer. Maybe hal now detects this and
somehow decides that polling is not worth in my drive??

I am really looking forward to squash this bug, is there any other information
that could be useful?

id output:
uid=1000(luisca) gid=1000(luisca)
groups=4(adm),20(dialout),24(cdrom),25(floppy),29(audio),30(dip),44(video),46(plugdev),104(lpadmin),105(scanner),106(admin),1000(luisca)

uname -a output:
Linux negrita 2.6.12-9-386 #1 Mon Oct 10 13:14:36 BST 2005 i686 GNU/Linux

Thanks

[John Tanner (jdtanneratgmaildotcom)]

(In reply to comment #59)

I confirm all of the above behaviour with another Dell Inspiron 8200 laptop.

Perhaps this should be moved to another bug?
John

[Martin Pitt (pitti)]

Ok, since the cause seems to be different for other people, I reopen this.

(In reply to comment #59)
> by now). First thing, to avoid the "Error: given UDI is not a mountable volume"
> error I have to do the setps from comment #8 (isn't there anything more elegant
> to fix it?).

Please see bug #36249. Can you please download the dapper version of pmount

  http://archive.ubuntu.com/ubuntu/pool/main/p/pmount/pmount_0.9.6-1_i386.deb

install it with

  sudo dpkg -i pmount_0.9.6-1_i386.deb

and verify that it works?

> - !!!! In ls-hal, note this:
> udi = '/org/freedesktop/Hal/devices/storage_model_HL_DT_STCD_RW
> (....) Many other lines referring to this udi, the only cd drive I
have.
> storage.media_check_enabled = false (bool) <---- Isn't this the
> problem???
>
> As additional data, my laptop is an Inspiron 8200. I just came to Ubuntu from
> Gentoo, and in my former distribution, when I first tried hal long time ago, I
> had to manually deactivate the polling of the cd-drive because my specific cd
> drive had some kind of problem with hal which caused the polling to take a lot
> of resources and almost freeze the computer. Maybe hal now detects this and
> somehow decides that polling is not worth in my drive??

Indeed. You have the exact drive that is blacklisted in
/usr/share/hal/fdi/preprobe/10osvendor/10-ide-drives.fdi:

    <!-- Handle weird Dell Laptops that slow down the system if the optical
         drive is polled (RH Bug #138148) -->
    <match key="storage.bus" string="ide">
      <match key="storage.model" string="HL-DT-STCD-RW/DVD-ROM GCC-4240N">
        <match key="block.device" string="/dev/hdb">
          <merge key="storage.media_check_enabled" type="bool">false</merge>
        </match>
        <match key="block.device" string="/dev/hdd">
          <merge key="storage.media_check_enabled" type="bool">false</merge>
        </match>
      </match>
    </match>

You can challenge your luck, edit the file as root and change 'false' to 'true'.
Then reboot your box (or restart hal and your session) and check whether it has
any negative impact.

[Martin Pitt (pitti)]

Luis, John, please tell me about your results. This check has been removed from
the current hal upstream version, and it would be nice to get more feedback
about it.

Thanks for your investigations!

[Luis Carlos Cobo (luiscarlos)]

New pmount had no effect, editing
/usr/share/hal/fdi/preprobe/10osvendor/10-ide-drives.fdi solved the problem. By
now looks like there is not any negative impact (and when I had it with older
hal versions it was really noticeable) so I guess that fixes the problem, I will
post here if later I notice negative impact. Only issue is that I had to restart
nautilus for the icon to appear on the screen.

[Linuxg33k (linuxg33k)]

i have had this series of problems on half a dozen machines, and yet on another
half dozen it did not appear.

it seems to only appear on clean installs, dist-upgrades seem to go okay (with
the exception of oo.org2 hosing the upgrade this time).

for this laptop i had the floppy issue from above, and still have the usb
devices not mount/activating.

- the floppy issue was solved by adding floppy module to /etc/modules and
upgrading pmount to dapper version.

- the usb issue is unresolved. usb stick lights up and then promptly shuts off,
usb mouse does not even light up. no /dev/sd* devices are created when I plug
ausb device in. the usb issue and therefore my devices.txt file is empty.

i posted my reports and files as well.

i hope this gets resolved this is definately a really bad situation, especially
for those of us running pilot programs and wishing to run ubuntu on the
corporate desktop.

[Linuxg33k (linuxg33k)]

Created an attachment (id=4995)
device output

[Linuxg33k (linuxg33k)]

Created an attachment (id=4996)
dmesg output

[Linuxg33k (linuxg33k)]

Created an attachment (id=4997)
gvm output

[Linuxg33k (linuxg33k)]

Created an attachment (id=4998)
lshal output

[Linuxg33k (linuxg33k)]

to post some additional information, i have now tested a number of other
distros, and every single one of them can access the usb port, only hoary and
breezy cannot.

this is either a configuration issue of some sort or the drivers are borked,
because as far as anyone can tell from all the testing we have done the kernel
simply does not see the usb port at all.

the modules can load and unload, the users are all in the right groups, but when
you tail /var/log/messages, the kernel simply gets no event of anything
happening on the usb port. i have a sneaky suspicion something is going on with
the drivers.

if you need further testing or have any suggestions of things to try i would be
more than happy to help out.

[Martin Pitt (pitti)]

Hi <email address hidden>!

(In reply to comment #69)
> to post some additional information, i have now tested a number of other
> distros, and every single one of them can access the usb port, only hoary and
> breezy cannot.

This bug is about an entirely different issue; can you please file a new bug
against 'linux' with your dmesg output? (The other logs are not required).

[Martin Pitt (pitti)]

(In reply to comment #63)
> New pmount had no effect, editing
> /usr/share/hal/fdi/preprobe/10osvendor/10-ide-drives.fdi solved the problem. By
> now looks like there is not any negative impact (and when I had it with older
> hal versions it was really noticeable) so I guess that fixes the problem

That is what upstream said as well. Thanks for the test.

> I will post here if later I notice negative impact.

Thanks! I close the bug for now since it is fixed in Dapper. I will reopen it if
any problem occurs.

> Only issue is that I had to restart nautilus for the icon to appear on the screen.

You have to restart your session after restarting hal, yes.

Thanks for testing!

[Johannes Hessellund (osos)]

(In reply to comment #71)
> Thanks! I close the bug for now since it is fixed in Dapper. I will reopen it if
> any problem occurs.

Will there be NO update/fix for Breezy ?
I have about 4 newbies I convinced to try Ubuntu, who has this problem. I had
this problem myself, but a reinstall helped, no clue why.
If the solution is at hand, why do we have to wait for Dapper?

[Martin Pitt (pitti)]

(In reply to comment #72)

> Will there be NO update/fix for Breezy ?

No, it is not a security or critical data loss bug. We do not fix normal bugs in
stable releases, the risk of disrupting things is too high.

> I have about 4 newbies I convinced to try Ubuntu, who has this problem.

Whoa, this type of CD-ROM drive seems to be quite common then...

> this problem myself, but a reinstall helped, no clue why.
> If the solution is at hand, why do we have to wait for Dapper?

You don't have to wait, you just have to do the configuration change manually.

[Scott Beamer (angrykeyboarder)]

(In reply to comment #18)
> (In reply to comment #17)
> > (In reply to comment #16)
> > > Alright, so anyone in the dev team confirm this bug? Or is this something
> > that will take months to fix?
> >
> > Fixing is usually easy after we know the source of the problem. This works fine
> > on all boxes I upgraded to hoary.
> >
> > Can you guys please do the steps described on the first half of
> >
> > http://wiki.ubuntu.com/DebuggingRemovableDevices
> >
> > and attach the logs here?
> >
> > Thanks!
>
> Can I just add that this isn't limited to removeable devices...the original
> poster was talking about an internal cd/dvd drive.
>
> Cheers,
> JohnT

How about a Kubuntu
 (In reply to comment #17)
> (In reply to comment #16)
> > Alright, so anyone in the dev team confirm this bug? Or is this something
> that will take months to fix?
>
> Fixing is usually easy after we know the source of the problem. This works fine
> on all boxes I upgraded to hoary.
>
> Can you guys please do the steps described on the first half of
>
> http://wiki.ubuntu.com/DebuggingRemovableDevices
>
> and attach the logs here?
>
> Thanks!

There are lovely instructions there for GNOME users. But what if you're using XFCE, Fluxbox or
(in my case) Kubuntu?

Needless to say, I'm having the same device issues as well. If this is not a critical bug it
certainly should be. My computer doesn't do me much good if I can't access my data....

[Scott Beamer (angrykeyboarder)]

Created an attachment (id=5269)
devices.txt

[Scott Beamer (angrykeyboarder)]

Created an attachment (id=5270)
dmesg.txt

[Scott Beamer (angrykeyboarder)]

Created an attachment (id=5271)
gvm.log

[Scott Beamer (angrykeyboarder)]

Created an attachment (id=5272)
hal.log

[Scott Beamer (angrykeyboarder)]

Created an attachment (id=5273)
lshal.txt

[Scott Beamer (angrykeyboarder)]

Created an attachment (id=5274)
lshal.txt

[MJo (mjo-iki)]

Nevermind, UI is just confusing trying to find: what was done for Breezy to fix this.