GNOME Bugzilla – Bug 445472
crash in Tasks: closing the application
Last modified: 2007-06-13 11:54:57 UTC
What were you doing when the application crashed? closing the application 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: Clearlooks Memory status: size: 150732800 vsize: 150732800 resident: 29798400 share: 18321408 rss: 29798400 rss_rlim: 4294967295 CPU usage: start_time: 1181306011 rtime: 421 utime: 376 stime: 45 cutime:0 cstime: 0 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 -1209186592 (LWP 2586)] [New Thread -1376515184 (LWP 2659)] [New Thread -1279345776 (LWP 2599)] (no debugging symbols found) 0x0029f402 in __kernel_vsyscall ()
+ Trace 139346
Thread 2 (Thread -1376515184 (LWP 2659))
----------- .xsession-errors (1458 sec old) --------------------- Increasing i (evolution:1935): libecal-WARNING **: e-cal.c:317: Unexpected response (evolution:1935): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0 ** Message: Response 1 camel-Message: -- (evolution:1935): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0 ** Message: Response 1 (evolution:1935): e-data-server-DEBUG: Loading categories from "/home/torbjorn/.evolution/categories.xml" (evolution:1935): e-data-server-DEBUG: Loaded 29 categories (evolution:1935): libecal-WARNING **: e-cal.c:317: Unexpected response (evolution:1935): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0 (evolution:1935): libecal-WARNING **: e-cal.c:317: Unexpected response (evolution:1935): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0 --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Could you please install some debugging packages [1], start the application as normal, and reproduce the crash, if possible? Once bug-buddy pops up, you can find the stacktrace in the Details, now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks in advance! [1] debugging packages for evolution, evolution-data-server, gtkhtml, gtk, glib, gnome-vfs, libgnome and libgnomeui (as far as those packages are provided by your distribution). More details can be found here: http://live.gnome.org/GettingTraces
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 445309 ***