GNOME Bugzilla – Bug 497590
crash in Tasks:
Last modified: 2007-11-18 18:02:10 UTC
Version: 2.10 What were you doing when the application crashed? Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.1-21.fc7 #1 SMP Thu Nov 1 21:09:24 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 155979776 vsize: 155979776 resident: 55496704 share: 38166528 rss: 55496704 rss_rlim: 4294967295 CPU usage: start_time: 1195287820 rtime: 2436 utime: 2193 stime: 243 cutime:94 cstime: 41 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' (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 -1208218896 (LWP 7455)] [New Thread -1318995056 (LWP 7643)] [New Thread -1297622128 (LWP 7630)] [New Thread -1244333168 (LWP 7582)] [New Thread -1232725104 (LWP 7458)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 178294
Thread 1 (Thread -1208218896 (LWP 7455))
----------- .xsession-errors (33 sec old) --------------------- (evolution:7455): camel-pop3-provider-WARNING **: Bad server response: wjj7RDFJH+//AM9+P6dPjDw3q2pRxxO7yO8h/deZFj8+Og5/Ec17f4f8QX626Osdyn7oDzLeX/20 (evolution:7455): camel-pop3-provider-WARNING **: Bad server response: /wD1j0rxPq/tLUut77+nn6d/8vRp6fvOj/Le3Xontt53PpyTVtQaS2mh/wBI+0RfZZRcWufJuMgW (evolution:7455): camel-pop3-provider-WARNING **: Bad server response: n/Hlz0/yOTWxpd39ouC9zp9u73Fqf3kcV1OPw/0HIse3bI4GK8Ts/EUc1nC6Xke+3lt5SLiK18g/ (evolution:7455): camel-pop3-provider-WARNING **: Bad server response: 489PxrvLPXryL7G8N5Zv+9MUx8ryP9H/APA7+v65xzezVOr7J23fn6X89UdNv3ntL6b2vp/Xn+B6 CLIENT: Task: Task::done() CLIENT: Task: emitting finished --------------------------------------------------
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. *** This bug has been marked as a duplicate of 426807 ***