GNOME Bugzilla – Bug 478381
crash in Tasks: bajar correo
Last modified: 2007-09-24 17:37:19 UTC
Version: 2.10 What were you doing when the application crashed? bajar correo 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: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 106225664 vsize: 106225664 resident: 36712448 share: 29306880 rss: 36712448 rss_rlim: 4294967295 CPU usage: start_time: 1190227999 rtime: 85 utime: 73 stime: 12 cutime:1 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 -1208314144 (LWP 4473)] [New Thread -1273508976 (LWP 4524)] [New Thread -1219822704 (LWP 4495)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 164005
Thread 1 (Thread -1208314144 (LWP 4473))
----------- .xsession-errors (12 sec old) --------------------- There seems to be an instance of aMule already running If this is not the case, you may have to remove the file ~/.aMule/muleLock, to allow aMule to run. Attempting to raise current running instance. Initialising aMule Checking if there is an instance already running... There seems to be an instance of aMule already running If this is not the case, you may have to remove the file ~/.aMule/muleLock, to allow aMule to run. Attempting to raise current running instance. CalDAV Eplugin starting up ... ** (evolution:4473): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:4473): DEBUG: mailto URL program: evolution libnm_glib_nm_state_cb: dbus returned an error. (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files --------------------------------------------------
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 ***