GNOME Bugzilla – Bug 494966
crash in Tasks:
Last modified: 2007-11-11 12:08:36 UTC
Version: 2.10 What were you doing when the application crashed? 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.23.1-21.fc7 #1 SMP Thu Nov 1 21:09:24 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Neu Memory status: size: 113451008 vsize: 113451008 resident: 42299392 share: 30867456 rss: 42299392 rss_rlim: 4294967295 CPU usage: start_time: 1194529013 rtime: 246 utime: 197 stime: 49 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 -1208690976 (LWP 3057)] [New Thread -1221256304 (LWP 3118)] [New Thread -1242236016 (LWP 3068)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 176315
Thread 1 (Thread -1208690976 (LWP 3057))
----------- .xsession-errors (9 sec old) --------------------- ** (evolution:3057): 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 XS[src/xmms-sid.c:xs_init:216]: xs_init() XS[src/xs_config.c:xs_init_configuration:164]: initializing configuration ... XS[src/xs_config.c:xs_read_configuration:265]: loading from config-file ... XS[src/xs_config.c:xs_read_configuration:320]: OK XS[src/xmms-sid.c:xs_reinit:163]: initializing emulator engine #1... XS[src/xmms-sid.c:xs_reinit:177]: init#1: OK, 1 XS[src/xmms-sid.c:xs_reinit:189]: init#2: OK, 0 XS[src/xmms-sid.c:xs_init:226]: OK (evolution:3057): camel-WARNING **: No from set for message (evolution:3057): camel-WARNING **: No from set for 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 431459 ***