Ubuntu
nautilus package

nautilus crashed with SIGSEGV

Bug #230566 reported by Henriël Veldtmann on 2008-05-15

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

I was busy doing a test upgrade on my Ubuntu Studio 7.10 running in VirtualBox running on i386.

After completing the setup, upon the first boot, I got this error message. I was still waiting for the system to finish booting, so I really have no idea what caused it.

ProblemType: Crash
Architecture: i386
Date: Wed May 14 21:20:04 2008
Disassembly: 0xb74effed:
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_ZA.UTF-8
Signal: 11
SourcePackage: nautilus
Stacktrace: #0 0xb74effed in ?? ()
StacktraceTop: ?? ()
ThreadStacktrace:
.
Thread 1 (process 5111):
#0 0xb74effed in ?? ()
Title: nautilus crashed with SIGSEGV
Uname: Linux 2.6.24-16-rt i686
UserGroups:

Tags:

Revision history for this message

Henriël Veldtmann (prince-unreal) wrote on 2008-05-15:

Dependencies.txt Edit (5.8 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (28.9 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (577 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-16: Symbolic stack trace

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

StacktraceTop:?? ()

Revision history for this message

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

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

Revision history for this message

Pedro Villavicencio (pedro) wrote on 2008-05-17:

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.