Burning CD/DVD, starvation, doesn't use burn-proof

Bug #72886 reported by Timothy Miller
Affects Status Importance Assigned to Milestone
k3b (Ubuntu)

Bug Description

Binary package hint: k3b

If I'm burning a CD or DVD using k3b, and something happens that requires a lot of disk of CPU access, k3b does nothing to recover.

First problem: k3b isn't given enough priority to prevent starvation.

So while burning a disc, I decided to start some other program. Stupid thing to do? Maybe, but k3b should have recovered. Instead, the drive itself quit burning.

Second problem: k3b doesn't notice that the drive quit and "keeps going" with the progress meter going along as though nothing happened.

So, the burn-proof option is useless to k3b because it never recognizes when a problem has occurred.

Naturally, during verify, the disc was found to be corrupt.

Revision history for this message
Someone (s4910321931-deactivatedaccount) wrote :

What burner do you use?

Revision history for this message
Timothy Miller (theosib) wrote :
Revision history for this message
Peter Cordes (peter-cordes) wrote :

newegg doesn't sell that item number anymore. Better to give a model number.

 Have you had this happen with CDs and DVDs? I thought DVDs were smarter about recovering, and were supposed to be able to. It didn't take a special feature like "burn proof".

 I'm not sure if I've ever had a buffer underrun while burning, but I think so, and my discs come out ok. (I've sometimes seen single-bit errors on them, though, which is why I always make par2 files to put on the disc with the files. This is easy if its a few big files, which is what I'm always burning.)

Revision history for this message
Daniel T Chen (crimsun) wrote :

One can work around this issue by making wodim setuid (not recommended in the general case) or by burning at a slower speed.

Changed in k3b:
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
Maarten Bezemer (veger) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running apport-collect 72886 and any other logs that are relevant for this particular issue.

Changed in k3b (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for k3b (Ubuntu) because there has been no activity for 60 days.]

Changed in k3b (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers