nautilus crashed with SIGSEGV in malloc()

Bug #433933 reported by graymalkin
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
brasero (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: brasero

.

ProblemType: Crash
Architecture: amd64
Date: Mon Sep 21 13:12:13 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/nautilus
Package: libbrasero-media0 2.27.92-0ubuntu2
ProcCmdline: nautilus file:///home/graymalkin/Video
ProcEnviron:
 PATH=(custom, no user)
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-5.6-rt
SegvAnalysis:
 Segfault happened at: 0x7f5493d153c6: mov 0x8(%r13),%rdx
 PC (0x7f5493d153c6) ok
 source "0x8(%r13)" (0x36312e30312e38) 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_object_newv () from /usr/lib/libgobject-2.0.so.0
 g_object_new_valist ()
Title: nautilus crashed with SIGSEGV in malloc()
Uname: Linux 2.6.31-5-rt x86_64
UserGroups:

Revision history for this message
graymalkin (muccapazza) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:_int_malloc (av=0x7f5494007e40, bytes=16) at malloc.c:4278
*__GI___libc_malloc (bytes=16) at malloc.c:3638
IA__g_malloc (n_bytes=16)
IA__g_object_newv (
IA__g_object_new_valist (object_type=34089216,

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 :

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.

visibility: private → public
Changed in brasero (Ubuntu):
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.