GNOME Bugzilla – Bug 127453
nautilus crashing on startup
Last modified: 2004-12-22 21:47:04 UTC
Distribution: Slackware Slackware 9.1.0 Package: nautilus Severity: critical Version: GNOME2.4.1 2.4.x Gnome-Distributor: GNOME.Org Synopsis: nautilus crashing on startup Bugzilla-Product: nautilus Bugzilla-Component: general Bugzilla-Version: 2.4.x BugBuddy-GnomeVersion: 2.0 (2.4.0.1) Description: Description of the crash: Nautilus crashes after I login to Gnome. The error message follows: ** 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... I'm unable to run Nautilus. I don't have sources online, but I assume Dropline Gnome releases debugging builds, since this is an assertion (should not be in production code). Since this is a binary distribution, I don't have debug symbols loaded. I have been running Gnome 2.4.1 for a week or so, and have not had this problem until today. It is a show stopper for me because I'm not unable to use the system. I would attempt pruning configuration files in case there is an error, but this seems like a problem with something missing, not something extra. Steps to reproduce the crash: 1. login or just run nautilus from command line 2. 3. Expected Results: How often does this happen? Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found)...[New Thread 16384 (LWP 1206)] [New Thread 32769 (LWP 1207)] [New Thread 16386 (LWP 1208)] [New Thread 32771 (LWP 1209)] [New Thread 49156 (LWP 1210)] [New Thread 65541 (LWP 1211)] [New Thread 81926 (LWP 1212)] 0x40ac060c in waitpid () from /lib/libpthread.so.0
+ Trace 41928
Thread 1 (Thread 16384 (LWP 1206))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-11-20 01:20 ------- Reassigning to the default owner of the component, nautilus-maint@bugzilla.gnome.org.
Ah, the error is written by g_assert(), not a naked assert(). I have tried using strace on nautilus to find further information, but can't find anything in the output that seems related. There are a lot of file not found lines, but all of the gnome code does this while searching for icons, and it seems that eventually every requested file is found. I have also checked for changes in my system, and can find none after 9 November, and in the period since then Nautilus has functioned perfectly. I have made no user-level changes in my configuration that should affect things. I created a new user on my system, and that user sees the same error in Nautilus. I also tried running Gnome as root, and root sees the same error once Nautilus tries to start. Something has to be different now, but I cannot imagine what that would be. I've tried using Bonsai to browse the code, but I rarely read any Gnome code, so I've no ideas yet on what else to look for.
I have found the cause of the error: I had 3 duplicated NFS mounts. In other words, this: /dev/sda1 on / type xfs (rw) none on /dev/pts type devpts (rw,gid=5,mode=620) none on /proc type proc (rw) /dev/sda6 on /tmp type xfs (rw) /dev/sda7 on /var type xfs (rw) /dev/sda8 on /usr type xfs (rw) /dev/sda9 on /home type xfs (rw) /dev/sda10 on /usr/local type xfs (rw) /dev/sdb2 on /u type xfs (rw) /dev/hda1 on /mnt/win type ntfs (ro,noexec,nosuid,nodev) usbfs on /proc/bus/usb type usbfs (rw) escape:/public on /public type nfs escape:/public2 on /public2 type nfs escape:/usr/local on /local2 type nfs escape:/public on /public type nfs escape:/public2 on /public2 type nfs escape:/usr/local on /local2 type nfs Nautilus can't handle this situation. Since it can easily happen, this is still a critical bug. I wonder too, if Nautilus would crash in similar but normal situations, or maybe something like union mounts?
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 120222 ***