GNOME Bugzilla – Bug 325936
crashed when I clicked save and close on a new signature
Last modified: 2006-01-06 12:10:18 UTC
Distribution: Fedora Core release 4 (Stentz) Package: Evolution Severity: major Version: GNOME2.10.0 2.2.x Gnome-Distributor: Red Hat, Inc Synopsis: crashed when I clicked save and close on a new signature Bugzilla-Product: Evolution Bugzilla-Component: Mailer Bugzilla-Version: 2.2.x BugBuddy-GnomeVersion: 2.0 (2.10.0) Description: Description of the crash: Background: Just finished installing FC4 on a new disk. Copied files from my account on old disk. Ran Evolution and let it migrate from earlier version (1.4 i think). Deleted old evolution directory. The signature I had is now just empty. Many of the accounts were incorrectly set to that signature after the migration. Created a new signature. Working through the list of accounts to fix the incorrect signature settings. Decided to create a brand new sig for one account using Add Signature. Cut and paste some text. Clicked Save And Close. CRASH. 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) [Thread debugging using libthread_db enabled] [New Thread -1208453440 (LWP 3322)] [New Thread -1337123920 (LWP 4151)] [New Thread -1318212688 (LWP 3581)] [New Thread -1347613776 (LWP 3359)] [New Thread -1305654352 (LWP 3350)] [New Thread -1389577296 (LWP 3345)] [New Thread -1379087440 (LWP 3344)] [New Thread -1295160400 (LWP 3335)] [New Thread -1284670544 (LWP 3334)] [New Thread -1274180688 (LWP 3333)] [New Thread -1263690832 (LWP 3332)] [New Thread -1253200976 (LWP 3331)] [New Thread -1242711120 (LWP 3330)] [New Thread -1232221264 (LWP 3329)] [New Thread -1221731408 (LWP 3328)] [New Thread -1211241552 (LWP 3327)] (no debugging symbols found) 0x00d18402 in ?? ()
+ Trace 64984
Thread 1 (Thread -1208453440 (LWP 3322))
------- Bug created by bug-buddy at 2006-01-06 03:04 -------
*** Bug 325937 has been marked as a duplicate of this bug. ***
same stacktrace as bug 325371 which is a duplicate of bug 312022 *** This bug has been marked as a duplicate of 312022 ***