GNOME Bugzilla – Bug 112055
Balsa randomly crashes
Last modified: 2004-12-22 21:47:04 UTC
Package: balsa Severity: major Version: 2.0.10 Synopsis: Balsa randomly crashes Bugzilla-Product: balsa Bugzilla-Component: general BugBuddy-GnomeVersion: 2.0 (2.2.0.1) Description: Description of Problem: Balsa randomly crashes Steps to reproduce the problem: 1. Launch Balsa 2. Wait and do something else 3. It crashes... Actual Results: Balsa is crashed and all mail status and movements betwenn boxes is lost Expected Results: none How often does this happen? At least once a day, sometimes it's worst Additional Information: I like Balsa Debugging Information: Backtrace was generated from '/usr/bin/balsa' (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)... (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 3290)] [New Thread 32769 (LWP 3291)] (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)... 0x41089af9 in wait4 () from /lib/libc.so.6
+ Trace 36480
Thread 1 (Thread 16384 (LWP 3290))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-05-02 04:46 ------- The original reporter (p.prost@ateme.fr) of this bug does not have an account here. Reassigning to the exporter, unknown@bugzilla.gnome.org. Reassigning to the default owner of the component, pawsa@theochem.kth.se.
This looks like the mysterious gtk+ crash that is showing up everywhere [See specifically bug 105745 for more info]. A number of people are getting this, but the stack traces are unfortunately useless and we don't know how to reproduce the problem. Can you get a stacktrace with symbols for us? [If you're using RedHat 9, you can do so with the following easy method; otherwise this will require recompiling from source: Install http://people.redhat.com/otaylor/tmp/gtk2-debuginfo-2.2.1-4.i386.rpm and if the problem occurs again, submit the backtrace you get. Installing the debuginfo package will make the backtrace much more useful.] I am adding myself to the cc and marking as needinfo for now.
*** This bug has been marked as a duplicate of 105745 ***