GNOME Bugzilla – Bug 304427
evolution bug
Last modified: 2005-05-31 22:37:18 UTC
Distribution: Debian 3.1 Package: Evolution Severity: normal Version: GNOME2.10.0 unspecified Gnome-Distributor: Ubuntu Synopsis: evolution bug Bugzilla-Product: Evolution Bugzilla-Component: Miscellaneous Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.10.0) Description: Description of the crash: I was saving my signature when it crashed. Steps to reproduce the crash: 1. Open a new message and type something in 2. Open the prefs and save a new signature Expected Results: Signature saved How often does this happen? I dont know yet, it is the first time and I didnt want to close without reporting. Good Luck! Debugging Information: Backtrace was generated from '/usr/bin/evolution-2.2' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. (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) (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 -1228736128 (LWP 6953)] [New Thread -1282307152 (LWP 13191)] [New Thread -1272190032 (LWP 13063)] [New Thread -1271923792 (LWP 8382)] [New Thread -1270592592 (LWP 8379)] [New Thread -1262064720 (LWP 8378)] [New Thread -1252840528 (LWP 7001)] [New Thread -1244447824 (LWP 7000)] [New Thread -1235207248 (LWP 6965)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 59768
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-05-16 21:55 UTC ------- 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 jmesquita@gmail.com.
Jmesquita: 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 so sorry, I couldnt reproduce the problem again. Anyway, I installed the proper debug symbols and hopefully, it will happen again so we can try and fix this. Thanks anyway for all the developers especially Nagappan for the very fast reply. Mesquita
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. Matches the stack trace in bug 303147, which has been marked as a duplicate of 300881 *** This bug has been marked as a duplicate of 300881 ***