brasero crashed with SIGSEGV in brasero_data_project_remove_node()

Bug #290384 reported by Michael Nagel
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
brasero (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: brasero

i was starting up brasero (no user interaction yet) when the crash happened

ProblemType: Crash
Architecture: i386
Date: Tue Oct 28 18:50:34 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/brasero
NonfreeKernelModules: fglrx
Package: brasero 0.8.1-0ubuntu2~hardy1
PackageArchitecture: i386
ProcCmdline: brasero
ProcEnviron:
 LC_TIME=de_DE.UTF-8
 PATH=/home/username/sysarch/bin:/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/zsh
 LC_PAPER=de_DE.UTF-8
Signal: 11
SourcePackage: brasero
StacktraceTop:
 brasero_data_project_remove_node ()
 ?? ()
 ?? ()
 ?? () from /usr/lib/libglib-2.0.so.0
 g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
Title: brasero crashed with SIGSEGV in brasero_data_project_remove_node()
Uname: Linux 2.6.24-20-386 i686
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin plugdev scanner tape vboxusers video www-data

Revision history for this message
Michael Nagel (nailor) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:brasero_split_dialog_metadata_finished_cb (metadata=0x8202c80, error=0x0,
?? ()
?? ()
?? ()
?? ()

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
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
Michael Nagel (nailor) wrote :

sorry, but i will not be able to supply a backtrace. feel free to close this bug if it is necessary.

Revision history for this message
Michael Nagel (nailor) 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:
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.