GNOME Bugzilla – Bug 504398
crash in Email:
Last modified: 2007-12-19 16:03:25 UTC
Version: 2.10 What were you doing when the application crashed? 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.23.1-10.fc7 #1 SMP Fri Oct 19 15:39:08 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: 129654784 vsize: 129654784 resident: 39190528 share: 30216192 rss: 39190528 rss_rlim: 4294967295 CPU usage: start_time: 1198053437 rtime: 103 utime: 88 stime: 15 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 -1208817952 (LWP 3372)] [New Thread -1263547504 (LWP 3405)] [New Thread -1232077936 (LWP 3401)] [New Thread -1220465776 (LWP 3400)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 182316
Thread 1 (Thread -1208817952 (LWP 3372))
----------- .xsession-errors (9 sec old) --------------------- localuser:roberto being added to access control list SESSION_MANAGER=local/unix:/tmp/.ICE-unix/3094 GSynaptics couldn't initialize. You have to set 'SHMConfig' 'true' in Xorg.conf or XFree86.conf to use GSynaptics Unable to connect to yum-updatesd. Please ensure that the yum-updatesd package is installed and that the service is running. ** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name CalDAV Eplugin starting up ... ** (evolution:3372): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:3372): 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 ***