GNOME Bugzilla – Bug 151312
logged in and got a gnome crash message
Last modified: 2004-12-22 21:47:04 UTC
Package: bug-buddy Severity: normal Version: GNOME2.2.2 2.2.2.1 os_details: GNOME.Org Synopsis: logged in and got a gnome crash message Bugzilla-Product: bug-buddy Bugzilla-Component: general BugBuddy-GnomeVersion: 2.0 (2.2.1) Description: Description of Problem: Steps to reproduce the problem: 1. 2. 3. Actual Results: Expected Results: How often does this happen? several so far Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/gnome-panel' (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)...[Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 13541)] 0x403604e8 in waitpid () from /lib/libpthread.so.0
+ Trace 49712
Thread 1 (Thread 16384 (LWP 13541))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-08-28 17:59 ------- Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "bug-buddy". 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 steve.levy@aeroflex.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.
*** This bug has been marked as a duplicate of 111147 ***