Ubuntu
nautilus package

nautilius crash during upgrade

Bug #221825 reported by otipher on 2008-04-25

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

Reported during upgrade process from 7.10 to 8.04

ProblemType: Crash
Architecture: amd64
Date: Fri Apr 18 06:50:42 2008
Disassembly: 0x2b9f5408531e:
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/nautilus
NonfreeKernelModules: ath_hal
Package: nautilus 1:2.22.2-0ubuntu4
PackageArchitecture: amd64
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_US.UTF-8
SHELL=/bin/bash
Signal: 11
SourcePackage: nautilus
Stacktrace:
#0 0x00002b9f5408531e in ?? ()
#1 0x0000000000000000 in ?? ()
StacktraceTop:
?? ()
?? ()
ThreadStacktrace:

Title: nautilus crashed with SIGSEGV
Uname: Linux 2.6.24-16-generic x86_64
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Tags:

Revision history for this message

otipher (otipher) wrote on 2008-04-25:

Dependencies.txt Edit (5.8 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (50.1 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (677 bytes, text/plain; charset="utf-8")
Registers.txt Edit (916 bytes, text/plain; charset="utf-8")

Revision history for this message

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

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

StacktraceTop:?? ()
?? ()

Revision history for this message

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

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

Revision history for this message

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

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.