Bug 238943 - K3B selects last ISO used when error is detected with selected ISO
Summary: K3B selects last ISO used when error is detected with selected ISO
Status: RESOLVED WORKSFORME
Alias: None
Product: k3b
Classification: Applications
Component: GUI/Usability (show other bugs)
Version: 1.92.0
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: k3b developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-26 23:35 UTC by Steve Morrissey
Modified: 2023-02-03 05:02 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 Steve Morrissey 2010-05-26 23:35:15 UTC
Version:           1.92.0 (using KDE 4.4.3) 
OS:                Linux

Using the KDE Actions right click menu on an ISO you can select to use K3B to write the image to a disc. This works unless there is an issue with the ISO, in which K3B will fall back to the last successfully burned image and bring up the burn prompt with the old image loaded in and no error message displayed. To get the error message to show you need to use the Browse button from within the burn dialog, select the bad ISO, and then you will see the error.

Reproducible: Always

Steps to Reproduce:
1. Select an ISO from your hard drive, right click, actions, burn image using K3B
2. Successfully write ISO to disc
3. Right click on a bad ISO while leaving K3B open and select actions, burn image using K3B
4. The selected ISO to burn will be the last ISO that was successfully burned and will not show an error message indiciating why it can't burn the desired ISO
5. Use the browse button to select the ISO from within K3B
6. The error message appears (that should have showed up after step 3)

Actual Results:  
The old ISO was queued for burning, again.

Expected Results:  
An error message indicating why the bad ISO couldn't be burned. The last successful ISO shouldn't be loaded up.
Comment 1 Andrew Crouthamel 2018-11-12 02:44:15 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:28:19 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-04 07:05:15 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-19 05:12:49 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-03 05:02:37 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!