Optical media does not automount

[Onkar Shinde]

Binary package hint: udev

I have recently updated my ibook G4 (powerpc) laptop to karmic. Since then optical media does not mount automatically. The problem is seen with DVD as well CD.

ProblemType: Bug
Architecture: powerpc
CustomUdevRuleFiles: 85-pbbuttonsd.rules
Date: Sun Nov 15 21:17:48 2009
DistroRelease: Ubuntu 9.10
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Package: udev 147~-6.1
ProcCmdLine: root=/dev/hda6 ro quiet
ProcEnviron:
 LANG=en_IN
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-powerpc
SourcePackage: udev
Uname: Linux 2.6.31-14-powerpc ppc

[WeatherGod (ben-v-root)]

I am not certain if this is udev, as it appears that the device is recognized. It appears to be having trouble communicating with the drive, which prevents the automount. Has this drive worked in earlier versions of Ubuntu?

[Onkar Shinde (onkarshinde)]

Yes it has worked in gutsy, hardy, intrepid and jaunty.
In fact there is no trouble mounting the drive manually. I can do that as normal user since /etc/fstab contains 'user' option. It is just auto mounting that does not work.

[Scott James Remnant (Canonical) (canonical-scott)]

This could well be a hardware problem, or a kernel driver issue

[WeatherGod (ben-v-root)]

Onkar, it is very curious that the manual command works but not the automount. It makes me suspect that this is a device-kit issue, though, not a udev issue. I am not entirely certain, though.

[Onkar Shinde (onkarshinde)]

Scott,

Can you please explain how this could be a hardware or kernel driver issue?

[Onkar Shinde (onkarshinde)]

Adding devicekit-disks task until it is clear whose fault it is.

[Martin Pitt (pitti)]

Thank you for taking the time to report this bug and trying to help make Ubuntu better. Unfortuately this report does not contain enough information for the developers to fix it. Can you please run "ubuntu-bug storage" in a situation where you can reproduce the problem and follow the interactive dialogs? This will collect all the useful logs which we need to track this problem.

Since this will create a new bug report, I am closing this one. Thank you!