After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 358146 - Freezes when removing cd during playback
Freezes when removing cd during playback
Status: RESOLVED DUPLICATE of bug 94289
Product: rhythmbox
Classification: Other
Component: general
0.9.5
Other Linux
: Normal normal
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-09-28 15:58 UTC by Sven Arvidsson
Modified: 2006-10-02 02:01 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Sven Arvidsson 2006-09-28 15:58:14 UTC 
This was reported to the Debian BTS.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=385528

From the Debian report:

"When playing a cd rhythmbox neight monitors the drive for disc removal
nor does it lock the drive. So removing the disc leads to scsi_read
errors and rhythmbox gets unusable.

On the commandline this is printed:

scsi_read error: sector=1426 length=3 retry=2
                 Sense key: 2 ASC: 3a ASCQ: 0
                 Transport error: Device busy
                 System error: Das  Gerät oder die Ressource ist belegt


Steps to reproduce:
1. start rhythmbox
2. insert a cd
3. play CD
4. remove CD"


I don't see the scsi read errors, but I can confirm that Rhythmbox seems to freeze when the playing cd is removed. However, if it's replaced, Rb resumes functioning.
Comment 1 Jonathan Matthew 2006-09-28 21:10:28 UTC 
This works properly if you use the libcdio CDDA source element, rather than the cdparanoia source element.  Unfortunately the cdparanoia source has a higher rank (128) than the libcdio source (127).
Comment 2 James "Doc" Livingston 2006-10-02 02:01:19 UTC 
This is a problem with libcdparanoia itself, and is unlikely to ever get fixed. As Jonathan mentioned the libcdio element doesn't suffer this problem - but AFAIK it doesn't do the extensive paranoia checks yet.

*** This bug has been marked as a duplicate of 94289 ***