GNOME Bugzilla – Bug 484614
crash in camel_key_table_sync (ki=0x0) at camel-partition-table.c:687
Last modified: 2008-01-22 13:02:46 UTC
What were you doing when the application crashed? Deleted 32 messages from junk, folder empties but message count still shows 32. I then moved over to trash folder and marked all. By mistake I pressed ctrl+Y before pressing ctrl+E to expunge, Moved to Inbox folder with message count 64 showing no messages, when bug buddy kicks inn. Distribution: Debian lenny/sid Gnome Release: 2.20.0 2007-09-21 (Debian) BugBuddy Version: 2.20.0 System: Linux 2.6.22-2-686 #1 SMP Fri Aug 31 00:24:01 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400000 Selinux: No Accessibility: Disabled GTK+ Theme: Mist Icon Theme: Mist Memory status: size: 142422016 vsize: 142422016 resident: 35827712 share: 17887232 rss: 35827712 rss_rlim: 4294967295 CPU usage: start_time: 1191024453 rtime: 5168426 utime: 4926622 stime: 241804 cutime:40856 cstime: 1704 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0xb69216b0 (LWP 26317)] [New Thread 0xb240bb90 (LWP 26480)] [New Thread 0xb26a5b90 (LWP 26344)] [New Thread 0xb2ea6b90 (LWP 26343)] [New Thread 0xb36a8b90 (LWP 26342)] [New Thread 0xb3f0fb90 (LWP 26332)] [New Thread 0xb47cab90 (LWP 26331)] [New Thread 0xb5936b90 (LWP 26330)] [New Thread 0xb5135b90 (LWP 26329)] [New Thread 0xb6140b90 (LWP 26326)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 168689
Thread 7 (Thread 0xb47cab90 (LWP 26331))
----------- .xsession-errors (858131 sec old) --------------------- fff fff fff fff fff fff fff fff fff fff fff fff fff f ...Too much output, ignoring rest... --------------------------------------------------
*** Bug 483762 has been marked as a duplicate of this bug. ***
*** Bug 492012 has been marked as a duplicate of this bug. ***
*** Bug 492078 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of 348149 ***