GNOME Bugzilla – Bug 514369
crash in Evolution: i've just pressed 'Send ...
Last modified: 2008-09-28 19:19:24 UTC
What were you doing when the application crashed? i've just pressed 'Send / Receive' and the 'Send & Receive Mail' window pop up. Distribution: Debian lenny/sid Gnome Release: 2.20.2 2007-11-29 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.22-2-k7 #1 SMP Fri Aug 31 01:02:37 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Pharago Icon Theme: gartoon Memory status: size: 187592704 vsize: 187592704 resident: 29872128 share: 18399232 rss: 29872128 rss_rlim: 4294967295 CPU usage: start_time: 1202147513 rtime: 95 utime: 83 stime: 12 cutime:0 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution-2.10' Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0xb67c56b0 (LWP 4245)] [New Thread 0xaf1fbb90 (LWP 4333)] [New Thread 0xad9f8b90 (LWP 4332)] [New Thread 0xaf9fcb90 (LWP 4293)] [New Thread 0xae1f9b90 (LWP 4289)] [New Thread 0xae9fab90 (LWP 4288)] [New Thread 0xb1bf9b90 (LWP 4282)] [New Thread 0xb33fcb90 (LWP 4279)] [New Thread 0xb3bfdb90 (LWP 4278)] [New Thread 0xb43feb90 (LWP 4277)] [New Thread 0xb4bffb90 (LWP 4276)] [New Thread 0xb5542b90 (LWP 4275)] [New Thread 0xb5d43b90 (LWP 4274)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 188075
Thread 1 (Thread 0xb67c56b0 (LWP 4245))
----------- .xsession-errors --------------------- get terrix pop://terrix@poczta.o2.pl/ Find Items 0 (evolution-2.10:4245): evolution-mail-WARNING **: Error occurred while existing dialogue active: Could not connect to pop3.poczta.gazeta.pl: Connection refused get terrix pop://terrix@poczta.interia.pl/ Find Items 0 get markpoks pop://markpoks@pop3.wp.pl/ Find Items 0 get euroim103 pop://euroim103@pop3.provider.pl/ Find Items 0 get terrix pop://terrix@pop3.wp.pl/ Find Items 0 get botmatic pop://botmatic@pop3.wp.pl/ Find Items 0 --------------------------------------------------
Dup of bug #523463
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 523463 ***