GNOME Bugzilla – Bug 479056
crash in Tasks: Sending and receiving ma...
Last modified: 2007-09-24 17:35:12 UTC
Version: 2.10 What were you doing when the application crashed? Sending and receiving mail............just turned the system on but it appeared finished loading everything - a weird one never happened b4 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.5-76.fc7 #1 SMP Thu Aug 30 13:47:21 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: 129343488 vsize: 129343488 resident: 40669184 share: 32378880 rss: 40669184 rss_rlim: 4294967295 CPU usage: start_time: 1190399681 rtime: 120 utime: 106 stime: 14 cutime:0 cstime: 1 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 -1208658208 (LWP 3581)] [New Thread -1274762352 (LWP 3634)] [New Thread -1225757808 (LWP 3603)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 164484
Thread 1 (Thread -1208658208 (LWP 3581))
----------- .xsession-errors (12 sec old) --------------------- localuser:dad being added to access control list SESSION_MANAGER=local/host217-40-248-42.in-addr.btopenworld.com:/tmp/.ICE-unix/3357 winscard_clnt.c:3349:SCardCheckDaemonAvailability() PCSC Not Running Unable to open desktop file /home/dad/Desktop/SAMBA configuration to join MS workgroup - LinuxQuestions.org.desktop for panel launcher: No such file or directory Unable to open desktop file /home/dad/Desktop/System - Summary.desktop for panel launcher: No such file or directory CalDAV Eplugin starting up ... ** (evolution:3581): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:3581): 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 ***