Bug 327578 - K3B does not recognize new media after one CD burn.
Summary: K3B does not recognize new media after one CD burn.
Status: RESOLVED WORKSFORME
Alias: None
Product: k3b
Classification: Applications
Component: Burning/Hardware (show other bugs)
Version: 2.0.2
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: k3b developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-11-13 20:36 UTC by Charlie
Modified: 2023-02-11 03:52 UTC (History)
1 user (show)

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 Charlie 2013-11-13 20:36:39 UTC
I burned one CD and now I cannot get K3B to recognize there is media in the burner drive. I've even rebooted the system (MS Windows solution), restarted user session, all to no avail. I've tried various methods to eject and/or umount, re-insert blank CDs and nothing. I've tried a couple different brand disks and sizes - still nothing. I am running OpenSuSe 12.1 on a laptop and am trying to burn the 12.3 network install CD in order to upgrade all systems. The drive plays everything OK so it's not the mechanics or electronics. 

Reproducible: Always

Steps to Reproduce:
1. Click on .iso with Dolphin or from K3B  selector menu.
2. K3B calculates the MD5 checksum, then leaves the [Start] button greyed out and the message Please insert empty medium.
3.
Actual Results:  
Nothing... I am not allowed to proceed to the burn.

Expected Results:  
Duh?
Comment 1 Andrew Crouthamel 2018-11-12 02:53:04 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 2 Andrew Crouthamel 2018-11-21 04:43:41 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? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Justin Zobel 2023-01-12 01:57:49 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 4 Bug Janitor Service 2023-01-27 05:07:39 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 5 Bug Janitor Service 2023-02-11 03:52:20 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!