Bug 149126 - Disk will not eject properly shortly after ripping is conpleted
Summary: Disk will not eject properly shortly after ripping is conpleted
Status: RESOLVED WORKSFORME
Alias: None
Product: kaudiocreator
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Gerd Fleischer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-08-23 05:42 UTC by Jim
Modified: 2023-01-02 05:28 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jim 2007-08-23 05:42:47 UTC
Version:           1.13 (using KDE 3.5.6 "release 25" , openSUSE 10.3)
Compiler:          Target: i586-suse-linux
OS:                Linux (i686) release 2.6.21-rc5-git13-2-default

This bug shows up semi-frequently; enough to get me really upset.

If you push the eject button (on the CD drive) immediately after the last "Ripping" task is completed (from the jobs list), the disk does not eject properly.  Sometimes the tray will not open at all, sometimes it will open and close instantly.

If you wait a few minutes, drive control will be returned to the user (as it should be, even if there are still some tasks encoding), but it seems to take a disturbingly long period of time.

This problem *seems* to be more noticeable on slower machines, but maybe that's just me.
Comment 1 Richard Lärkäng 2007-08-23 12:27:25 UTC
Not really sure what the problem is, here I can eject the cd even while ripping.
What does "fuser -v /dev/cdrom" say when you can't eject the cd? (replace /dev/cdrom with the cd-device you are using)
Comment 2 Jim 2007-09-23 15:06:52 UTC
It opened and closed instantly (one of the bad conditions).

jimr@linux-rplh:~> fuser -v /dev/dvd

                     USER        PID ACCESS COMMAND
/dev/dvd:            jimr      22999 f.... kaudiocreator
                     jimr      23785 f.... kio_audiocd
                     jimr      24070 f.... lame

jimr@linux-rplh:~>
Comment 3 Andrew Crouthamel 2018-11-02 04:24:48 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Andrew Crouthamel 2018-11-16 02:35:10 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version?

Thank you for helping us make KDE software even better for everyone!
Comment 5 Justin Zobel 2022-12-03 09:01:35 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 6 Bug Janitor Service 2022-12-18 05:14:06 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 7 Bug Janitor Service 2023-01-02 05:28:01 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!