GNOME Bugzilla – Bug 136895
crashes after start with assertion failed: (g_hash_table_lookup (directory->details->file_hash, file->details->relative_uri) == NULL)
Last modified: 2004-12-22 21:47:04 UTC
Distribution: Debian testing/unstable Package: nautilus Severity: normal Version: GNOME2.4.1 2.4.2 Gnome-Distributor: Debian Synopsis: crashes after start with assertion failed: (g_hash_table_lookup (directory->details->file_hash, file->details->relative_uri) == NULL) Bugzilla-Product: nautilus Bugzilla-Component: general Bugzilla-Version: 2.4.2 BugBuddy-GnomeVersion: 2.0 (2.4.0.1) Description: Description of the crash: ** 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... Steps to reproduce the crash: 1. run nautilus 2. 3. Expected Results: How often does this happen? Always, ever since this afternoon. Additional Information: Debugging Information: Backtrace was generated from '/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)...[New Thread 1088141952 (LWP 9065)] [New Thread 1091488688 (LWP 9074)] [New Thread 1091226544 (LWP 9073)] [New Thread 1090964400 (LWP 9072)] [New Thread 1090702256 (LWP 9071)] [New Thread 1090440112 (LWP 9070)] 0x40a06411 in __waitpid_nocancel () from /lib/tls/libpthread.so.0
+ Trace 45020
Thread 1 (Thread 1088141952 (LWP 9065))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-03-11 10:34 ------- Unknown version 2.4.2 in product nautilus. Setting version to the default, "unspecified". The original reporter (bugbuddy@spam.nitric.co.za) 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.
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. You should check your /etc/fstab for a bad syntax or duplicate mounts, and if you find out what's wrong, add a comment to bug 120222. *** This bug has been marked as a duplicate of 120222 ***