GNOME Bugzilla – Bug 469889
crash in Tasks: Logging in in my GNOME-S...
Last modified: 2007-09-24 18:53:20 UTC
Version: 2.10 What were you doing when the application crashed? Logging in in my GNOME-Session and starting Evolution right after... 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.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 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: 125579264 vsize: 125579264 resident: 35274752 share: 28782592 rss: 35274752 rss_rlim: 4294967295 CPU usage: start_time: 1187961037 rtime: 84 utime: 71 stime: 13 cutime:3 cstime: 8 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1209026848 (LWP 3343)] [New Thread -1263547504 (LWP 3384)] [New Thread -1232077936 (LWP 3380)] [New Thread -1219933296 (LWP 3379)] 0x00110402 in __kernel_vsyscall ()
+ Trace 157587
Thread 1 (Thread -1209026848 (LWP 3343))
----------- .xsession-errors (6 sec old) --------------------- localuser:rehcla being added to access control list No profile for user 'rehcla' found SESSION_MANAGER=local/station1:/tmp/.ICE-unix/2828 winscard_clnt.c:3349:SCardCheckDaemonAvailability() PCSC Not Running Initializing nautilus-open-terminal extension seahorse nautilus module initialized CalDAV Eplugin starting up ... evolution-shell-Message: Killing old version of evolution-data-server... ** (evolution:3343): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:3343): 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 --------------------------------------------------
useful stacktrace for bug #459761 and the dupes..
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 ***