GNOME Bugzilla – Bug 272488
Crash: Impossible to create signatures
Last modified: 2013-09-13 00:50:02 UTC
Distribution: Debian 3.1 Package: Evolution Priority: Normal Version: GNOME2.9.91 2.1.5 Gnome-Distributor: Ubuntu Synopsis: Impossible to create signatures Bugzilla-Product: Evolution Bugzilla-Component: Miscellaneous Bugzilla-Version: 2.1.5 BugBuddy-GnomeVersion: 2.0 (2.9.1) Description: Description of the crash: Every time I try to add a new signatura, evolution crashes Steps to reproduce the crash: 1. Go to the preferences editor 2. Select the signatures editor and try to add a new one 3. See how the editor appear and evolution crash. Expected Results: Be able to add a new signature How often does this happen? Always Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/evolution-2.2' (no debugging symbols found) Using host libthread_db library "/lib/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) [Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 30559)] [New Thread 32769 (LWP 30572)] [New Thread 16386 (LWP 30573)] [New Thread 32771 (LWP 30574)] [New Thread 81924 (LWP 30591)] [New Thread 65541 (LWP 30576)] [New Thread 98310 (LWP 30592)] 0x0f4c1c78 in waitpid () from /lib/libc.so.6
+ Trace 55584
Unknown reporter: carlos@pemas.net, changed to bugbuddy-import@ximian.com. 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 271904 ***