Brasero crashes with file name starting with %

[Hermann Kerr]

Binary package hint: brasero

Very similar to bug 307957. Brasero terminates when it encounters a file name beginning with % (which came off a Windows Partition) claiming there were duplicate files in the directory. Problem disappeared when I rename the file to a name without the %. The code obviously was cleverly written - plodding code would have worked better (I can say this from my personal experience of 30+ years in software development) - I dare say it is also the reason for bug 307957 as well.

OS: Ubuntu 9.10
Application: Brasero 2.28.2

ProblemType: Bug
Architecture: i386
Date: Mon Apr 26 08:53:24 2010
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/brasero
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
Package: brasero 2.28.2-0ubuntu1
ProcEnviron:
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-20.58-generic
SourcePackage: brasero
Uname: Linux 2.6.31-20-generic i686

[bbordwell (benbordwell)]

I am unable to reproduce this in lucid, perhaps it has already been fixed? If you could please confirm that you can not reproduce this bug in lucid (via livecd or upgrading) that would be great.

[Pedro Villavicencio (pedro)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a ".crash" file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

If you are using Ubuntu with the Gnome desktop environment - launch nautilus and navigate to your /var/crash directory and double click on the crash report you wish to submit.
If you are using Kubuntu or Xubuntu you can file the crash using /usr/share/apport/apport-qt --crash-file=/var/crash/_my_crash_report.crash in a terminal - where _my_crash_report.crash is the crash you would like to report.

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.