Ubuntu
brasero package

Brasero doesn't set working directory properly when launched from Nautilus; fails with "cue file appears to be invalid"

Bug #278903 reported by Scott Ritchie on 2008-10-06

Affects		Status	Importance	Assigned to	Milestone
	Brasero	Fix Released	Low	gnome-bugs #563204
	brasero (Ubuntu)	Invalid	Low	Ubuntu Desktop Bugs

Bug Description

Binary package hint: brasero

If I open a .cue file in nautilus (double click, right click->open with brasero), and then attempt to burn, Brasero will fail and claim that the .cue file is invalid as though the .bin file it was pointing to did not exist.

If I navigate to that .cue file in the terminal and then open it using brasero foo.cue, everything works as expected.

This is Hardy with Brasero 0.8.1-0ubuntu2~hardy1

Scott Ritchie (scottritchie) on 2008-10-09

Changed in brasero:
status:	New → Confirmed

Pedro Villavicencio (pedro) on 2008-10-10

Changed in brasero:
assignee:	nobody → desktop-bugs
importance:	Undecided → Low
status:	Confirmed → Triaged

Bug Watch Updater (bug-watch-updater) on 2008-10-10

Changed in brasero:
status:	Unknown → New

Bug Watch Updater (bug-watch-updater) on 2009-01-29

Changed in brasero:
status:	New → Invalid

Scott Ritchie (scottritchie) on 2009-01-29

Changed in brasero:
status:	Invalid → Unknown

Bug Watch Updater (bug-watch-updater) on 2009-01-30

Changed in brasero:
status:	Unknown → Incomplete

Bug Watch Updater (bug-watch-updater) on 2009-07-16

Changed in brasero:
status:	Incomplete → Fix Released

Revision history for this message

Chris Coulson (chrisccoulson) wrote on 2009-08-13:

Could someone experiencing this issue please try and test if it still happens in Jaunty or Karmic? This is something that should be reproducible from a live CD.

Thanks

Changed in brasero (Ubuntu):
status:	Triaged → Incomplete

Revision history for this message

Robert Ancell (robert-ancell) wrote on 2009-11-05:

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!