Ubuntu
nautilus package

nautilus crashed with SIGSEGV

Bug #228089 reported by Tabrays on 2008-05-08

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

After upgrading from 7.10 to 8.04. After first login.

ProblemType: Crash
Architecture: i386
Date: Sun May 4 16:51:06 2008
Disassembly: 0xb74b4fed:
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/nautilus
NonfreeKernelModules: nvidia
Package: nautilus 1:2.22.2-0ubuntu5
PackageArchitecture: i386
ProcCmdline: nautilus --no-default-window --sm-client-id default2
ProcEnviron:
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
LANG=en_CA.UTF-8
SHELL=/bin/bash
Signal: 11
SourcePackage: nautilus
Stacktrace:
#0 0xb74b4fed in ?? ()
#1 0x08177dc8 in ?? ()
#2 0x00000000 in ?? ()
StacktraceTop:
?? ()
?? ()
?? ()
ThreadStacktrace:
.
Thread 1 (process 23106):
#0 0xb74b4fed in ?? ()
#1 0x08177dc8 in ?? ()
#2 0x00000000 in ?? ()
Title: nautilus crashed with SIGSEGV
Uname: Linux 2.6.24-16-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin mythtv netdev plugdev powerdev scanner vboxusers video

Tags:

Revision history for this message

Tabrays (tabrays) wrote on 2008-05-08:

Dependencies.txt Edit (5.8 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (31.9 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (679 bytes, text/plain; charset="utf-8")
Registers.txt Edit (462 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 (99 bytes, text/plain)

Revision history for this message

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

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.