gnomebaker crashed with SIGSEGV in g_slice_free1()

Bug #261227 reported by Pavel Mlčoch
8
Affects Status Importance Assigned to Milestone
gnomebaker (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: gnomebaker

crash when I add files to second audio CD

ProblemType: Crash
Architecture: i386
CrashCounter: 1
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/gnomebaker
Package: gnomebaker 0.6.4-1
ProcAttrCurrent: unconfined
ProcCmdline: gnomebaker
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/opt/thinlinc/bin
 LANG=cs_CZ.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: gnomebaker
StacktraceTop:
 ?? () from /usr/lib/libglib-2.0.so.0
 ?? () from /usr/lib/libglib-2.0.so.0
 g_slice_free1 () from /usr/lib/libglib-2.0.so.0
 gdk_region_destroy () from /usr/lib/libgdk-x11-2.0.so.0
 ?? () from /usr/lib/libgdk-x11-2.0.so.0
Title: gnomebaker crashed with SIGSEGV in g_slice_free1()
Uname: Linux 2.6.26-5-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin mythtv plugdev sambashare tty vboxusers video

Revision history for this message
Pavel Mlčoch (pavkamlc) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? () from /usr/lib/libglib-2.0.so.0
?? () from /usr/lib/libglib-2.0.so.0
g_slice_free1 () from /usr/lib/libglib-2.0.so.0
IA__gdk_region_destroy (region=0x984b500) at /build/buildd/gtk+2.0-2.13.6/gdk/gdkregion-generic.c:340
queue_item_free (item=0x97b7f80) at /build/buildd/gtk+2.0-2.13.6/gdk/x11/gdkgeometry-x11.c:983

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a valgrind log following the instructions at https://wiki.ubuntu.com/Valgrind and attach the file to the bug report. This will greatly help us in tracking down your problem.

Changed in gnomebaker:
importance: Undecided → Medium
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 gnomebaker:
status: Incomplete → Invalid
Revision history for this message
Pavel Mlčoch (pavkamlc) wrote :

I've tried today and seems to can be close this bug.

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.