GNOME Bugzilla – Bug 462222
crash in Tasks: pressing send/receive to...
Last modified: 2007-10-07 18:49:50 UTC
Version: 2.10 What were you doing when the application crashed? pressing send/receive to fetch my mail from gmail 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-27.fc7 #1 SMP Tue Jul 17 17:13:26 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: MurrinaLightGraphite Icon Theme: glass-icons Memory status: size: 117411840 vsize: 117411840 resident: 48902144 share: 29401088 rss: 48902144 rss_rlim: 4294967295 CPU usage: start_time: 1185902897 rtime: 191 utime: 135 stime: 56 cutime:4 cstime: 10 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 -1208588576 (LWP 3828)] [New Thread -1263031408 (LWP 3886)] [New Thread -1231029360 (LWP 3858)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 151879
Thread 1 (Thread -1208588576 (LWP 3828))
----------- .xsession-errors (8 sec old) --------------------- (evolution:3828): camel-pop3-provider-WARNING **: Bad server response: anst=E4llda, l=E4gga ner postkontor, f=F6rs=E4mra arbetstiderna och (evolution:3828): camel-pop3-provider-WARNING **: Bad server response: m=F6jligheterna till pension. Och som f=F6r att understryka det (evolution:3828): camel-pop3-provider-WARNING **: Bad server response: l=F6gnaktiga i deras p=E5st=E5enden om att det saknas pengar f=E5r (evolution:3828): camel-pop3-provider-WARNING **: Bad server response: cheferna bonusar p=E5 =F6ver 500 mille sammanlagt. Tro fan att (evolution:3828): camel-pop3-provider-WARNING **: Bad server response: arbetarna =E4r sura. --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
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 ***