Bug 487215 - Crashes when ejecting a disc with read errors
Summary: Crashes when ejecting a disc with read errors
Status: RESOLVED WORKSFORME
Alias: None
Product: k3b
Classification: Applications
Component: Data Project (show other bugs)
Version: 24.04.90
Platform: Slackware Linux
: NOR crash
Target Milestone: ---
Assignee: k3b developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-05-19 01:54 UTC by Henry Pfeil
Modified: 2024-06-18 03:47 UTC (History)
3 users (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 Henry Pfeil 2024-05-19 01:54:25 UTC
***
If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

SUMMARY
I'm digitizing all of my CDs/DVDs because bit rot has damaged a dozen or so discs so far. 

STEPS TO REPRODUCE
1. Copy medium. Only create image. Begin copying the disc to iso.
2. Things proceed as advertised until k3b starts throwing read errors.
3. Eject the bad disc, either from the menu, or press the eject button.

OBSERVED RESULT
K3b crashes, a bug report pops up

EXPECTED RESULT
Produce an iso image like the hundreds of correct discs already digitized.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
KDE Plasma Version: 5.27.11
KDE Frameworks Version: 5.115.0
Qt Version: 5.15.13

ADDITIONAL INFORMATION
I tried submitting a bug report, but they always hang trying to log in.
Comment 1 Albert Astals Cid 2024-05-19 09:19:55 UTC
If you report a crash it needs to have crash information https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
Comment 2 Bug Janitor Service 2024-06-03 03:45:50 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 3 Bug Janitor Service 2024-06-18 03:47:05 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!