| Summary: | "Burn image" consistently gives size mismatch error | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Frank Griffin <ftg> |
| Component: | RPM Packages | Assignee: | All Packagers <pkg-bugs> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | k3b | CVE: | |
| Status comment: | |||
|
Description
Frank Griffin
2017-03-15 15:33:20 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 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 ? 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? 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. 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 |