GNOME Bugzilla – Bug 159265
Opening Nautilus
Last modified: 2004-12-22 21:47:04 UTC
Distribution: Debian 3.1 Package: nautilus Severity: normal Version: GNOME2.8.1 2.8.2 Gnome-Distributor: Ubuntu Synopsis: Opening Nautilus Bugzilla-Product: nautilus Bugzilla-Component: general Bugzilla-Version: 2.8.2 BugBuddy-GnomeVersion: 2.0 (2.8.0) Description: Description of the crash: Opening Nautilus get error The Application "nautilus" has quit unexpectedly. Steps to reproduce the crash: 1. Click Computer 2. Home 3. Expected Results: Nautilus to open How often does this happen? Everytime you do the aove. Additional Information: This just started happening after I did a apt-get update, apt-get upgrade Running AMD64 Debugging Information: Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) Using host libthread_db library "/lib/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) [Thread debugging using libthread_db enabled] [New Thread 182985016608 (LWP 7416)] [New Thread 1082128752 (LWP 7417)] [Thread debugging using libthread_db enabled] [New Thread 182985016608 (LWP 7416)] [New Thread 1082128752 (LWP 7417)] (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) 0x0000002a969e89fe in waitpid () from /lib/libpthread.so.0
+ Trace 52565
Thread 2 (Thread 1082128752 (LWP 7417))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-11-23 21:44 ------- Unknown version 2.8.2 in product nautilus. Setting version to "2.8.x". 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 bigal50@charter.net. 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 148847 ***