After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 614021 - Create audio CD fails just before writing to disk
Create audio CD fails just before writing to disk
Status: RESOLVED DUPLICATE of bug 617494
Product: brasero
Classification: Applications
Component: libbrasero-burn
2.29.x
Other Linux
: Normal normal
: 2.26
Assigned To: Brasero maintainer(s)
Brasero maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2010-03-26 15:44 UTC by Ben
Modified: 2010-05-22 07:42 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
log file from unsuccseful burn (116.00 KB, text/x-log)
2010-03-26 15:46 UTC, Ben 		Details
burn debug (94.15 KB, text/plain)
2010-04-29 17:27 UTC, Ben 		Details

Description Ben 2010-03-26 15:44:55 UTC 
I am forwarding this bug from downstream (https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/546655)

I was able to work around this issue by selecting burn to image, and then burning the image to the disk.
Comment 1 Ben 2010-03-26 15:46:05 UTC 
Created attachment 157182 [details]
log file from unsuccseful burn
Comment 2 Sebastien Bacher 2010-04-28 21:18:18 UTC 
https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/571021 has a video which
shows the issue on
http://launchpadlibrarian.net/45836596/brasero-notburning-jcastro.ogv

https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/555485 seems to indicate
recording video cds has the issue

would extra debug informations be useful there? having the default GNOME CD
recording software being able to record audio or video cds again would be nice,
not sure if anybody is reading the brasero bugs atm though
Comment 3 Ben 2010-04-29 17:27:36 UTC 
Created attachment 159917 [details]
burn debug
Comment 4 Philippe Rouquier 2010-05-22 07:42:29 UTC 
Thanks for reporting the bug. This has been fixed in master and stable for next release.

*** This bug has been marked as a duplicate of bug 617494 ***