GNOME Bugzilla – Bug 484180
crash in Tasks: Nothing - the screen sav...
Last modified: 2007-10-07 10:17:34 UTC
Version: 2.10 What were you doing when the application crashed? Nothing - the screen saver was on.... 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.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 106737664 vsize: 106737664 resident: 37445632 share: 29188096 rss: 37445632 rss_rlim: 4294967295 CPU usage: start_time: 1191685124 rtime: 131 utime: 115 stime: 16 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 -1208756512 (LWP 3533)] [New Thread -1242567792 (LWP 4314)] [New Thread -1232077936 (LWP 3558)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 168355
Thread 1 (Thread -1208756512 (LWP 3533))
----------- .xsession-errors (3299 sec old) --------------------- localuser:terrapin being added to access control list Sat Oct 6 09:38:22 MDT 2007 SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/3268 error getting update info: Cannot retrieve repository metadata (repomd.xml) for repository: livna. Please verify its path and try again ** Message: <info> You are now connected to the wireless network 'thing1'. CalDAV Eplugin starting up ... ** (evolution:3533): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:3533): DEBUG: mailto URL program: evolution camel-Message: -- --------------------------------------------------
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 ***