GNOME Bugzilla – Bug 498622
crash in Evolution: Send and receive mails. ...
Last modified: 2009-02-28 11:34:31 UTC
What were you doing when the application crashed? Send and receive mails. Always when click in send/recieve mail its happened. Distribution: Debian lenny/sid Gnome Release: 2.20.1 2007-10-26 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.18-5-k7 #1 SMP Wed Oct 3 00:47:27 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: T-ish-Ubuntulooks Icon Theme: OSX Memory status: size: 130224128 vsize: 130224128 resident: 35147776 share: 19742720 rss: 35147776 rss_rlim: 4294967295 CPU usage: start_time: 1195595439 rtime: 760 utime: 666 stime: 94 cutime:1264 cstime: 86 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 0xb67d26b0 (LWP 3347)] [New Thread 0xb1c96b90 (LWP 3394)] [New Thread 0xb36f3b90 (LWP 3391)] [New Thread 0xb4755b90 (LWP 3390)] [New Thread 0xb3ef4b90 (LWP 3389)] [New Thread 0xb26dcb90 (LWP 3372)] [New Thread 0xb2eddb90 (LWP 3371)] [New Thread 0xb4f5fb90 (LWP 3366)] [New Thread 0xb5760b90 (LWP 3365)] [New Thread 0xb5f61b90 (LWP 3364)] 0xb7f21410 in ?? ()
+ Trace 179012
----------- .xsession-errors --------------------- Excel 97 + (evolution-2.10:3347): camel-pop3-provider-WARNING **: POP3 retrieval failed: Tempo esgotado para conexão Reading file:///tmp/tmp55f584e5.tmp Excel 97 + Reading file:///tmp/tmp4fb928ca.tmp Excel 97 + (evolution-2.10:3347): evolution-mail-WARNING **: Error occurred while existing dialogue active: Não foi possível obter mensagem: 2659: Tempo esgotado para conexão (evolution-2.10:3347): camel-pop3-provider-WARNING **: POP3 retrieval failed: Tempo esgotado para conexão (bug-buddy:6694): Gtk-WARNING **: Não foi possível localizar a ferramenta de temas no module_path: "ubuntulooks", Failed to read a valid object file image from memory. --------------------------------------------------
*** Bug 499926 has been marked as a duplicate of this bug. ***
*** Bug 496293 has been marked as a duplicate of this bug. ***
*** Bug 498628 has been marked as a duplicate of this bug. ***
could be dup of bug 492041
I didn't get what happened here, I do not see any <signal handler called> or something similar. Can you explain more what is happening here, please?
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!