Red Hat Bugzilla – Bug 976529
e-mail compose hang
Last modified: 2013-07-22 21:16:48 EDT
Created attachment 763558 [details] thread apply all bt of evolution-address-factory evolution-3.8.3-1.fc19.x86_64 I semi-regularly get a hang when I try to compose a new mail message. I just get a solid grey screen. I can click the X in the top right and eventually can 'force quit'. (or I can do what I normally do and pkill -9 evolution) The last couple of times I hit this problem I had one compose window open and clicked to compose a second e-mail. The second compose window was what actually hung. Attached you will a copy of 'thread apply all backtrace' after I attached gdb to the evolution-address-factory process while the grey screen hang was happening.
Looks like https://bugzilla.gnome.org/show_bug.cgi?id=698912.
Thanks for a bug report. Could you get backtrace of evolution itself, please? As long as evolution is frozen, then its backtrace matters. From that we can move to other processes to see what they do (like for the addressbook factory, as you already did), but for the starter the frozen process is the place where to begin. If Matthew's bug will be the right one, then I'll upstream this there. If not, I'll upstream it in a new bug report. It's because it doesn't seem to be Fedora issue, but a general evolution issue, for which the Gnome bugzilla is the place where to report issues.
libsoup-2.42.2-2.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/libsoup-2.42.2-2.fc19
Package libsoup-2.42.2-2.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing libsoup-2.42.2-2.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-12976/libsoup-2.42.2-2.fc19 then log in and leave karma (feedback).
libsoup-2.42.2-2.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.