GNOME Bugzilla – Bug 272493
evolution crashes when sending second link of session
Last modified: 2005-04-10 10:34:49 UTC
Distribution: Debian 3.1 Package: Evolution Priority: Normal Version: GNOME2.9.91 2.1.5 Gnome-Distributor: Ubuntu Synopsis: evolution crashes when sending second link of session Bugzilla-Product: Evolution Bugzilla-Component: Mailer Bugzilla-Version: 2.1.5 BugBuddy-GnomeVersion: 2.0 (2.9.1) Description: Description of the crash: evolution crashes when sending second link of session Steps to reproduce the crash: 1. start evolution 2. send a link from my browser (firefox) 3. send a second link from my browser 4. crash Expected Results: send second link How often does this happen? every time I send more than one link per session Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/evolution' (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) (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 -1233188256 (LWP 24080)] [New Thread -1319912528 (LWP 24117)] [New Thread -1311163472 (LWP 24116)] [New Thread -1302336592 (LWP 24115)] [New Thread -1293943888 (LWP 24113)] [New Thread -1265742928 (LWP 24112)] [New Thread -1257350224 (LWP 24110)] [New Thread -1282716752 (LWP 24095)] [New Thread -1274139728 (LWP 24094)] [New Thread -1248957520 (LWP 24091)] [New Thread -1240564816 (LWP 24090)] (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) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 55596
Unknown reporter: chck@bellcore.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. Matches 272586, which has been duplicated to bug 272525. *** This bug has been marked as a duplicate of 272525 ***
The bug that this bug was marked as a duplicate of has seemingly nothing to do with this bug. Did you mean to mark it as a duplicate of another bug?
bugs@bellcore.net: Nope, it was my intention to dupe to that bug. Checking now it seems the 2nd stacktrace doesn't match the 1st one. Sebastien: The two stacktraces in bug 272525 differ. Was I ok to dupe to that one?
seems to be right for me