Ubuntu
nautilus package

nautilus crashed with SIGSEGV

Bug #223434 reported by Erland Howden on 2008-04-28

This bug report is a duplicate of: Bug #192457: nautilus crashed with SIGSEGV. Edit Remove

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

Bug Description

Binary package hint: nautilus

don't know

ProblemType: Crash
Architecture: i386
Date: Tue Apr 22 12:15:40 2008
Disassembly: 0xb7579fed:
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/nautilus
NonfreeKernelModules: cdrom
Package: nautilus 1:2.22.2-0ubuntu4
PackageArchitecture: i386
ProcCmdline: nautilus
ProcEnviron:
SHELL=/bin/bash
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin
LANG=en_AU.UTF-8
Signal: 11
SourcePackage: nautilus
Stacktrace:
#0 0xb7579fed in ?? ()
#1 0x08177e00 in ?? ()
#2 0x00000000 in ?? ()
StacktraceTop:
?? ()
?? ()
?? ()
ThreadStacktrace:
.
Thread 1 (process 6852):
#0 0xb7579fed in ?? ()
#1 0x08177e00 in ?? ()
#2 0x00000000 in ?? ()
Title: nautilus crashed with SIGSEGV
Uname: Linux 2.6.24-16-generic i686
UserGroups:

Tags:

Revision history for this message

Erland Howden (erlandh-deactivatedaccount) wrote on 2008-04-28:

Dependencies.txt Edit (5.8 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (29.4 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (591 bytes, text/plain; charset="utf-8")
Registers.txt Edit (466 bytes, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2008-05-10: Symbolic stack trace

Stacktrace.txt (retraced) Edit (71 bytes, text/plain)

StacktraceTop:?? ()
?? ()
?? ()

Revision history for this message

Apport retracing service (apport) wrote on 2008-05-10: Symbolic threaded stack trace

ThreadStacktrace.txt (retraced) Edit (98 bytes, text/plain)

Revision history for this message

Sebastien Bacher (seb128) wrote on 2008-05-10:

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.