GNOME Bugzilla – Bug 362428
crash in Evolution: Accepting a appointment
Last modified: 2007-09-04 06:18:23 UTC
What were you doing when the application crashed? Accepting a appointment Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 371396608 vsize: 0 resident: 371396608 share: 0 rss: 85315584 rss_rlim: 0 CPU usage: start_time: 1160902593 rtime: 0 utime: 3976 stime: 0 cutime:3739 cstime: 0 timeout: 237 it_real_value: 0 frequency: 6 Backtrace was generated from '/usr/bin/evolution-2.8' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1232795984 (LWP 5831)] [New Thread -1435735136 (LWP 5921)] [New Thread -1370043488 (LWP 5901)] [New Thread -1352803424 (LWP 5856)] [New Thread -1304433760 (LWP 5854)] [New Thread -1296041056 (LWP 5852)] [New Thread -1285968992 (LWP 5851)] [New Thread -1277539424 (LWP 5849)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 76492
Thread 1 (Thread -1232795984 (LWP 5831))
(In reply to comment #0) > Accepting a appointment Arjan, does the description of bug 353183 match your scenario by any chance? Especially, has GPG been involved? NEEDINFO. The stacktraces do match...
I have set up PGP/GPG, but i'm not signing my messages with it, i'm using S/MIME instead for signing the messages, and have used this for an long time without any problems. The version off evolution in bug 353183 is 2.6, but i'm using version 2.8, so there are some differences.
*** Bug 373460 has been marked as a duplicate of this bug. ***
*** Bug 381645 has been marked as a duplicate of this bug. ***
*** Bug 353183 has been marked as a duplicate of this bug. ***
confirming as per duplicates, i'm going to use this bug as the "original" bug as the description is better then in bug 353183, and the line numbers are up-to-date here.
*** Bug 383038 has been marked as a duplicate of this bug. ***
*** Bug 405471 has been marked as a duplicate of this bug. ***
*** Bug 410804 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of 355418 ***