Brasero unable to read its own TOC file - writes faulty CD-text items

Bug #544981 reported by GNUbee40
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
brasero (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: brasero

Steps to reproduce the error:

Insert Audio CD from Artist "Speech" Title "Hoopla", length 1 hr 6 mins.
Start Brasero
Choose "Make 1:1 copy"
Choose either to burn an Image to a chosen location or use same drive as copying destination.

Expected:
Brasero burns an image either to /temp or to a chosen location.
Then either asks for an empty CD and burns the temporary image
or
Burns the saved image when the "Burn image" function is chosen.

The Reality:
Either way, Brasero creates the images without errors, but when proceeding to burn them:
Error: The TOC file could not be found

Will attach the session log.
One of the errors repeatedly occuring in the log:
BraseroCdrdao stderr: ERROR: /home/nino/brasero.toc:45: Invalid CD-TEXT item for a track.
These lines contain The item Disc_ID=""

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/brasero
Package: brasero 2.26.1-0ubuntu1
ProcEnviron:
 LANG=da_DK.UTF-8
 SHELL=/bin/bash
SourcePackage: brasero
Uname: Linux 2.6.28-18-generic i686

Revision history for this message
GNUbee40 (docnino) wrote :
Revision history for this message
GNUbee40 (docnino) wrote :
Revision history for this message
GNUbee40 (docnino) wrote :

After removing the lines containing the invalid CD_Tekst items from the TOC file the image will burn without problems.
But ideally these invalid tags should not be created at all.

GNUbee40 (docnino)
description: updated
summary: - Brasero unable to read its own TOC file
+ Brasero unable to read its own TOC file - writes faulty CD-text items
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for the report, could you please try the same with Lucid and tell us if you get the same there? Thanks in advance.

Changed in brasero (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.