brasero crashes when trying to burn a file with a "#" in its name

Bug #307957 reported by Charon
10
Affects Status Importance Assigned to Milestone
brasero (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: brasero

This happens to me on:
Ubuntu 8.10

Package Version is:
0.8.2-0ubuntu1

I expected:
Brasero to burn a CD.

What happened:
When you try to burn a data-cd with a file on it which has a filename containing a "#" brasero quits with a segmentation fault.

Steps to reproduce :
1. create a new data-project
2. add the file "test #555.txt" (i attached it to this bug-report. you may try a different file with a "#" in its name since it originally crashed on me due to a different file)
3. click on the burn-button in the lower right corner of brasero
4. you may either chose your cd-burner or an image-file as the destination. its crashes with both (originally chrashed on me during burning a cd. can be reproduced with an image-file though). makes no difference if you change any of the other options here.
5. click the burn-button, it will crash immediately and you don't know where during the burn process. if this was one file out of many you want to burn you will see that it crashes during the creation of the checksum for the image-file.

A few of these guidelines to recreate the bug may be a bit off since i am doing this in a german environment and don't know the proper english terms.

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/brasero
NonfreeKernelModules: nvidia
Package: brasero 0.8.2-0ubuntu1
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: brasero
Uname: Linux 2.6.27-9-generic i686

Tags: apport-bug
Revision history for this message
Charon (markus-lobedann) wrote :
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

Changed in brasero:
assignee: nobody → desktop-bugs
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Charon (markus-lobedann) wrote :
Revision history for this message
Charon (markus-lobedann) wrote :
Revision history for this message
Charon (markus-lobedann) wrote :

I created both a backtrace and a valgrind log like described in your link and can run strace if you want me to.
~/.xsession-errors showed nothing during the program crash.

Thanks for your help
Markus

Revision history for this message
Jerome (seide) wrote :

I have exactly the same problem (although I understood it came from the "#" only by reading this thread): I tried to burn a DVD with many files, one of them having a "#" in its name, and brasero crashed after having completed the chesksum of the files to burn (I wonder why he computes such a checksum since there is no original md5sum to compare to).

I am willing to test the next version of brasero (all the more that I have another - slight, this time - bug with the CD burned using brasero 0.8.2), but on the contrary to what is said on this website, brasero 0.9.1 is not available in the intrepid-backports...

Revision history for this message
Andreas Moog (ampelbein) wrote :

Version 0.9.1 should be available in the repositories by now, can you try with that version? I just tried version 2.26.0 and the issue is fixed there.

Revision history for this message
Robert Ancell (robert-ancell) 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.