nautilus crashed with SIGSEGV in malloc()

[Daniel Hermansson]

Binary package hint: brasero

nautilus crashed on upgrade

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Wed Sep 16 02:00:34 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/nautilus
Package: libbrasero-media0 2.27.92-0ubuntu2
ProcCmdline: nautilus --sm-client-id 10abc8fd85e8abe3123842597657286700000046980029 --sm-client-state-file /home/username/.config/session-state/nautilus-1253033721.desktop
ProcEnviron:
 PATH=(custom, user)
 LANG=sv_SE.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-10.32-generic
SegvAnalysis:
 Segfault happened at: 0x7f010f2ab3c6: mov 0x8(%r13),%rdx
 PC (0x7f010f2ab3c6) ok
 source "0x8(%r13)" (0x66206d616572745b) not located in a known VMA region (needed readable region)!
 destination "%rdx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: brasero
StacktraceTop:
 ?? () from /lib/libc.so.6
 malloc () from /lib/libc.so.6
 IA__g_malloc (n_bytes=16)
 IA__g_path_get_basename (
 gst_registry_lookup_locked (registry=0x2142c10,
Title: nautilus crashed with SIGSEGV in malloc()
Uname: Linux 2.6.31-10-generic x86_64
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse kvm libvirtd lpadmin netdev plugdev sambashare scanner tape vboxusers video

[Apport retracing service (apport)]

StacktraceTop:_int_malloc (av=0x7f010f59de40, bytes=16) at malloc.c:4278
*__GI___libc_malloc (bytes=16) at malloc.c:3638
IA__g_malloc (n_bytes=16)
IA__g_path_get_basename (
gst_registry_lookup_locked (registry=0x2142c10,

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