Bug 23691 - Burning with USB drive fails when using k3b, but doing the same with XFBurn works fine
Summary: Burning with USB drive fails when using k3b, but doing the same with XFBurn w...
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: KDE maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-10-14 14:57 CEST by Frank Griffin
Modified: 2021-05-17 01:15 CEST (History)
1 user (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Frank Griffin 2018-10-14 14:57:09 CEST 
This seems related to a revious bug I reorted and closed as hardware ( https://bugs.mageia.org/show_bug.cgi?id=23236 ), but that was a while back and this is still happening.

k3b has been burning just fine on my desktop system with an internal DVD burner.  However, using an external USB burner on my laptop, it fails immediately claiming it can't write the first sector.

If I restart the burn with the same drive and blank using XFBurn, it works perfectly.  So two things are obvious: whatever k3b is doing t never gets to the point of physically corupting the blank, and k3b is misreading completion status from a usb drive and seeing errors where none exist.
Marja Van Waes 2018-10-16 19:58:08 CEST

Assignee: bugsquad => kde
Summary: Burning fails with USB drive => Burning with USB drive fails when using k3b, but doing the same with XFBurn works fine
CC: (none) => marja11

Comment 1 Aurelien Oudelet 2021-05-17 01:15:35 CEST 
Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.

Closing as OLD.

Resolution: (none) => OLD
Status: NEW => RESOLVED
Note You need to log in before you can comment on or make changes to this bug.