By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.
Bug 96 - KDE takes forever to acknowledge an audio CD
Summary: KDE takes forever to acknowledge an audio CD
Status: RESOLVED WONTFIX
Alias: None
Product: TDE
Classification: Unclassified
Component: other (any) (show other bugs)
Version: 3.5.10
Hardware: i386 Linux
: P5 normal
Assignee: Timothy Pearson
URL:
Depends on:
Blocks:
 
Reported: 2009-06-02 14:57 CDT by Vanessa Ezekowitz
Modified: 2012-11-19 16:18 CST (History)
2 users (show)

See Also:
Compiler Version:
TDE Version String:
Application Version:
Application Name:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Vanessa Ezekowitz 2009-06-02 14:57:16 CDT 
Using Jaunty in a KDE 3.5.10 session...

When I insert an audio CD, it takes *forever* for KDE to acknowledge it after the drive examines it.  What I mean is, the drive light comes on, reads for a few seconds, then goes out.  It then takes a very long time, even on a disc I *just* burned, before KDE finally displays the "What shall I do with this disc?" dialog.  Inserting a data DVD is far faster: after the drive reads the disk, it only takes one or two seconds to get that popup.

While I'm waiting for the audio CD dialog, I am unable to eject the disk - my attempts to eject via the button appear to be ignored.  If I wait long enough, however (30 to 60 seconds, I'd say), KDE finally displays the popup AND ejects the disc.

Is there something in the system that could be grabbing the audio CD and interfering with KDE's general access to it?  Amarok and K3B can do this, but I had shut both down before testing this.
Comment 1 Darrell 2012-11-19 16:18:59 CST 
Closing as won't fix because this report was written more than three years ago against KDE 3.5.10, the original reporter Vanessa has provided no follow-up, and nobody else has reported the same problem in subsequent versions of Trinity.

If the original reporter Vanessa can still replicate this bug then please reopen the report. :)