GNOME Bugzilla – Bug 161452
Could not launch 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: Debian Synopsis: Could not launch nautilus Bugzilla-Product: nautilus Bugzilla-Component: general Bugzilla-Version: 2.8.2 BugBuddy-GnomeVersion: 2.0 (2.8.0) Description: Description of the crash: At 9:30 EST, Dec 16, 2004, I upgraded my Debian Sarge installation to the latest version of all installed packages (including the Gnome desktop applications and libraries), and I can't launch nautilus (package v2.8.2-2). Steps to reproduce the crash: 1. Install the latest Debian Sarge packages, including gnome-core (package v62) 2. Try to launch nautilus (either through the menu icon, or from the command line). 3. Get an error dialog: 'The Application "nautilus" has quit unexpectedly.' Expected Results: nautilus should launch and run How often does this happen? every time Additional Information: My email is james.damour@request.com, and I'm willing to take any steps to assist in debugging this issue. 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)...[Thread debugging using libthread_db enabled] [New Thread 1089979392 (LWP 28352)] [New Thread 1100454832 (LWP 28353)] [Thread debugging using libthread_db enabled] [New Thread 1089979392 (LWP 28352)] [New Thread 1100454832 (LWP 28353)] (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 1089979392 (LWP 28352)] [New Thread 1100454832 (LWP 28353)] (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)...0x40442431 in __waitpid_nocancel () from /lib/tls/libpthread.so.0
+ Trace 53588
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-12-16 09:41 ------- 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 james.damour@request.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 148847 ***