nautilus crashed with SIGSEGV

Bug #145434 reported by Will Nowak on 2007-09-27
146
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: nautilus

Howdy,

This bug may be a duplicate of either 85836 or 92350, but I cannot say for sure, so I will let someone else decide.

After logging in, the notification area icons take a long time to load, and the desktop is non-responsive. After some time, the notification area icons show up with this apport crash notification. This has started within the last week and a half of package updates (I'm pulling the latest set each time they become available).

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Wed Sep 26 15:28:20 2007
Disassembly: 0xffffe410:
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/nautilus
NonfreeKernelModules: nvidia
Package: nautilus 1:2.20.0-0ubuntu1
PackageArchitecture: i386
ProcCmdline:

ProcCwd: /home/wan
ProcEnviron:

ProcMaps:
 08048000-0816a000 r-xp 00000000 08:05 134622407 /usr/bin/nautilus
 0816a000-0816f000 rw-p 00122000 08:05 134622407 /usr/bin/nautilus
 0816f000-08170000 rw-p 0816f000 00:00 0 [heap]
 bf90e000-bf923000 rw-p bf90e000 00:00 0 [stack]
Signal: 11
SourcePackage: nautilus
Stacktrace: #0 0xffffe410 in ?? ()
StacktraceTop: ?? ()
ThreadStacktrace:
 .
 Thread 1 (process 5804):
 #0 0xffffe410 in ?? ()
Title: nautilus crashed with SIGSEGV
Uname: Linux mind 2.6.22-12-386 #1 Sun Sep 23 17:37:35 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin mythtv netdev plugdev powerdev scanner video

Will Nowak (compbrain) wrote :

StacktraceTop:?? ()

Sebastien Bacher (seb128) wrote :

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.

Changed in nautilus:
assignee: nobody → desktop-bugs
importance: Undecided → Medium
status: New → Incomplete
Will Nowak (compbrain) wrote :

I followed the DebuggingProgramCrash instructions, installed the nautilus-dbgsym package, and attempted to start the program via gdb:
wan % gdb nautilus
GNU gdb 6.6-debian
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...
"/usr/bin/nautilus": not in executable format: File format not recognized

Strace output?
wan % strace nautilus
execve("/usr/bin/nautilus", ["nautilus"], [/* 42 vars */]) = -1 EFAULT (Bad address)
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV (core dumped) +++
Process 6558 detached

Maybe the file format was incorrect?
[mind:~]
wan % file `which nautilus`
/usr/bin/nautilus: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.6.8, dynamically linked (uses shared libs), stripped

Hmm. What else can I try?

wan % sudo aptitude reinstall nautilus
wan % gdb nautilus
GNU gdb 6.6-debian
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".

Aha! Corrupt package maybe?

Will Nowak (compbrain) wrote :

Yes, the issues I was having are now resolved, upon reboot the desktop is functional and the notification area popped up right on schedule.
As long as you feel alright with this result, I say we can close the bug.

Sebastien Bacher (seb128) wrote :

looked like your installation was corrupted, since that's fixed and not a real bug closing

Changed in nautilus:
status: Incomplete → Invalid
miked (miked11) wrote :

root@2HewittRand-desktop:~# cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=8.04
DISTRIB_CODENAME=hardy
DISTRIB_DESCRIPTION="Ubuntu hardy (development branch)"
root@2HewittRand-desktop:~#
Hardy Heron Alpha 4

Zaeggu (zaeggu) wrote :

I have the same Bug of my PC withe Hardy and lasted updates.

Bigbiz (markozz) wrote :

This morning, after updating Hardy, Nautilus doesn't run properly.
If I type nautilus in command line this is the result:

seahorse nautilus module initialized

** (nautilus:8895): WARNING **: Unable to add monitor: Not supported
Segmentation fault (core dumped)

and nautilus doesn't start!!!

If I type sudo nautilus the result:

[sudo] password for xxxxx:
seahorse nautilus module initialized

** (nautilus:9002): WARNING **: Unable to add monitor: Not supported

and nautilus STARTS... ? ? ?

Desktop is unavailable!!!

Pedro Villavicencio (pedro) wrote :

Please use apport to send the report of the crash, thanks.

Qchacho (ajmateusg) wrote :

Crash in start session on XFCE

miked (miked11) wrote :

Ubuntu Hardy Heron 8.04 Alpha 5
root@tower-desktop:~#
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/180795

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers