Bug 415554

Summary:	k3b refuses to burn an image it just created
Product:	[Applications] k3b	Reporter:	willkranz
Component:	Data Project	Assignee:	k3b developers <k3b>
Status:	RESOLVED NOT A BUG
Severity:	normal	CC:	aacid, michalm, trueg, willkranz
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description willkranz 2019-12-25 15:15:26 UTC

SUMMARY
k3b refuses to burn an image it just created.

STEPS TO REPRODUCE
1. run k3b software
2. select the image to burn from menu
3. k3b warns image is not in a standard format and refuses to burn

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: linux
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
The image is of a CD apparent created by '*EPSON Total disc Maker' as the string occurs near offset 0x10961 in image.  However this image does not appear to have the standard header at offset 0x8001, it just has the string "BEA01" which is followed by NULs.  Is there any override to allow a non-standard image?  If not I can probably re-write the image, but not sure what is being checked.  I can not find source code for this a SourceForge, is it available so I can remove the test which stops the burn?

Comment 1 Albert Astals Cid 2019-12-26 10:43:03 UTC

"I can not find source code for this a SourceForge"

You mean k3b? 

https://cgit.kde.org/k3b.git/

Comment 2 willkranz 2019-12-27 00:52:43 UTC

Will Kranz did a little more research.  Found source code for K3B at
https://sourceforge.net/projects/k3b/files/k3b/2.0.2/k3b-2.0.2.tar.bz2
This is C++ code that I am not fluent with, so I tried the simple fix
of writing the string "CD001" at offset 0x8001 in image file.
Once this has been done K3B is happy to burn the image.

I still consider this a bug,  I would like K3B to query if I want to proceed with the non-standard image rather the just dis-allowing a burn.  Oh well.

Comment 3 Albert Astals Cid 2019-12-27 16:55:21 UTC

Will kranz did terrible research if that's the tarball he found

Comment 4 willkranz 2019-12-29 23:12:02 UTC

(In reply to Albert Astals Cid from comment #3)
> Will kranz did terrible research if that's the tarball he found

thanks Albert that is less than helpful.  I have no interest in starting a flame war, but how about some constructive comments.

Comment 5 willkranz 2019-12-29 23:19:10 UTC

I did a little more of my 'terrible research' this morning.
I have been running K3B as root because I am a slob and often work as root.
K3B warns me running as root is not the best approach, but allows it.
If I select one of my non-standard images it warns:
  'Seems not to be a useable image'
and refuses to try to burn it.
Today I found that if I run as a normal user rather than root the warning does
not occur and apparently would proceed to burn the images.
This makes the issue seem even less important, but might be useful for some users to know.  I spent a couple frustrating days learning this.

Comment 6 Albert Astals Cid 2019-12-30 01:59:53 UTC

(In reply to willkranz from comment #4)
> (In reply to Albert Astals Cid from comment #3)
> > Will kranz did terrible research if that's the tarball he found
> 
> thanks Albert that is less than helpful.  I have no interest in starting a
> flame war, but how about some constructive comments.

I already gave you the url where the code is a few days ago that you decided to ignore it is your own fault, not much more i can do than that

Comment 7 Albert Astals Cid 2019-12-30 02:00:12 UTC

Anyhow, yes don't run k3b as root