GNOME Bugzilla – Bug 156983
Nautilus crashes at Startup
Last modified: 2004-12-22 21:47:04 UTC
Distribution: SuSE Linux 9.1 (i586) Package: nautilus Severity: normal Version: GNOME2.4.1 2.4.2 Gnome-Distributor: GNOME.Org Synopsis: Nautilus crashes at Startup Bugzilla-Product: nautilus Bugzilla-Component: general Bugzilla-Version: 2.4.2 BugBuddy-GnomeVersion: 2.0 (2.4.0.1) Description: Description of the crash: Login in gnome - an allert tells me, "Die Anwendung 'nautilus' (Prozess-No. xyz) ist wegen eines schweren Fehlers abgestuerzt (Abgebrochen)" (the applikation 'nautilus' is crashed by a "strong error" :-) This error appears every time on login at gnome by the KDE-Loginmananger KDM System: SuSE 9.1 with linux 2.6.5-7.111-default on an Athlon 1GB i386 (sorry about my English - I'm german) Steps to reproduce the crash: 1. 2. 3. Expected Results: How often does this happen? everytimes on login Additional Information: Debugging Information: Backtrace was generated from '/opt/gnome/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)...(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)...[Thread debugging using libthread_db enabled] [New Thread 1089933344 (LWP 11143)] [New Thread 1092836272 (LWP 11148)] [Thread debugging using libthread_db enabled] [New Thread 1089933344 (LWP 11143)] [New Thread 1092836272 (LWP 11148)] [Thread debugging using libthread_db enabled] [New Thread 1089933344 (LWP 11143)] [New Thread 1092836272 (LWP 11148)] [New Thread 1092570032 (LWP 11147)] [New Thread 1092303792 (LWP 11146)] [New Thread 1092037552 (LWP 11145)] [New Thread 1091771312 (LWP 11144)] (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)...0xffffe410 in ?? ()
+ Trace 51508
Thread 1 (Thread 1089933344 (LWP 11143))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-10-31 15:57 ------- Unknown version 2.4.2 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, '---' 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 spam@udel.de. 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. Matches the stack trace in bug 155806, which has been marked as a duplicate of 120222. *** This bug has been marked as a duplicate of 120222 ***