GNOME Bugzilla – Bug 516661
crash in Tasks:
Last modified: 2008-02-15 13:13:44 UTC
Version: 2.10 What were you doing when the application crashed? Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.8-34.fc7 #1 SMP Thu Nov 22 23:05:33 EST 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: 148971520 vsize: 148971520 resident: 39751680 share: 32337920 rss: 39751680 rss_rlim: 4294967295 CPU usage: start_time: 1203077048 rtime: 47 utime: 43 stime: 4 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 -1209162016 (LWP 5881)] [New Thread -1305826416 (LWP 5909)] [New Thread -1269838960 (LWP 5903)] [New Thread -1248859248 (LWP 5900)] [New Thread -1226245232 (LWP 5898)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 189294
Thread 1 (Thread -1209162016 (LWP 5881))
----------- .xsession-errors --------------------- localuser:admin being added to access control list SESSION_MANAGER=local/unix:/tmp/.ICE-unix/5714 CalDAV Eplugin starting up ... ** (evolution:5881): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:5881): 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 calendar-gui-Message: launch_alarm_daemon_cb(): Le processus fils n'a pas renvoyé de message d'erreur, une erreur inconnue s'est produite 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 ***