GNOME Bugzilla – Bug 329427
Crash when Save and Close signature dialog.
Last modified: 2006-05-11 21:30:55 UTC
Distribution: Gentoo Base System version 1.12.0_pre15 Package: Evolution Severity: critical Version: GNOME2.12.2 2.4.x Gnome-Distributor: Gentoo Synopsis: Crash when Save and Close signature dialog. Bugzilla-Product: Evolution Bugzilla-Component: Mailer Bugzilla-Version: 2.4.x BugBuddy-GnomeVersion: 2.0 (2.12.0) Description: Description of the crash: Evolution crashed when I pressed the Save and Close button on an Edit Signature dialog. Steps to reproduce the crash: 1. 2. 3. Expected Results: Signature saved. How often does this happen? Only once so far Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/evolution-2.4' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 28974)] [New Thread 32769 (LWP 28980)] [New Thread 16386 (LWP 28981)] [New Thread 32771 (LWP 28982)] [New Thread 65540 (LWP 28984)] [New Thread 98309 (LWP 29008)] [New Thread 131078 (LWP 29115)] [New Thread 147463 (LWP 29117)] [New Thread 163848 (LWP 29238)] 0x00002aaaae3ee33a in waitpid () from /lib/libpthread.so.0
+ Trace 65809
Thread 8 (Thread 147463 (LWP 29117))
Thread 6 (Thread 98309 (LWP 29008))
Thread 5 (Thread 65540 (LWP 28984))
Thread 4 (Thread 32771 (LWP 28982))
Thread 3 (Thread 16386 (LWP 28981))
Thread 1 (Thread 16384 (LWP 28974))
------- Bug created by bug-buddy at 2006-02-01 05:43 -------
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. I am going to set this to NEEDINFO, if this happens again and you submit another stacktrace by bug-buddy, please leave a comment here. Thanks very much in advance.
i pretty much assume that this is the same bug as bug 341293 and a dozen other ones which are already marked as a duplicate of bug 312022. *** This bug has been marked as a duplicate of 312022 ***