Bug 296037

Summary:	Strange speed reporting.
Product:	[Applications] k3b	Reporter:	Dane <dmutters>
Component:	Burning/Hardware	Assignee:	k3b developers <k3b>
Status:	RESOLVED WORKSFORME
Severity:	minor	CC:	aacid, trueg
Priority:	NOR
Version:	2.0.2
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	Screenshot of k3b in-program log

Description Dane 2012-03-15 05:33:28 UTC

I just tried burning the Linux Mint 12 KDE/64-bit ISO to a single-layer DVD-R disc, using my ATAPI iHAS124 Y DVD/CD-RW burner.  The log had a really weird message (see screenshot) about being unable to burn at 16x, so switching to 17x. 

The messages in the log just strike me as being really weird; if it can't burn at 16x, why should it work at 17x?  In point of fact, my burner can manage around 24x.  I'm writing this report mainly to reduce the befuddlement of future users.

 It may or may not be relevant, but the DVD failed a md5sum using the more reliable method I've tried: "dd if=<device> bs=2048 count=xxxxxx conv=notrunc,noerror,sync |md5sum".  It got a correct sum, however, by just doing "md5sum <device>"--which almost never works.

Let me know if you need anymore information.

Thanks for your time.

Comment 1 Dane 2012-03-15 05:34:56 UTC

Created attachment 69632 [details]
Screenshot of k3b in-program log

Comment 2 Andrew Crouthamel 2018-11-12 02:56:09 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 3 Andrew Crouthamel 2018-11-21 04:43:04 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 4 Dane 2018-11-22 05:10:20 UTC

I no longer have any of the hardware, or the ISO that were being used when this bug was discovered, so I'm unable to test whether the problem still exists.

Comment 5 Justin Zobel 2023-01-18 02:41:20 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 2023-02-02 05:00:31 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 Dane 2023-02-02 08:52:22 UTC

I recently tested with k3b 21.12.3 and didn't experience any problems.  However, I'm using different hardware, a different ISO image, different media, and different operating system software than I was in 2012, so this might not be a valid test.  If nobody else is having the problem, maybe that's good enough to close the bug.  Your call.