BTW, the broken hardware eject button is covered in bug 397734, should be well within the karmic range.
The first thing that caught my eye is that the CD media capabilities are misdetected. It claims that it's a DVD-RAM, and whatnot. However, it does that here as well, so this is apparently not the reason. I filed that as bug 439701 to not forget about it.
The more interesting difference between my system (where everything works) and your's is that udev does not detect the file system type. For me it says
BTW, the broken hardware eject button is covered in bug 397734, should be well within the karmic range.
The first thing that caught my eye is that the CD media capabilities are misdetected. It claims that it's a DVD-RAM, and whatnot. However, it does that here as well, so this is apparently not the reason. I filed that as bug 439701 to not forget about it.
The more interesting difference between my system (where everything works) and your's is that udev does not detect the file system type. For me it says
ID_FS_LABEL= Ubuntu_ 9.04_amd64 ENC=Ubuntu\ x209.04\ x20amd64 filesystem
ID_FS_LABEL_
ID_FS_TYPE=iso9660
ID_FS_USAGE=
This is completely missing for you, and consequently the higher levels don't consider it as an automountable volume.
Can you please run some further tests to track this down?
When booting without a CD-ROM in the drive (i. e. broken autodetection), please insert that CD again, and copy&paste the output of
blkid -p /dev/cdrom
sudo mount /dev/cdrom /mnt
After that, please attach /var/log/kern.log (you forgot the previous time, but I'd like to check it if the kernel detected some anomalies).
Thanks!