GNOME Bugzilla – Bug 567313
Crash in IA__g_hash_table_lookup camel_object_bag_remove_unlocked at camel-object.c line 2334
Last modified: 2010-12-20 17:49:25 UTC
What were you doing when the application crashed? Had just opened Evolution, then clicked "send/receive." The "Send/Receive Mail" box opened (and may have done something, but not much). I then got "Bug Buddy." Distribution: Debian 5.0 Gnome Release: 2.22.3 2008-09-18 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.26-1-amd64 #1 SMP Wed Nov 26 18:26:02 UTC 2008 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: SphereCrystal Icon Theme: SphereCrystal Memory status: size: 651464704 vsize: 651464704 resident: 39780352 share: 20127744 rss: 39780352 rss_rlim: 18446744073709551615 CPU usage: start_time: 1231630592 rtime: 436 utime: 334 stime: 102 cutime:72 cstime: 82 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' [Thread debugging using libthread_db enabled] [New Thread 0x7f875aff0700 (LWP 20996)] [New Thread 0x4546e950 (LWP 21126)] [New Thread 0x4446c950 (LWP 21124)] [New Thread 0x42c69950 (LWP 21121)] [New Thread 0x400c2950 (LWP 21072)] [New Thread 0x417fb950 (LWP 21071)] [New Thread 0x40a9d950 (LWP 21035)] [New Thread 0x42468950 (LWP 21028)] 0x00007f87568d25ef in waitpid () from /lib/libpthread.so.0
+ Trace 211455
Thread 8 (Thread 0x42468950 (LWP 21028))
----------- .xsession-errors (7 sec old) --------------------- (evolution:20996): camel-pop3-provider-WARNING **: Bad server response: </tr> (evolution:20996): camel-pop3-provider-WARNING **: Bad server response: <tr><td><img width="1" src="http://images.foodnetwork.com/webfood/images/spacer.gif" height="4"></td (evolution:20996): camel-pop3-provider-WARNING **: Bad server response: <tr> (evolution:20996): camel-pop3-provider-WARNING **: Bad server response: <td align="center"><span style="font-family:Arial, Helvetica, sans-serif; font-size:12px; color:#3D (evolution:20996): camel-pop3-provider-WARNING **: Bad server response: = --------------------------------------------------
Have not seen any duplicates or similar traces for the recent stable releases. Closing as OBSOLETE as codebase has changed quite a lot in the last two years.