nautilus crashed with SIGSEGV in __libc_start_main()

Bug #542408 reported by tekstr1der
84
This bug affects 11 people
Affects Status Importance Assigned to Milestone
Nautilus
Expired
Critical
nautilus (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: nautilus

Attempting to launch nautilus

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Sat Mar 20 00:22:00 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100317.1)
Package: nautilus 1:2.29.92.1-0ubuntu2
ProcCmdline: nautilus
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.utf8
ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
SegvAnalysis:
 Segfault happened at: 0x50ad4c: mov 0x10(%rax),%rdi
 PC (0x0050ad4c) ok
 source "0x10(%rax)" (0x00000010) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? ()
 ?? ()
 __libc_start_main () from /lib/libc.so.6
 ?? ()
 ?? ()
Title: nautilus crashed with SIGSEGV in __libc_start_main()
Uname: Linux 2.6.32-16-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
tekstr1der (tekstr1der) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 append_quoted_word (str=0x7f19f75b5e80,
 main (argc=1, argv=0x7fff4e80f718)

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in nautilus (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
visibility: private → public
Revision history for this message
Pedro Villavicencio (pedro) wrote :

we got a good backtrace and a recent duplicate, the crash seems to be in the libegg inside nautilus, will send it upstream, thanks all.

Changed in nautilus (Ubuntu):
status: New → Confirmed
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for your bug report. This bug has been reported to the developers of the software. You can track it and make comments at:
 https://bugzilla.gnome.org/show_bug.cgi?id=614583

Changed in nautilus (Ubuntu):
status: Confirmed → Triaged
Changed in nautilus:
status: Unknown → New
Changed in nautilus:
importance: Unknown → Critical
Changed in nautilus:
status: New → Incomplete
Changed in nautilus:
status: Incomplete → Expired
Revision history for this message
Sebastien Bacher (seb128) wrote :

The bug didn't get activity/new duplicates for some year and the nautilus code saw quite some changes since which probably deprecated the issue so closing it. If it's still a problem in recent Ubuntu/nautilus version please submit a new report

Changed in nautilus (Ubuntu):
status: Triaged → 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.