Ubuntu
nautilus package

nautilus crashed with SIGSEGV

Bug #225646 reported by Greg Barrett on 2008-05-02

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

during upgrade to 8.04 lts

ProblemType: Crash
Architecture: i386
Date: Thu Apr 24 22:45:09 2008
Disassembly: 0xb74e7fed:
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/nautilus
NonfreeKernelModules: cdrom
Package: nautilus 1:2.22.2-0ubuntu4
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
StacktraceTop:
?? ()
?? ()
?? ()
?? ()
?? ()
Title: nautilus crashed with SIGSEGV
Uname: Linux 2.6.22-14-generic i686
UserGroups: adm admin audio cdrom dialout fax floppy fuse plugdev scanner tape

Tags:

Revision history for this message

Greg Barrett (gbarre2002) wrote on 2008-05-02:

Dependencies.txt Edit (5.8 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (30.6 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (653 bytes, text/plain; charset="utf-8")
Registers.txt Edit (462 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (1.1 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (1.1 KiB, 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 (1.1 KiB, 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 (1.1 KiB, 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.