GNOME Bugzilla – Bug 151843
Crash on closing window
Last modified: 2004-12-22 21:47:04 UTC
Distribution: Fedora Core release 2 (Tettnang) Package: nautilus Severity: normal Version: GNOME2.7.92 2.7.92 Gnome-Distributor: GARNOME Synopsis: Crash on closing window Bugzilla-Product: nautilus Bugzilla-Component: general Bugzilla-Version: 2.7.92 BugBuddy-GnomeVersion: 2.0 (2.7.92) Description: Description of the crash: nautilus crashes and restarts when a file browsing window is closed. Steps to reproduce the crash: 1. 2. 3. Expected Results: How often does this happen? 100% Additional Information:' I installed all the platform and desktop tarballs for gnome 2.7.92 to /opt/gnome-2.7.92 after installing the hal rpm packages (and there dependencies) from the Fedora Core 2 development brach. I suspect it is a hal issue. Debugging Information: Backtrace was generated from '/opt/gnome-2.7.92/bin/nautilus' Using host libthread_db library "/lib/tls/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -151125888 (LWP 14547)] [New Thread 116743088 (LWP 14602)] [Thread debugging using libthread_db enabled] [New Thread -151125888 (LWP 14547)] [New Thread 116743088 (LWP 14602)] [Thread debugging using libthread_db enabled] [New Thread -151125888 (LWP 14547)] [New Thread 116743088 (LWP 14602)] [New Thread 16063408 (LWP 14601)] [New Thread 15203248 (LWP 14600)] [New Thread 14937008 (LWP 14599)] [New Thread 12929968 (LWP 14598)] [New Thread 133335984 (LWP 14595)] 0x006ac7a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
+ Trace 49890
Thread 1 (Thread -151125888 (LWP 14547))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-09-04 13:34 ------- Unknown version 2.7.92 in product nautilus. Setting version to "1.0.x". 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.
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 151493 ***