GNOME Bugzilla – Bug 118028
Crashed trying to generate report on Evolution crash
Last modified: 2006-04-10 20:13:56 UTC
Package: bug-buddy Severity: normal Version: GNOME2.2.2 2.2.104 os_details: Ximian, Inc. Synopsis: Crashed trying to generate report on Evolution crash Bugzilla-Product: bug-buddy Bugzilla-Component: general BugBuddy-GnomeVersion: 2.0 (2.2.0.1) Description: Description of Problem: Evolution crashed. Bug Buddy popped up. Asked to download updated information, which I confirmed. It appeared to download fine and then creashed while trying to open the next window (I think). Debugging Information: Backtrace was generated from '/usr/bin/bug-buddy' (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)...[New Thread 16384 (LWP 26917)] [New Thread 32769 (LWP 26918)] [New Thread 16386 (LWP 26919)] (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)...0x408ca844 in waitpid () from /lib/libpthread.so.0
+ Trace 38925
Thread 1 (Thread 16384 (LWP 26917))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-07-21 18:20 ------- Reassigning to the default owner of the component, bug-buddy-maint@bugzilla.gnome.org.
Evolution crashed again in a similar scenario and I was able to use Bug Buddy successfully the second time. Here's the URL to the Ximian bug in case you are interested. http://bugzilla.ximian.com/show_bug.cgi?id=46690
Other than bug 118008 (which describes the original galeon bug instead of the bug-buddy crash for which a stack trace is included in the report), this appears to be a unique stack trace according to the simple-dup-finder. (I'm not marking 118008 as a duplicate of this, though, as it has already been marked as a duplicate of another galeon bug). Setting version, adding bugsquad keyword, and marking as new.
*** Bug 118128 has been marked as a duplicate of this bug. ***
*** Bug 119448 has been marked as a duplicate of this bug. ***
I believe we fixed this in a bug-buddy update several months ago; some weird quirk in the specific version we shipped with the first XD2.
*** Bug 338012 has been marked as a duplicate of this bug. ***