GNOME Bugzilla – Bug 489531
crash in Tasks: bonjour, ouverture d'evo...
Last modified: 2007-10-24 20:11:54 UTC
Version: 2.10 What were you doing when the application crashed? bonjour, ouverture d'evolution pour consultation des mails 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: 126320640 vsize: 126320640 resident: 44847104 share: 36593664 rss: 44847104 rss_rlim: 4294967295 CPU usage: start_time: 1193165574 rtime: 128 utime: 113 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 -1208166688 (LWP 3145)] [New Thread -1293968496 (LWP 3205)] [New Thread -1219716208 (LWP 3204)] [New Thread -1263547504 (LWP 3192)] [New Thread -1242567792 (LWP 3169)] (no debugging symbols found) 0x0012d402 in __kernel_vsyscall ()
+ Trace 172322
Thread 1 (Thread -1208166688 (LWP 3145))
----------- .xsession-errors --------------------- localuser:jo being added to access control list SESSION_MANAGER=local/unix:/tmp/.ICE-unix/2932 CalDAV Eplugin starting up ... ** (evolution:3145): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:3145): 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 (evolution:3145): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution:3145): camel-WARNING **: camel_exception_get_id called with NULL parameter. --------------------------------------------------
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 431459 ***