cds still listed after being ejected (using the hardware button)

[robert marshall]

Prior to my upgrade from 13.04 to 13.10 if I inserted a cd the device notifier would pop up and I could take an action based on the system settings. Now nothing happens - if I start (say) k3b and it is an audio cd that will see the tracks and I can rip them without a problem. However the device notifier not picking up the event is annoying - and - I assume that is also the reason for a music player (eg amarok) not seeing the cd either.

I'm not sure which package this is - the probelm occurred (as I said) after the upgrade but I assume there's now a liblem with a libcd* package

lsb_release -rd
Description: Ubuntu 13.10
Release: 13.10

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: ubuntu-release-upgrader-core 1:0.205.4
ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10
Uname: Linux 3.11.0-15-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: i386
CrashDB: ubuntu
Date: Mon Feb 17 13:44:25 2014
InstallationDate: Installed on 2011-09-14 (887 days ago)
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
MarkForUpload: True
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
Symptom: ubuntu-release-upgrader
UpgradeStatus: Upgraded to saucy on 2013-11-05 (103 days ago)

[robert marshall (robert-capuchin)]

I think the problem is at a lower level than nautilus - I'm seeing the issue both with kde/plasma (my usual desktop) and with the standard ubuntu desktop. Unless nautilus handles the event in both cases?

I can't see the cd hardware in any of those attachments, here's part of the output of lshw:

    *-scsi:1
          physical id: 3
          logical name: scsi3
          capabilities: emulated
        *-cdrom
             description: DVD-RAM writer
             product: CDDVDW SH-S223C
             vendor: TSSTcorp
             physical id: 0.1.0
             bus info: scsi@3:0.1.0
             logical name: /dev/cdrom
             logical name: /dev/sr0
             version: SB06
             capabilities: removable audio cd-r cd-rw dvd dvd-r dvd-ram
             configuration: ansiversion=5 status=ready
           *-medium
                physical id: 0
                logical name: /dev/cdrom

[Sebastien Bacher (seb128)]

thank you for your bug report, It's more likely an udisks issue I guess then, could you run "udisksctl monitor", insert a CD and copy the output here?

[robert marshall (robert-capuchin)]

Here it is:

09:42:58.451: The udisks-daemon is running (name-owner :1.36).
09:43:12.768: /org/freedesktop/UDisks2/drives/Hitachi_HDT725032VLA380_VFJ201R8CLM5SX: org.freedesktop.UDisks2.Drive.Ata: Properties Changed
  SmartUpdated: 1392802992
09:43:12.914: /org/freedesktop/UDisks2/drives/ST3500413AS_Z2A01SJ1: org.freedesktop.UDisks2.Drive.Ata: Properties Changed
  SmartUpdated: 1392802992
09:43:25.837: /org/freedesktop/UDisks2/drives/TSSTcorp_CDDVDW_SH_S223C_R41368DB142613: org.freedesktop.UDisks2.Drive: Properties Changed
  TimeMediaDetected: 1392803005836174
  OpticalNumAudioTracks: 11
  OpticalNumTracks: 11
  OpticalNumSessions: 1
  Optical: true
  Media: optical_cd
  MediaCompatibility: optical_cd
                                optical_cd_r
                                optical_cd_rw
                                optical_dvd
                                optical_dvd_plus_r
                                optical_dvd_plus_r_dl
                                optical_dvd_plus_rw
                                optical_dvd_r
                                optical_dvd_ram
                                optical_dvd_rw
                                optical_mrw
                                optical_mrw_w
  MediaAvailable: true
  Size: 535554048
09:43:25.837: /org/freedesktop/UDisks2/block_devices/sr0: org.freedesktop.UDisks2.Block: Properties Changed
  Size: 535554048
  Symlinks: /dev/cdrom
                        /dev/disk/by-id/ata-TSSTcorp_CDDVDW_SH-S223C_R41368DB142613

[Sebastien Bacher (seb128)]

that seems fine to me, what happen if under an Unity session you run "gvfs-mount --monitor" and insert the CD?

[robert marshall (robert-capuchin)]

I get:
gvfs-mount --monitor
Monitoring events. Press Ctrl+C to quit.
Drive changed: 'TSSTcorp CDDVDW SH-S223C'
(and that's it)

Having tried that, I rebooted - after a kernel update of today - accidentally the cd was still in the drive - then logged into kde/plasma, ejected the audio cd (using eject from the command line) and inserted another audio cd- I wanted to try another cd and that worked!
gvfs-mount --monitor gave me
Drive changed: 'TSSTcorp CDDVDW SH-S223C'
Drive changed: 'TSSTcorp CDDVDW SH-S223C'
Drive changed: 'TSSTcorp CDDVDW SH-S223C'
Volume changed: 'Audio Disc'

(so a removal followed by an insertion) and the device notifier popped up saying a cd had been inserted!

However I then ejected that and tried inserting the previous one and that didn't work, went back to the one that previously worked and that now no longer pops up the device notifier - so now not working. I've tried a few other audio cds and they don't work either.

Is it that the first one after a reboot/login works and/or that the reboot/login happened with an audio cd in the drive?

[Sebastien Bacher (seb128)]

Renaming, it seems that the issue only happens if you press the CD drive button to eject (in which case the drive is still listed in the UI and blocks new insertions to be handled correctly)

[robert marshall (robert-capuchin)]

I'm not sure that description exactly fits the bug (as I see it here - the problem still there with 14.10)

After a reboot the system sees the cd - which was inserted before the reboot (ok).
On replacing that cd with another - if you use an eject facility either via an app or the command line command - the next cd is seen correctly (ok).
The next cd is not recognised - even if you eject using an app or cmd line eject - this buggy state of affairs then continues until the next reboot (not ok).

[Phillip Susi (psusi)]

Just to confirm, after you eject the cd using the physical button on the drive, the files on the now ejected cd still appear in a nautilus window? Can you run findmnt in a terminal at this time and post the output?

[robert marshall (robert-capuchin)]

So I ejected the cd using the physical button on the drive
Then fired up nautilus, it showed the cd as an icon but when I clicked on it the app redrew itself and instead showed my home directory - the cd icon disappearing.
I then ran findmnt (with no cd in the drive)
findmnt
TARGET SOURCE FSTYPE OPTIONS
/ /dev/disk/by-uuid/e4b277e5-8b4f-42af-bfca-4cc526cb829f
                                     ext3 rw,relatime,errors=remount-ro,data=ordered
├─/sys sysfs sysfs rw,nosuid,nodev,noexec,relatime
│ ├─/sys/fs/cgroup none tmpfs rw,relatime,size=4k,mode=755
│ │ └─/sys/fs/cgroup/systemd
                         systemd cgroup rw,nosuid,nodev,noexec,relatime,release_agent=/run/cgmanager/agents/cgm-re
│ ├─/sys/fs/fuse/connections
                         none fusectl rw,relatime
│ ├─/sys/kernel/debug none debugfs rw,relatime
│ ├─/sys/kernel/security none securityfs rw,relatime
│ └─/sys/fs/pstore none pstore rw,relatime
├─/proc proc proc rw,nosuid,nodev,noexec,relatime
│ └─/proc/sys/fs/binfmt_misc
                         binfmt_misc binfmt_misc rw,nosuid,nodev,noexec,relatime
├─/dev udev devtmpfs rw,relatime,size=2059200k,nr_inodes=208447,mode=755
│ └─/dev/pts devpts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000
├─/run tmpfs tmpfs rw,nosuid,noexec,relatime,size=414808k,mode=755
│ ├─/run/lock none tmpfs rw,nosuid,nodev,noexec,relatime,size=5120k
│ ├─/run/shm none tmpfs rw,nosuid,nodev,relatime
│ └─/run/user none tmpfs rw,nosuid,nodev,noexec,relatime,size=102400k,mode=755
├─/home /dev/sdb7 ext3 rw,relatime,data=ordered
├─/usr/local /dev/sdb5 ext3 rw,relatime,data=ordered
├─/var /dev/sda1 ext4 rw,relatime,data=ordered
└─/Backup /dev/sda2 ext3 rw,relatime,data=ordered

(as I comment in the note on 2014-11-06 I'm seeing the problem even when I use (for example) amarok to eject the cd. The next cd still doesn't get recognised)