GNOME Bugzilla – Bug 154636
balsa crashes when you click compose
Last modified: 2005-04-23 14:01:12 UTC
Distribution: Fedora Core release 2.91 (FC3 Test 2) Package: balsa Severity: normal Version: GNOME2.7.92 unspecified Gnome-Distributor: Red Hat, Inc Synopsis: balsa crashes when you click compose Bugzilla-Product: balsa Bugzilla-Component: general Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.7.92) Description: Description of the crash: balsa crashes and user is presented with a program restart dialog Steps to reproduce the crash: 1. open balsa 2. click compose 3. Expected Results: i expect to be able to write an e-mail How often does this happen? every time Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/balsa' (no debugging symbols found)...Using host libthread_db library "/lib/tls/i686/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)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[Thread debugging using libthread_db enabled] [New Thread -1208164224 (LWP 27742)] (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)...0x00a512f1 in __waitpid_nocancel () from /lib/tls/i686/libpthread.so.0
+ Trace 50807
Thread 1 (Thread -1208164224 (LWP 27742))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-10-05 23:22 ------- Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "balsa". 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 fateisajester84@earthlink.net. 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. *** This bug has been marked as a duplicate of 156871 ***
*** Bug 301685 has been marked as a duplicate of this bug. ***