GNOME Bugzilla – Bug 484437
crash in Tasks: Fetching Mail..... Gmail...
Last modified: 2007-10-07 17:53:00 UTC
Version: 2.10 What were you doing when the application crashed? Fetching Mail..... Gmail.... pop.gmail.com 995 using SSL 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: Glider Icon Theme: gnome Memory status: size: 130076672 vsize: 130076672 resident: 42385408 share: 33996800 rss: 42385408 rss_rlim: 4294967295 CPU usage: start_time: 1191771932 rtime: 491 utime: 437 stime: 54 cutime:1 cstime: 3 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 -1208523040 (LWP 3300)] [New Thread -1296594032 (LWP 3357)] [New Thread -1275614320 (LWP 3354)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 168558
Thread 1 (Thread -1208523040 (LWP 3300))
----------- .xsession-errors (13 sec old) --------------------- Window manager warning: Lost connection to the display ':0.0'; most likely the X server was shut down or you killed/destroyed the window manager. beryl: Plugin 'showdesktop' can't be activated because plugin 'fadeDesktop' is already providing feature 'showdesktop' Couldn't initialise showdesktop. This should not happen! kbuildsycoca running... DCOP Cleaning up dead connections. Launched ok, pid = 3182 ** Message: <info> You are now connected to the wireless network 'TEST'. CalDAV Eplugin starting up ... ** (evolution:3300): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:3300): DEBUG: mailto URL program: evolution (evolution:3300): e-data-server-ui-WARNING **: Key file does not have group 'Passwords-Mail' --------------------------------------------------
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 ***