Ubuntu
brasero package

nautilus crashed with SIGSEGV in malloc()

Bug #425091 reported by Ronal on 2009-09-06

This bug report is a duplicate of: Bug #420841: nautilus assert failure: *** glibc detected *** nautilus: double free or corruption . Edit Remove

This bug affects 11 people

Affects		Status	Importance	Assigned to	Milestone
	brasero (Ubuntu)	Incomplete	Medium	Ubuntu Desktop Bugs

Bug Description

Binary package hint: brasero

when I try to open nautilus with 'gksu nautilus' don't work and when I try 'sudo nautilus' appear

** (nautilus:6259): WARNING **: No marshaller for signature of signal 'UploadFinished'

** (nautilus:6259): WARNING **: No marshaller for signature of signal 'DownloadFinished'
Sense key: 0x70 0x00 0x02 0x00 0x00 0x00 0x00 0x0a 0x00 0x00 0x00 0x00 0x3a 0x00 0x00 0x00 0x00 0x00 0x00
Fallo de segmentación (`core' generado)

I'm using Karmic alpha 5 amd64

ProblemType: Crash
Architecture: amd64
Date: Sun Sep 6 01:59:01 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/nautilus
NonfreeKernelModules: nvidia
Package: libbrasero-media0 2.27.91-0ubuntu2
ProcCmdline: nautilus
ProcEnviron:
PATH=(custom, no user)
LANG=es_VE.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-9.29-generic
SegvAnalysis:
Segfault happened at: 0x7f91c5a09336: mov 0x8(%r13),%rdx
PC (0x7f91c5a09336) ok
source "0x8(%r13)" (0x6e609e5fed5) 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
g_malloc () from /usr/lib/libglib-2.0.so.0
g_type_create_instance ()
?? () from /usr/lib/libgobject-2.0.so.0
Title: nautilus crashed with SIGSEGV in malloc()
Uname: Linux 2.6.31-9-generic x86_64
UserGroups:

See original description

Tags:

Revision history for this message

Ronal (iecelaya) wrote on 2009-09-06:

Dependencies.txt Edit (3.1 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (586 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (48.8 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (722 bytes, text/plain; charset="utf-8")
Registers.txt Edit (969 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (1.7 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (1.7 KiB, text/plain; charset="utf-8")

Ronal (iecelaya) on 2009-09-06

description:

updated

Revision history for this message

Apport retracing service (apport) wrote on 2009-09-06: Stacktrace.txt (retraced)

Stacktrace.txt (retraced) Edit (5.8 KiB, text/plain)

StacktraceTop:_int_malloc (av=0x7f91c5cfbe40, bytes=24) at malloc.c:4278
*__GI___libc_malloc (bytes=24) at malloc.c:3638
IA__g_malloc (n_bytes=24)
IA__g_type_create_instance (
g_object_constructor (type=140264065711680,

Revision history for this message

Apport retracing service (apport) wrote on 2009-09-06: ThreadStacktrace.txt (retraced)

ThreadStacktrace.txt (retraced) Edit (5.8 KiB, text/plain)

Changed in brasero (Ubuntu):
importance:	Undecided → Medium
tags:	removed: need-amd64-retrace

Revision history for this message

Pedro Villavicencio (pedro) wrote on 2009-09-07:

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.