GNOME Bugzilla – Bug 146708
nautilus crashes on startup
Last modified: 2004-12-22 21:47:04 UTC
Distribution: Fedora Core release 2 (Tettnang) Package: nautilus Severity: critical Version: GNOME2.6. 2.6.x Gnome-Distributor: Red Hat, Inc Synopsis: nautilus crashes on startup Bugzilla-Product: nautilus Bugzilla-Component: general Bugzilla-Version: 2.6.x BugBuddy-GnomeVersion: 2.0 (2.6.0) Description: Description of the crash: upon logging into gnome, nautilus crashes on startup Steps to reproduce the crash: 1. log into gnome 2. 3. Expected Results: no crash How often does this happen? every time Additional Information: this is on x86-64 Debugging Information: Backtrace was generated from '/usr/bin/nautilus' Using host libthread_db library "/lib64/tls/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 182894179520 (LWP 5823)] [New Thread 1084225888 (LWP 5824)] [Thread debugging using libthread_db enabled] [New Thread 182894179520 (LWP 5823)] [New Thread 1084225888 (LWP 5824)] [Thread debugging using libthread_db enabled] [New Thread 182894179520 (LWP 5823)] [New Thread 1084225888 (LWP 5824)] 0x0000003e48a0c08e in __libc_waitpid (pid=5846, stat_loc=0x7fbfffe83c, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:41 41 int result = INLINE_SYSCALL (wait4, 4, pid, stat_loc, options, NULL);
+ Trace 48120
Thread 1 (Thread 182894179520 (LWP 5823))
descrip = 0x0, argDescrip = 0x0}} 0x0000003e48a0c08e 41 int result = INLINE_SYSCALL (wait4, 4, pid, stat_loc, options, NULL); ------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-07-09 05:09 ------- Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "nautilus". Setting to default milestone for this product, '---' The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@bugzilla.gnome.org. Previous reporter was jason@cluephone.com. 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.
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 146614 ***