GNOME Bugzilla – Bug 153888
nautilus crash shortly after boot to multiuser runlevel 5
Last modified: 2006-08-24 16:21:08 UTC
Distribution: Fedora Core release 2.91 (FC3 Test 2) Package: nautilus Severity: normal Version: GNOME2.8.0 2.8.x Gnome-Distributor: Red Hat, Inc Synopsis: nautilus crash shortly after boot to multiuser runlevel 5 Bugzilla-Product: nautilus Bugzilla-Component: general Bugzilla-Version: 2.8.x BugBuddy-GnomeVersion: 2.0 (2.8.0) Description: Description of the crash: Error window appeared shortly after non-superuser logged in to recently-booted system. "The Application "nautilus" has quit unexpectedly. You can inform the developers of what happened to help them fix it. ..." Steps to reproduce the crash: 1. unknown 2. 3. Expected Results: no crash How often does this happen? first time in 6 days of Fedora Core 3 test 2. Additional Information: nautilus-2.8.0-1 recently up2date with glibc-2.3.3-58. Debugging Information: Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found)...Using host libthread_db library "/lib/tls/libthread_db.so.1". (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 -151124928 (LWP 3443)] [New Thread 16034736 (LWP 3496)] [Thread debugging using libthread_db enabled] [New Thread -151124928 (LWP 3443)] [New Thread 16034736 (LWP 3496)] [Thread debugging using libthread_db enabled] [New Thread -151124928 (LWP 3443)] [New Thread 16034736 (LWP 3496)] [New Thread 13454256 (LWP 3495)] [New Thread 13188016 (LWP 3494)] [New Thread 67423152 (LWP 3450)] (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)...(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)...0x00f96782 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
+ Trace 50533
Thread 1 (Thread -151124928 (LWP 3443))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-09-27 16:28 ------- Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "nautilus". Setting to default milestone for this product, '---' Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
*** Bug 153942 has been marked as a duplicate of this bug. ***
From a query on the nautilus_directory_are_all_files_seen function name, this appears to be a unique stack trace other than the duplicate already marked.
*** Bug 154415 has been marked as a duplicate of this bug. ***
*** Bug 154474 has been marked as a duplicate of this bug. ***
*** Bug 150758 has been marked as a duplicate of this bug. ***
May be related to bug 123294.
*** Bug 154842 has been marked as a duplicate of this bug. ***
*** Bug 155307 has been marked as a duplicate of this bug. ***
*** Bug 156027 has been marked as a duplicate of this bug. ***
*** Bug 156490 has been marked as a duplicate of this bug. ***
*** Bug 156383 has been marked as a duplicate of this bug. ***
The reporter of bug 156383 -- which was marked a duplicate of this -- wrote: "Since 2.8.0 it always crashes upon start with the following message: ** ERROR **: file nautilus-directory.c: line 553 (add_to_hash_table): assertion failed: (g_hash_table_lookup (directory->details->file_hash, file->details->relative_uri) == NULL) aborting..." which makes it seem like this bug may be a duplicate of bug 120222.
*** Bug 158019 has been marked as a duplicate of this bug. ***
Lots of dupes, so I'm confirming.
*** Bug 158136 has been marked as a duplicate of this bug. ***
*** Bug 158338 has been marked as a duplicate of this bug. ***
*** Bug 158643 has been marked as a duplicate of this bug. ***
*** Bug 158737 has been marked as a duplicate of this bug. ***
*** Bug 158720 has been marked as a duplicate of this bug. ***
*** Bug 159170 has been marked as a duplicate of this bug. ***
*** Bug 159303 has been marked as a duplicate of this bug. ***
*** Bug 159488 has been marked as a duplicate of this bug. ***
*** Bug 159497 has been marked as a duplicate of this bug. ***
*** Bug 159582 has been marked as a duplicate of this bug. ***
*** Bug 159666 has been marked as a duplicate of this bug. ***
*** Bug 159886 has been marked as a duplicate of this bug. ***
*** Bug 159935 has been marked as a duplicate of this bug. ***
*** Bug 159951 has been marked as a duplicate of this bug. ***
Created attachment 34333 [details] [review] Proposed patch (Don't use the drive name for desktop links) This is basically the 2.8.x version of bug 120222. It's caused by nautilus trying to use the same filename twice for volume desktop links. This triggers an assertion in nautilus-directory eventually. To reproduce: 1. Mount a cdrom with the same name as an unmounted volume from your fstab 2. mount the volume from fstab
*** Bug 160070 has been marked as a duplicate of this bug. ***
*** Bug 160285 has been marked as a duplicate of this bug. ***
*** Bug 160575 has been marked as a duplicate of this bug. ***
*** Bug 160587 has been marked as a duplicate of this bug. ***
*** Bug 160588 has been marked as a duplicate of this bug. ***
*** Bug 160745 has been marked as a duplicate of this bug. ***
*** Bug 160886 has been marked as a duplicate of this bug. ***
Created attachment 34677 [details] stack trace resulting from conditions simmilar to those reported in Bug 160886 Another stack trace spawned by this bug.
*** Bug 160974 has been marked as a duplicate of this bug. ***
Fixed on HEAD and gnome-2-8 branch with: 2004-12-12 Alexander Larsson <alexl@redhat.com> * libnautilus-private/nautilus-desktop-link-monitor.c: (destroy_desktop_link_monitor), (nautilus_desktop_link_monitor_get), (volume_file_name_used), (nautilus_desktop_link_monitor_make_filename_unique), (create_volume_link), (nautilus_desktop_link_monitor_init): * libnautilus-private/nautilus-desktop-link-monitor.h: * libnautilus-private/nautilus-desktop-link.c: (nautilus_desktop_link_new_from_volume): Make sure volume filenames are unique (#153888)
*** Bug 161069 has been marked as a duplicate of this bug. ***
*** Bug 161187 has been marked as a duplicate of this bug. ***
*** Bug 161196 has been marked as a duplicate of this bug. ***
*** Bug 161226 has been marked as a duplicate of this bug. ***
*** Bug 161421 has been marked as a duplicate of this bug. ***
*** Bug 161608 has been marked as a duplicate of this bug. ***
*** Bug 161627 has been marked as a duplicate of this bug. ***
*** Bug 161657 has been marked as a duplicate of this bug. ***
*** Bug 161846 has been marked as a duplicate of this bug. ***
*** Bug 161871 has been marked as a duplicate of this bug. ***
*** Bug 161880 has been marked as a duplicate of this bug. ***
*** Bug 162052 has been marked as a duplicate of this bug. ***
*** Bug 162216 has been marked as a duplicate of this bug. ***
*** Bug 162427 has been marked as a duplicate of this bug. ***
*** Bug 162436 has been marked as a duplicate of this bug. ***
*** Bug 162514 has been marked as a duplicate of this bug. ***
*** Bug 162679 has been marked as a duplicate of this bug. ***
*** Bug 162702 has been marked as a duplicate of this bug. ***
*** Bug 162722 has been marked as a duplicate of this bug. ***
*** Bug 162724 has been marked as a duplicate of this bug. ***
*** Bug 162749 has been marked as a duplicate of this bug. ***
*** Bug 162886 has been marked as a duplicate of this bug. ***
*** Bug 163206 has been marked as a duplicate of this bug. ***
*** Bug 163272 has been marked as a duplicate of this bug. ***
*** Bug 163388 has been marked as a duplicate of this bug. ***
*** Bug 163460 has been marked as a duplicate of this bug. ***
*** Bug 163489 has been marked as a duplicate of this bug. ***
*** Bug 163503 has been marked as a duplicate of this bug. ***
*** Bug 163837 has been marked as a duplicate of this bug. ***
*** Bug 163970 has been marked as a duplicate of this bug. ***
*** Bug 164144 has been marked as a duplicate of this bug. ***
*** Bug 164210 has been marked as a duplicate of this bug. ***
*** Bug 164470 has been marked as a duplicate of this bug. ***
*** Bug 164483 has been marked as a duplicate of this bug. ***
*** Bug 164641 has been marked as a duplicate of this bug. ***
*** Bug 164692 has been marked as a duplicate of this bug. ***
*** Bug 164872 has been marked as a duplicate of this bug. ***
*** Bug 165059 has been marked as a duplicate of this bug. ***
*** Bug 165087 has been marked as a duplicate of this bug. ***
*** Bug 165071 has been marked as a duplicate of this bug. ***
*** Bug 165072 has been marked as a duplicate of this bug. ***
*** Bug 165073 has been marked as a duplicate of this bug. ***
*** Bug 165134 has been marked as a duplicate of this bug. ***
*** Bug 165245 has been marked as a duplicate of this bug. ***
*** Bug 165338 has been marked as a duplicate of this bug. ***
*** Bug 165507 has been marked as a duplicate of this bug. ***
*** Bug 165601 has been marked as a duplicate of this bug. ***
*** Bug 165658 has been marked as a duplicate of this bug. ***
*** Bug 165878 has been marked as a duplicate of this bug. ***
*** Bug 165946 has been marked as a duplicate of this bug. ***
*** Bug 166237 has been marked as a duplicate of this bug. ***
*** Bug 166394 has been marked as a duplicate of this bug. ***
*** Bug 166459 has been marked as a duplicate of this bug. ***
*** Bug 166511 has been marked as a duplicate of this bug. ***
*** Bug 166513 has been marked as a duplicate of this bug. ***
*** Bug 166723 has been marked as a duplicate of this bug. ***
*** Bug 166842 has been marked as a duplicate of this bug. ***
*** Bug 167265 has been marked as a duplicate of this bug. ***
*** Bug 167613 has been marked as a duplicate of this bug. ***
*** Bug 167710 has been marked as a duplicate of this bug. ***
*** Bug 167731 has been marked as a duplicate of this bug. ***
*** Bug 167733 has been marked as a duplicate of this bug. ***
*** Bug 167865 has been marked as a duplicate of this bug. ***
*** Bug 167877 has been marked as a duplicate of this bug. ***
*** Bug 167939 has been marked as a duplicate of this bug. ***
*** Bug 167990 has been marked as a duplicate of this bug. ***
*** Bug 168200 has been marked as a duplicate of this bug. ***
*** Bug 168293 has been marked as a duplicate of this bug. ***
*** Bug 168369 has been marked as a duplicate of this bug. ***
*** Bug 168495 has been marked as a duplicate of this bug. ***
*** Bug 168521 has been marked as a duplicate of this bug. ***
*** Bug 168794 has been marked as a duplicate of this bug. ***
*** Bug 168863 has been marked as a duplicate of this bug. ***
*** Bug 168920 has been marked as a duplicate of this bug. ***
*** Bug 169114 has been marked as a duplicate of this bug. ***
*** Bug 169131 has been marked as a duplicate of this bug. ***
*** Bug 169484 has been marked as a duplicate of this bug. ***
*** Bug 169696 has been marked as a duplicate of this bug. ***
*** Bug 169744 has been marked as a duplicate of this bug. ***
*** Bug 169929 has been marked as a duplicate of this bug. ***
*** Bug 170101 has been marked as a duplicate of this bug. ***
*** Bug 170117 has been marked as a duplicate of this bug. ***
*** Bug 170173 has been marked as a duplicate of this bug. ***
*** Bug 170271 has been marked as a duplicate of this bug. ***
*** Bug 170366 has been marked as a duplicate of this bug. ***
*** Bug 170539 has been marked as a duplicate of this bug. ***
*** Bug 170650 has been marked as a duplicate of this bug. ***
*** Bug 170881 has been marked as a duplicate of this bug. ***
*** Bug 171360 has been marked as a duplicate of this bug. ***
*** Bug 171411 has been marked as a duplicate of this bug. ***
*** Bug 171633 has been marked as a duplicate of this bug. ***
*** Bug 171717 has been marked as a duplicate of this bug. ***
*** Bug 171792 has been marked as a duplicate of this bug. ***
Although this bug has been declared 'fixed', it is still happening. I want to add information which was not available when I posted this problem. This bug only seems to happen when using the 2.6.11.x kernel. I have two 2.6.11 kernels to which I can boot, both using FC3, and they both exhibit this problem. However, I have just recompiled a 2.6.10 kernel, as well as the 2.6.10-1.741_FC3 kernel, both also using FC3, which do not exhibit this problem. The / directories are common to all kernels. Nautilus is common to all kernels. The only apparent differences are the 2.6.11.x kernels. I hope this information is helpful. owa
what version of nautilus are you using ?
*** Bug 171814 has been marked as a duplicate of this bug. ***
I think it is version 2.8..... it is what ever version which came packaged with the Fedora Core 3 stable release. I had NOT experienced this bug until after I installed the 2.6.11 kernel a few days ago. It happens frequently with either the 2.6.11 or the 2.6.11.4. I downloaded both of these kernels from kernel.org.... vanilla kernels, which I configured and built manually, using the .config defaults from the 2.6.10 kernel. The 2.6.10 kernels, one built manually from a vanilla kernel from kernel.org, and the other installed by apt-get/synaptic update, both built on the .config defaults from the 2.6.9-* kernel which came with the FC3 package. This is unrelated to this particular bug, but may be useful information; After I built the 2.6.11 kernels, I installed the recommended udev rpm for 2.6.11. After that is when I first experienced this bug. In addition, I was forced to replace my CD drive due to failure since installing the 2.6.11 kernels. Oddly, after replacing the CD drive with a DVD/CD r/w, the 2.6.10 and 2.6.9 kernels wouldn't boot completely. The 2.6.10 would hang just after uncompressing the kernel, and would eventually give a message, "hdb: not ready to receive command." The 2.6.9 kernel would hang just before the login screen, with what seemed to be no video driver. The 2.6.10-1.741_FC3 kernel would boot. I was able to rebuild a working 2.6.10 kernel from the .config defaults of the 2.6.10-1.741_FC3 kernel. I am using this custom built 2.6.10 kernel now, till we can resolve the issue of this bug. If this additional information is of no value, I appologize. I've spent 37 years fixing things, and quite often symptoms which seem, at first, to be completely unrelated, provide a clue which proves to be instrumental in solving the problem. If this is of value, I'm glad. If it is not, please disregard. Thanks, owa
you have the nautilus version in the about box. This bug is supposed to be fixed for the gnome-2-8 CVS branch (there is no tarball with this patch) and for nautilus 2.10. FC3 probably packages a 2.8 tarball, you should ask them to patch the package for that.
*** Bug 172107 has been marked as a duplicate of this bug. ***
*** Bug 172269 has been marked as a duplicate of this bug. ***
*** Bug 172452 has been marked as a duplicate of this bug. ***
*** Bug 172502 has been marked as a duplicate of this bug. ***
*** Bug 172609 has been marked as a duplicate of this bug. ***
*** Bug 172613 has been marked as a duplicate of this bug. ***
*** Bug 172617 has been marked as a duplicate of this bug. ***
*** Bug 173022 has been marked as a duplicate of this bug. ***
*** Bug 300060 has been marked as a duplicate of this bug. ***
*** Bug 300294 has been marked as a duplicate of this bug. ***
*** Bug 300394 has been marked as a duplicate of this bug. ***
*** Bug 300670 has been marked as a duplicate of this bug. ***
*** Bug 301047 has been marked as a duplicate of this bug. ***
*** Bug 301277 has been marked as a duplicate of this bug. ***
*** Bug 301569 has been marked as a duplicate of this bug. ***
*** Bug 301577 has been marked as a duplicate of this bug. ***
*** Bug 301927 has been marked as a duplicate of this bug. ***
*** Bug 301991 has been marked as a duplicate of this bug. ***
*** Bug 302086 has been marked as a duplicate of this bug. ***
*** Bug 302499 has been marked as a duplicate of this bug. ***
*** Bug 302744 has been marked as a duplicate of this bug. ***
*** Bug 302807 has been marked as a duplicate of this bug. ***
*** Bug 302923 has been marked as a duplicate of this bug. ***
*** Bug 303419 has been marked as a duplicate of this bug. ***
*** Bug 303521 has been marked as a duplicate of this bug. ***
*** Bug 303875 has been marked as a duplicate of this bug. ***
*** Bug 304250 has been marked as a duplicate of this bug. ***
*** Bug 304746 has been marked as a duplicate of this bug. ***
*** Bug 168848 has been marked as a duplicate of this bug. ***
*** Bug 304839 has been marked as a duplicate of this bug. ***
*** Bug 305200 has been marked as a duplicate of this bug. ***
*** Bug 305283 has been marked as a duplicate of this bug. ***
*** Bug 305416 has been marked as a duplicate of this bug. ***
*** Bug 305454 has been marked as a duplicate of this bug. ***
*** Bug 305339 has been marked as a duplicate of this bug. ***
*** Bug 305757 has been marked as a duplicate of this bug. ***
This has reoccured under Debian Sid. Nautilus didn't die on a remote login. Local login killed Nautilus both for the local AND remote session. 2.4 series kernel. 2.6 series kernel doesn't seem to cause the issue (granted, present logins are impossible due to mouse failure). Could be related to hard disk corruption or motherboard IDE controller failures. Linux fallenangel 2.4.27-1-386 #1 Wed Dec 1 19:43:08 JST 2004 i686 GNU/Linux Gnome nautilus 2.8.2
*** Bug 305763 has been marked as a duplicate of this bug. ***
*** Bug 306098 has been marked as a duplicate of this bug. ***
*** Bug 306100 has been marked as a duplicate of this bug. ***
*** Bug 306142 has been marked as a duplicate of this bug. ***
*** Bug 306412 has been marked as a duplicate of this bug. ***
*** Bug 306490 has been marked as a duplicate of this bug. ***
*** Bug 306634 has been marked as a duplicate of this bug. ***
*** Bug 306703 has been marked as a duplicate of this bug. ***
*** Bug 307161 has been marked as a duplicate of this bug. ***
*** Bug 307206 has been marked as a duplicate of this bug. ***
*** Bug 307432 has been marked as a duplicate of this bug. ***
*** Bug 308217 has been marked as a duplicate of this bug. ***
Nautilus crashed on my first login in Fedora Core 4. This is occurring with Gnome 2.10 and Nautilus nautilus-2.10.0-4. Should this bug be reopened?
Would turning off /apps/nautilus/desktop/volumes_visible do anything to work around this problem?
GConf error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: IOR file '/tmp/gconfd-root/lock/ior' not opened successfully, no gconfd located: No such file or directory 2: IOR file '/tmp/gconfd-root/lock/ior' not opened successfully, no gconfd located: No such file or directory)
*** Bug 330252 has been marked as a duplicate of this bug. ***
*** Bug 330345 has been marked as a duplicate of this bug. ***
*** Bug 352647 has been marked as a duplicate of this bug. ***