Ubuntu
nautilus package

nautilus crashed with SIGSEGV

Bug #225003 reported by onana on 2008-05-01

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

Ubuntu 8.04 - the Hardy Heron

ProblemType: Crash
Architecture: i386
Date: Thu Apr 24 21:09:45 2008
Disassembly: 0xb72567bc:
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/nautilus
NonfreeKernelModules: ath_hal
Package: nautilus 1:2.22.2-0ubuntu4
PackageArchitecture: i386
ProcCmdline: nautilus --no-desktop file:///home/onana/Pictures
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
StacktraceTop:
?? ()
?? ()
?? ()
?? ()
?? ()
Title: nautilus crashed with SIGSEGV
Uname: Linux 2.6.24-16-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Tags:

Revision history for this message

onana (imanorangebanana) wrote on 2008-05-01:

Dependencies.txt Edit (5.8 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (17.6 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (663 bytes, text/plain; charset="utf-8")
Registers.txt Edit (438 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (311 bytes, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (1.3 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 (311 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 (1.3 KiB, 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. What did you do to get the issue?