Created attachment 582050 [details] backtrace Description of problem: Formatting Message process hang evolution and stop view another messages Video: https://docs.google.com/open?id=0B0nwzlfiB4aQb0wtWG96OXZWWE0
Created attachment 582074 [details] backtrace 2
Created attachment 582250 [details] backtrace, again hang while format message
Created attachment 582256 [details] backtrace
Thanks for a bug report. This is particularly known issue, when evolution tries to talk to your addressbooks, but if the evolution-addresssbook-factory is stuck in something, then the evolution keeps waiting for a response forever. This might be hopefully fixed within evolution 3.6.0 (to be part of Fedora 18). There exists a workaround, open Edit->Preferences->Mail Preferences and make sure that on tab 'HTML Messages' is _not_ checked "Load images only in messages from contacts" and in tab 'Headers' is _not_ checked "Show the photograph of sender in the message preview". The later causes stuck state for you. Corresponding upstream bug report is: https://bugzilla.gnome.org/show_bug.cgi?id=361145
Created attachment 583448 [details] HTML Messages tab
Created attachment 583449 [details] Headers tab
As you can see "Load images only in messages from contacts" and "Show the photograph of sender in the message preview" is unchecked, but it not help to workaround my problem.
Even after restart of evolution? Because the backtrace shows checking for contact's photo and if I test with load all images and disabled show contact photo then the function isn't called for me, neither with text/plain, nor HTML messages. Though the restart of evolution wasn't needed for me, disabling/enabling sender's photo was used immediately. Maybe it's stuck on something else now, could you get a new backtrace, please? I would like to see backtrace of evolution-addressbook-factory too, please, I guess it's stuck and causes hang of evolution.
Created attachment 584840 [details] backtrace evolution-addressbook-factory
Created attachment 584841 [details] backtrace evolution-alarm-notify
Created attachment 584842 [details] backtrace evolution-calendar-factory
Created attachment 584843 [details] backtrace evolution
Please look my new backtraces
evolution-addressbook-factory: Most of the threads are stuck in e_book_backend_authenticate_user, waiting evolution-alarm-notify: it's basically idle evolution-calendar-factory: also basically idle evolution: waiting for a response from the addressbook factory, still under em_utils_contact_photo, which you might have disabled. I made a full update on my F17 machine, and i retested this, and if I disable the Show sender's photo..." from mail Preferences Headers tab, then this code is not called. What do you see, if you run from console: $ dconf read /org/gnome/evolution/mail/show-sender-photo it should return false as it does for me when I have the option disabled. If not, please execute: $ dconf write /org/gnome/evolution/mail/show-sender-photo false and the evolution should stop searching for the photo when you select the next message (if it's already in a stuck state then it'll not help). Please note that the backtraces are missing all the debug information, because the update of binary packages didn't update also debuginfo packages, thus there is a version mismatch between binary and debuginfo. You can check that with: $ rpm -qa | grep evolution | sort
[mikhail@telecon17l ~]$ dconf read /org/gnome/evolution/mail/show-sender-photo false Ups already false... [mikhail@telecon17l ~]$ rpm -qa | grep evolution | sort evolution-3.4.1-2.fc17.i686 evolution-data-server-3.4.1-2.fc17.i686 evolution-data-server-debuginfo-3.4.2-1.fc17.i686 evolution-debuginfo-3.4.2-1.fc17.i686 evolution-ews-3.4.1-1.3.fc17.i686 evolution-ews-debuginfo-3.4.2-1.fc17.i686 evolution-exchange-3.4.1-1.fc17.i686 evolution-exchange-debuginfo-3.4.1-1.fc17.i686 evolution-mapi-3.4.1-3.fc17.i686 evolution-mapi-debuginfo-3.4.2-1.fc17.i686 evolution-NetworkManager-3.4.1-2.fc17.i686
(In reply to comment #15) > [mikhail@telecon17l ~]$ dconf read /org/gnome/evolution/mail/show-sender-photo > false > > Ups already false... Then it doesn't make sense, the code which blocks on you should not be called at all, the same as it does for me. Doues evolution claim anything on console when you run it, please? > [mikhail@telecon17l ~]$ rpm -qa | grep evolution | sort > evolution-data-server-3.4.1-2.fc17.i686 > evolution-data-server-debuginfo-3.4.2-1.fc17.i686 > ... Interesting, you've this the other way than it usually happens to me. Your binary package version is 3.4.1, while debuginfo package is 3.4.2, so you've newer debug info than binary package. Maybe you've updates-testing disabled? I would try to re-update with yum.
(In reply to comment #16) > > Then it doesn't make sense, the code which blocks on you should not be called > at all, the same as it does for me. Doues evolution claim anything on console > when you run it, please? (evolution:24439): libsoup-WARNING **: NTLM single-sign-on by using /usr/bin/ntlm_auth failed Unknown parameter encountered: "max log size" Ignoring unknown parameter "max log size" Unknown parameter encountered: "load printers" Ignoring unknown parameter "load printers" Unknown parameter encountered: "cups options" Ignoring unknown parameter "cups options" Unknown parameter encountered: "writable" Ignoring unknown parameter "writable" Unknown parameter encountered: "guest ok" Ignoring unknown parameter "guest ok" Unknown parameter encountered: "writable" Ignoring unknown parameter "writable" (evolution:24439): libsoup-WARNING **: NTLM single-sign-on by using /usr/bin/ntlm_auth failed Unknown parameter encountered: "max log size" Ignoring unknown parameter "max log size" Unknown parameter encountered: "load printers" Ignoring unknown parameter "load printers" Unknown parameter encountered: "cups options" Ignoring unknown parameter "cups options" Unknown parameter encountered: "writable" Ignoring unknown parameter "writable" Unknown parameter encountered: "guest ok" Ignoring unknown parameter "guest ok" Unknown parameter encountered: "writable" Ignoring unknown parameter "writable" (evolution:24439): libsoup-WARNING **: NTLM single-sign-on by using /usr/bin/ntlm_auth failed Unknown parameter encountered: "max log size" Ignoring unknown parameter "max log size" Unknown parameter encountered: "load printers" Ignoring unknown parameter "load printers" Unknown parameter encountered: "cups options" Ignoring unknown parameter "cups options" Unknown parameter encountered: "writable" Ignoring unknown parameter "writable" Unknown parameter encountered: "guest ok" Ignoring unknown parameter "guest ok" Unknown parameter encountered: "writable" Ignoring unknown parameter "writable" and etc..... > > Interesting, you've this the other way than it usually happens to me. Your > binary package version is 3.4.1, while debuginfo package is 3.4.2, so you've > newer debug info than binary package. Maybe you've updates-testing disabled? I > would try to re-update with yum. oh.. updates-testing repository was be disabled and I do yum update always with --enablerepo=*debuginfo param, now I enable updates-testing repository and re-update all components.
Those "Unknown parameters" I usually see when I have MAPI account enabled, I think they come from samba4 code. These, same as the NTLM single-sign-on messages, may not influence behaviour of the show-sender-photo.
I have a little update on this. I just found out that the setting to use only local addressbooks for contact photo didn't work. This had been fixed within [1], for 3.4.2 of evolution. We are dealing with other issues on that 3.4.2 release within bug #821228 and bug #805927, where I believe this fix [1] uncovered those other issues in the code, sadly on the stable branch. [1] https://bugzilla.gnome.org/show_bug.cgi?id=674381
Hi Milan, Do you think this fix will appear in the stable update of Evolution or will have to install a development version. Currently my Evolution is unusable with Exchange account on Fedora 17. Thanks
(In reply to comment #20) > Do you think this fix will appear in the stable update of Evolution or will > have to install a development version. Currently my Evolution is unusable > with Exchange account on Fedora 17. The change is part of evolution-ews-3.4.2-2, which is in updates-testing from yesterday. See bug #821228 for update details. I'll appreciate if you can give it a try and let me know whether the update helped. The best if you could set karma on the update itself too.