GNOME Bugzilla – Bug 124686
nautilus 2.4.0 crashes on startup
Last modified: 2004-12-22 21:47:04 UTC
Distribution: Unknown Package: nautilus Severity: normal Version: GNOME2.4.0 unspecified Gnome-Distributor: Gentoo Linux Synopsis: nautilus 2.4.0 crashes on startup Bugzilla-Product: nautilus Bugzilla-Component: general Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.4.0.1) Description: Description of the crash: After a recent restart of X nautilus just will not start. I have tried removing all the settings, .gnome* and .gconf* directories but this has no effect. Steps to reproduce the crash: 1. startx 2. open a terminal 3. try and start nautilus Expected Results: The nautilus window should appear How often does this happen? Every time Additional Information: I am using gentoo Linux, kernel 2.6.0test7, nautilus-2.4.0, gnome-vfs-2.4.1, ORBit2-2.8.2, libgnome-2.4.0, libgnomeui-2.4.0.1, libbonobo-2.4.1, libbonoboui-2.4.0 I have seen other similar bugs here but I cannot tell if they are actually the same, the traces do look a bit different. Debugging Information: Backtrace was generated from '/usr/bin/nautilus' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 4856)] [New Thread 32769 (LWP 4857)] [New Thread 16386 (LWP 4858)] [New Thread 32771 (LWP 4859)] [New Thread 49156 (LWP 4860)] [New Thread 65541 (LWP 4861)] [New Thread 81926 (LWP 4863)] [New Thread 98311 (LWP 4864)] [New Thread 114696 (LWP 4865)] 0x47a8b178 in waitpid () from /lib/libpthread.so.0
+ Trace 40884
Thread 9 (Thread 114696 (LWP 4865))
Thread 8 (Thread 98311 (LWP 4864))
Thread 7 (Thread 81926 (LWP 4863))
Thread 6 (Thread 65541 (LWP 4861))
Thread 5 (Thread 49156 (LWP 4860))
Thread 4 (Thread 32771 (LWP 4859))
Thread 3 (Thread 16386 (LWP 4858))
Thread 1 (Thread 16384 (LWP 4856))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-10-15 12:47 ------- The original reporter (simeon@sbs.bangor.ac.uk) of this bug does not have an account here. Reassigning to the exporter, unknown@bugzilla.gnome.org. Reassigning to the default owner of the component, nautilus-maint@bugzilla.gnome.org.
Could you upgrade to Nautilus 2.4.1 and see if the problem persist? If yes, please send another stacktrace as this one looks incomplete. See http://bugzilla.gnome.org/getting-traces.cgi for more information about getting a useful stack trace.
With 2.4.1 the error seems the same (BTW though I used an ebuild it was totally standard with no patches applied). Should I upgrade any other libs/components? I got this trace from gdb following the instructions referred to above: sim@milliways:~>gdb /usr/bin/nautilus GNU gdb 5.3.90_20030710 Copyright 2003 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 "i686-pc-linux-gnu"...(no debugging symbols found)...Using host libthread_db library "/lib/libthread_db.so.1". (gdb) run Starting program: /usr/bin/nautilus (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 16208)] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[New Thread 32769 (LWP 16209)] [New Thread 16386 (LWP 16210)] [New Thread 32771 (LWP 16211)] [New Thread 49156 (LWP 16212)] [New Thread 65541 (LWP 16213)] [New Thread 81926 (LWP 16214)] ** ERROR **: file nautilus-directory.c: line 546 (add_to_hash_table): assertion failed: (g_hash_table_lookup (directory->details->file_hash, file->details->relative_uri) == NULL) aborting... Program received signal SIGABRT, Aborted. [Switching to Thread 16384 (LWP 16208)] 0x47791001 in kill () from /lib/libc.so.6 (gdb) thread apply all bt
+ Trace 40889
Thread 5 (Thread 49156 (LWP 16212))
Thread 4 (Thread 32771 (LWP 16211))
Thread 3 (Thread 16386 (LWP 16210))
Thanks for following up. Unfortunately your second stack is as incomplete as the first one, however the assertion failure makes it look very much like a duplicate of bug 120222 (see bugs 123163, 122268 too). Please have a look at 120222, check if you have a similiar configuration with a volume mounted twice and add any information you find to that bug.
*** This bug has been marked as a duplicate of 120222 ***
Thanks for looking at this. I don't know why the stack traces are incomplete, I posted all that gdb generated. But, yes, I did have an nfs volume mounted twice. This is the problem! Thanks again.