GNOME Bugzilla – Bug 483025
crash in Tasks: I try a password for a a...
Last modified: 2007-10-05 10:04:16 UTC
Version: 2.10 What were you doing when the application crashed? I try a password for a account 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: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 163172352 vsize: 163172352 resident: 38940672 share: 29986816 rss: 38940672 rss_rlim: 4294967295 CPU usage: start_time: 1191433215 rtime: 115 utime: 102 stime: 13 cutime:0 cstime: 2 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 -1208789280 (LWP 4314)] [New Thread -1370543216 (LWP 4346)] [New Thread -1349563504 (LWP 4343)] [New Thread -1221874800 (LWP 4331)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 167460
Thread 1 (Thread -1208789280 (LWP 4314))
----------- .xsession-errors --------------------- (evolution:3781): camel-pop3-provider-WARNING **: Bad server response: Disconnect because authentication is too long (evolution:3781): camel-pop3-provider-WARNING **: Bad server response: Disconnect because authentication is too long (evolution:3781): camel-pop3-provider-WARNING **: Bad server response: Disconnect because authentication is too long (evolution:3781): camel-pop3-provider-WARNING **: Bad server response: Disconnect because authentication is too long CalDAV Eplugin starting up ... 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 ***