GNOME Bugzilla – Bug 474294
crash in Tasks: send/receive mail
Last modified: 2007-09-24 17:51:52 UTC
Version: 2.10 What were you doing when the application crashed? send/receive mail Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.22.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 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: 126414848 vsize: 126414848 resident: 44871680 share: 31834112 rss: 44871680 rss_rlim: 4294967295 CPU usage: start_time: 1189100274 rtime: 600 utime: 554 stime: 46 cutime:2 cstime: 4 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 -1208187168 (LWP 26709)] [New Thread -1287656560 (LWP 26797)] [New Thread -1226642544 (LWP 26736)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 160935
Thread 1 (Thread -1208187168 (LWP 26709))
----------- .xsession-errors (334 sec old) --------------------- in emp_apps_open_in in emp_apps_open_in in emp_apps_open_in CalDAV Eplugin starting up ... evolution-shell-Message: Killing old version of evolution-data-server... ** (evolution:25735): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:25735): DEBUG: mailto URL program: evolution xscreensaver-command: activating and locking. xscreensaver-command: activating and locking. CalDAV Eplugin starting up ... evolution-shell-Message: Killing old version of evolution-data-server... ** (evolution:26709): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:26709): DEBUG: mailto URL program: evolution --------------------------------------------------
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 364700 ***