GNOME Bugzilla – Bug 487527
crash in Tasks: Opening application, sto...
Last modified: 2007-10-22 22:49:42 UTC
What were you doing when the application crashed? Opening application, storing folders. Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 157356032 vsize: 157356032 resident: 36343808 share: 16257024 rss: 36343808 rss_rlim: 4294967295 CPU usage: start_time: 1192632588 rtime: 2415 utime: 1876 stime: 539 cutime:1 cstime: 3 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 -1208785184 (LWP 20532)] [New Thread -1301836912 (LWP 20568)] [New Thread -1270400112 (LWP 20557)] [New Thread -1238930544 (LWP 20552)] (no debugging symbols found) 0x00b54402 in __kernel_vsyscall ()
+ Trace 170862
Thread 4 (Thread -1238930544 (LWP 20552))
----------- .xsession-errors (3954 sec old) --------------------- (evolution:2538): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0 (evolution:2538): camel-local-provider-WARNING **: Didn't get the next message where I expected (105606530) got 105606529 instead (evolution:2538): evolution-mail-WARNING **: Error occurred while existing dialogue active: Summary and folder mismatch, even after a sync (evolution:2538): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0 (evolution:2538): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0 (evolution:2538): camel-local-provider-WARNING **: Didn't get the next message where I expected (105606530) got 105606529 instead (evolution:2538): evolution-mail-WARNING **: Error occurred while existing dialogue active: Summary and folder mismatch, even after a sync ...Too much output, ignoring rest... --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 339602 ***