brasero crashed with SIGSEGV in g_slice_alloc()

[Nicolò Chieffo]

I think this crash was caused after renaming a directory (from nautilus) which was added in the brasero current project

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: brasero 3.0.0-1ubuntu4
ProcVersionSignature: Ubuntu 3.0.0-9.14-generic 3.0.3
Uname: Linux 3.0.0-9-generic x86_64
Architecture: amd64
Date: Mon Aug 29 21:29:51 2011
ExecutablePath: /usr/bin/brasero
ProcCmdline: brasero
SegvAnalysis:
 Segfault happened at: 0x7f85671345a5 <g_slice_alloc+293>: mov (%rbx),%rdx
 PC (0x7f85671345a5) ok
 source "(%rbx)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%rdx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: brasero
StacktraceTop:
 g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_slice_alloc0 () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/libgtk-3.so.0
 gtk_style_properties_merge () from /usr/lib/libgtk-3.so.0
 ?? () from /usr/lib/libgtk-3.so.0
Title: brasero crashed with SIGSEGV in g_slice_alloc()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:
 magazine_chain_pop_head (magazine_chunks=0x17aa850) at /build/buildd/glib2.0-2.29.16/./glib/gslice.c:492
 thread_memory_magazine1_alloc (ix=<optimized out>, tmem=<optimized out>) at /build/buildd/glib2.0-2.29.16/./glib/gslice.c:795
 g_slice_alloc (mem_size=8) at /build/buildd/glib2.0-2.29.16/./glib/gslice.c:833
 g_slice_alloc0 (mem_size=8) at /build/buildd/glib2.0-2.29.16/./glib/gslice.c:854
 property_data_new () at /build/buildd/gtk+3.0-3.1.12/./gtk/gtkstyleproperties.c:103

[Pedro Villavicencio (pedro)]

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.

[Pedro Villavicencio (pedro)]

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!.