brasero crashed with SIGSEGV in g_signal_emit_valist()

Bug #381027 reported by LCID Fire
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

When clicking on the list of files it crashed

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/brasero
Package: brasero 2.26.1-0ubuntu1
ProcCmdline: brasero
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: brasero
StacktraceTop:
 ?? () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_signal_emit_valist ()
 g_signal_emit_by_name ()
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
Title: brasero crashed with SIGSEGV in g_signal_emit_valist()
Uname: Linux 2.6.28-11-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev pulse-rt sambashare

Revision history for this message
LCID Fire (lcid-fire) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:boxed_nodes_cmp (p1=0x7fffd47d4eb0, p2=0x6b41c68)
boxed_proxy_collect_value (value=0x7fffac026b08,
IA__g_signal_emit_valist (instance=0xdae000,
IA__g_signal_emit_by_name (instance=0xdae000,
_gtk_size_group_compute_requisition (

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in brasero (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for the report, in which list of files? may you tell us a few easy steps in order to recreate the crash? looks like a crash inside gtk.

Changed in brasero (Ubuntu):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
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.