Bug 20490 - "Burn image" consistently gives size mismatch error
Summary: "Burn image" consistently gives size mismatch error
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: All Packagers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-03-15 15:33 CET by Frank Griffin
Modified: 2017-03-16 18:08 CET (History)
0 users

See Also:
Source RPM: k3b
CVE:
Status comment:


Attachments

Description Frank Griffin 2017-03-15 15:33:20 CET
Whenever you try to burn an ISO image with k3b, you get a popup saying that the size of the image doesn't match the size in the ISO header.  You have the option to continue anyway, and if you do so the burn seems to work fine.

I've only started using k3b again recently, but I recall this happening quite a while ago as well.
Comment 1 Rémi Verschelde 2017-03-15 15:36:23 CET
Does this happen with all images, or only specific ones?

Could you try maybe with a Mageia 6 sta2 ISO if you have one, after having checked its md5sum?

Assignee: bugsquad => pkg-bugs

Comment 2 Frank Griffin 2017-03-15 15:58:35 CET
It's hard to see a pattern, because I only go back and check if there's a playback error after the fact, and I assume that the disk blank would have had to have a defect to start with, which would be random.  It definitely doesn't happen with all images.

Generally, by the time I try to use the disk for playback, I've deleted the ISO from harddisk.  I can try running a dd or a cmp after each burn, but what would I look for if I did get a failure ?
Comment 3 Rémi Verschelde 2017-03-15 16:05:04 CET
Well you mentioned that it gives a size mismatch error popup when you try to burn, so I guess you still have the ISO at hand at that time no? Maybe you confused this bug with bug 20491?
Comment 4 Frank Griffin 2017-03-15 16:37:15 CET
Yes, sorry, I did confuse the two.

The popup from k3b occurs with every image I try.  When brasero started exhibiting the problem in bug#20491, I switched to using k3b and noticed that the popup was still happening.

I'll try with the MGA ISO.
Comment 5 Frank Griffin 2017-03-16 18:08:30 CET
Doesn't happen with the MGA ISO or others not produced by the particular ripper I was using, so it must be a bug in that.

Status: NEW => RESOLVED
Resolution: (none) => INVALID


Note You need to log in before you can comment on or make changes to this bug.