GNOME Bugzilla – Bug 146633
Seahorse crashe during startup
Last modified: 2004-12-22 21:47:04 UTC
Distribution: Debian testing/unstable Package: seahorse Severity: normal Version: GNOME2.6.1 0.7.3 Gnome-Distributor: Debian Synopsis: Seahorse crashe during startup Bugzilla-Product: seahorse Bugzilla-Component: general Bugzilla-Version: 0.7.3 BugBuddy-GnomeVersion: 2.0 (2.6.1.1) Description: Description of the crash: Directly after startup the application crashed. Steps to reproduce the crash: 1. Startup Seahorse Expected Results: Startup How often does this happen? Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/seahorse' (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)...[Thread debugging using libthread_db enabled] [New Thread 1088747104 (LWP 10533)] (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)...0x40aa440e in __waitpid_nocancel () from /lib/tls/libpthread.so.0
+ Trace 48067
Thread 1 (Thread 1088747104 (LWP 10533))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-07-09 03:57 ------- Unknown version 0.7.3 in product seahorse. Setting version to "0.6.x". Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "seahorse". 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 tobias@schlitt.info. 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 114467, which has been marked as a duplicate of 104261. *** This bug has been marked as a duplicate of 104261 ***