GNOME Bugzilla – Bug 451946
crash in Evolution: I have been playing with...
Last modified: 2008-02-21 17:57:44 UTC
What were you doing when the application crashed? I have been playing with different settings for a while, and set up a couple of new accounts. Everything was working fine. The application has crashed as soon as I had clicked the close button. Distribution: Gentoo Base System release 1.12.9 Gnome Release: 2.16.3 2007-06-17 (Gentoo) BugBuddy Version: 2.16.1 System: Linux 2.6.20-gentoo-r8 #1 Tue May 29 06:09:58 EEST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled Memory status: size: 261795840 vsize: 0 resident: 261795840 share: 0 rss: 88883200 rss_rlim: 0 CPU usage: start_time: 1182979682 rtime: 0 utime: 13198 stime: 0 cutime:12655 cstime: 0 timeout: 543 it_real_value: 0 frequency: 45 Backtrace was generated from '/usr/bin/evolution-2.8' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1232897856 (LWP 27267)] [New Thread -1382835312 (LWP 30154)] [New Thread -1353069680 (LWP 27324)] [New Thread -1344283760 (LWP 27320)] [New Thread -1335891056 (LWP 27319)] [New Thread -1327498352 (LWP 27318)] [New Thread -1317905520 (LWP 27317)] [New Thread -1309512816 (LWP 27315)] [New Thread -1284334704 (LWP 27314)] [New Thread -1301120112 (LWP 27313)] [New Thread -1292727408 (LWP 27309)] [New Thread -1275942000 (LWP 27307)] [New Thread -1267090544 (LWP 27306)] [New Thread -1258697840 (LWP 27305)] 0xb7fda410 in __kernel_vsyscall ()
+ Trace 144368
Thread 4 (Thread -1344283760 (LWP 27320))
----------- .xsession-errors (69441 sec old) --------------------- nsPluginNativeWindowGtk2: NPPVpluginNeedsXEmbed=0 nsPluginNativeWindowGtk2: call SetWindow with xid=0x345ecde For application/x-shockwave-flash found plugin /opt/netscape/plugins/libflashplayer.so nsPluginNativeWindowGtk2: NPPVpluginNeedsXEmbed=0 nsPluginNativeWindowGtk2: call SetWindow with xid=0x345eeba About to create new ws_info... About to create new xtbin of 240 X 60 from 0x99bbac0... About to show xtbin(0xa840b30)... completed gtk_widget_show(0xa840b30) nsPluginNativeWindowGtk2: NPPVpluginNeedsXEmbed=0 nsPluginNativeWindowGtk2: call SetWindow with xid=0x345eeba nsPluginNativeWindowGtk2: NPPVpluginNeedsXEmbed=0 nsPluginNativeWindowGtk2: call SetWindow with xid=0x345eeba ...Too much output, ignoring rest... --------------------------------------------------
Damn! I was able to unintentionally reproduce the error two more times during the same day!! That bothers. On the bright side, now I can tell _exactly_ what makes it crash. The algorithm is as follows. Make sure you have an account, which Evolution does not know the password for. Run a check for new mail and let it open an "Enter password" dialog. Now merely try to close the application by pressing the cross in the upper-right corner. Here it is, crashed again!
It has crashed again. I don't want to post any more bugs because it seems they are caused by a single reason. What makes it crash is checking this setting: Preferences -> my imap account on inbox.ru (mail.ru) -> Receiving options -> Automatically synchronize remote mail locally. There were no open dialog windows, so I was happy too early yesterday. As for any other options that might matter, here they are: server: imap.mail.ru:143 secure connection: TLS Authentication: password ... check for new messages in all folders on (I have pretty much of them) other settings are either not important or switched off
Evolution has crashed again and again. I don't want to post any more bugs because it seems they are caused by a single reason. What makes it crash today is switching on one specific imap account or sometimes checking this setting: Preferences -> the mentioned account -> Receiving options -> Automatically synchronize remote mail locally. There were no open dialog windows, so I was happy too early yesterday. As for any other options that might matter, here they are: server: imap.mail.ru:143 secure connection: TLS Authentication: password ... check for new messages in all folders on other settings are either not important or switched off They have pretty bad security: POP uses plain authentication with no encryption and the certificate for imap is outdated. In this light I wouldn't be surprised if TLS encryption is just wrongly implemented at their side. However, I cannot say any more for sure. Should anyone need a testing account but have problems with Russian, I can setup one as soon as will be back from holidays. Otherwise, there is not much advice in the help center, and you can directly contact the support (they should speak English).
Only notice that the old function session_thread_received was renamed to session_thread_proxy somewhere between revisions 6679 and 7577 (the later one from Mon Jan 8 16:10:19 2007). *** This bug has been marked as a duplicate of 434802 ***