Bug 238896

Summary: K3B burning corrupted bootable discs, three times in a row.
Product: [Applications] k3b Reporter: Nuclear Peon <peon.developments>
Component: Burning/HardwareAssignee: k3b developers <k3b>
Status: RESOLVED WORKSFORME    
Severity: normal CC: trueg
Priority: NOR    
Version: 1.91.0   
Target Milestone: ---   
Platform: Gentoo Packages   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Nuclear Peon 2010-05-26 16:18:42 UTC 
Version:           1.91.0 (using KDE 4.4.3) 
OS:                Linux

Burning (k)ubuntu iso's and installing them on an old desktop reveals corrupted files when running the cd check utility as well as problems cropping up when installed.

Reproducible: Always

Steps to Reproduce:
Insert blank cdrom into drive on laptop
Launch K3B and use "Burn Image" in toolbar
Select ubuntu-server-i386.iso
Click Burn button
Once cd is finished, insert into desktop cdrom drive
Select check disc for errors

Actual Results:  
I get a red screen saying that a package md5sum is incorrect and cd may possibly be corrupted

Expected Results:  
No errors in cd check

This is the first time I've burnt cd's since upgrading to the 1.91.0 version on Gentoo. I've selected burn speed to run at 4x (slowest selectable speed) to prevent errors, as well as verify data option.

Burnt 3 different cd's with the same issue: after installing from cd burnt in k3b, errors occured with packages upon cd check and strange behaviour after installation, such as not being able to log in. Have burnt (k)ubuntu and other bootable cd's successfully on this installation before using previous versions.

I looked at the Gentoo bug tracker and saw no open bugs that would relate to this issue. Downloaded the ubuntu server iso from official website and md5sum is the same. Compiled with -O2 and -j3 options. Burnt from Lenovo T60 thinkpad. Using kde overlay, which may incorporate unstable components of kde. I'm reporting this bug for the sake of reporting behaviour, not because I'm asking for a fix. If others report this issue, you'll know that something fishy is possibly in this release. 
Perhaps it's a ubuntu/kubuntu issue. Feel free to mark this bug as invalid.
Comment 1 Andrew Crouthamel 2018-11-12 02:55:46 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:45:07 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-13 01:36:04 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-28 05:07:47 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-12 03:49:57 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!