GNOME Bugzilla – Bug 445428
crash in Tasks: Just starting. Made a fe...
Last modified: 2007-06-12 00:40:09 UTC
What were you doing when the application crashed? Just starting. Made a few attempts with the same result. 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: No Accessibility: Disabled GTK+ Theme: Glider Icon Theme: gnome Memory status: size: 92712960 vsize: 92712960 resident: 21651456 share: 13910016 rss: 21651456 rss_rlim: 4294967295 CPU usage: start_time: 1181294034 rtime: 209 utime: 192 stime: 17 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 -1208883488 (LWP 5024)] (no debugging symbols found) 0x00a3d402 in __kernel_vsyscall ()
+ Trace 139316
Thread 1 (Thread -1208883488 (LWP 5024))
----------- .xsession-errors (6 sec old) --------------------- localuser:demichev being added to access control list SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/3769 ** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name ** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name error getting update info: Cannot open/read repomd.xml file for repository: fedora CalDAV Eplugin starting up ... (evolution:4279): e-data-server-DEBUG: Loaded default categories CalDAV Eplugin starting up ... Loading "installonlyn" plugin CalDAV Eplugin starting up ... Loading "installonlyn" plugin Loading "installonlyn" plugin Loading "installonlyn" plugin CalDAV Eplugin starting up ... CalDAV Eplugin starting up ... --------------------------------------------------
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 425129 ***