GNOME Bugzilla – Bug 772660
After some time, Evolution stops being able to display mail content in either preview pane or dedicated window
Last modified: 2016-12-05 13:08:02 UTC
As mentioned in #778073. With current Fedora 25 - evolution-3.22.0-1.fc25.x86_64 , webkitgtk4-2.13.92-1.fc25.x86_64 - I'm seeing a bug where after running for some time, Evolution stops being able to display mails when they're selected. The preview pane will just show blank white space, or get stuck displaying whatever mail it was displaying before the bug kicked in. Double-clicking an email opens a new window with chrome and a toolbar, but the main pane is entirely grey. If I run Evo from a console, then when the bug has kicked in, every time I click on a different mail, after a few seconds a couple of these messages show up in the console: (evolution:19487): evolution-util-WARNING **: Failed to call a DBus Proxy method org.gnome.Evolution.WebExtension::AddCSSRuleIntoStyleSheet: Timeout was reached (evolution:19487): evolution-util-WARNING **: Failed to call a DBus Proxy method org.gnome.Evolution.WebExtension::AddCSSRuleIntoStyleSheet: Timeout was reached The last couple of messages before those messages started appearing are: (process:19509): GLib-GObject-WARNING **: g_object_weak_unref: couldn't find weak ref 0x7f6e02a3e580(0x55d260344f38) (evolution:19487): camel-imapx-WARNING **: camel_imapx_server_process_command_sync: [F] 0x55f6e9b0f320: Starting command 0x55f6ea30b120 (STATUS) while still processing 0x55f6e94f8b60 (NOOP) but as the messages aren't timestamped, I don't know if those came immediately before the bug kicked in, or long before it. Once this bug starts happening, I have to quit and restart Evo to fix it.
(In reply to Adam Williamson from comment #0) > (process:19509): GLib-GObject-WARNING **: g_object_weak_unref: couldn't find > weak ref 0x7f6e02a3e580(0x55d260344f38) > > (evolution:19487): camel-imapx-WARNING **: > camel_imapx_server_process_command_sync: [F] 0x55f6e9b0f320: Starting > command 0x55f6ea30b120 (STATUS) while still processing 0x55f6e94f8b60 (NOOP) > > but as the messages aren't timestamped, I don't know if those came > immediately before the bug kicked in, or long before it. They're bugs at any rate; I bet Milan would appreciate a backtrace taken using G_DEBUG=fatal-warnings in the environment.
Thanks for a bug report. The "(process:19509)" warnings may come from the WebKitWebProcess, from the evolution's web extension. I guess so at least. I guess there happened something with the WebKitWebPorcess, which is responsible to show the message content. It would be good if you could get a backtrace of the running evolution and the associated WebKitWebProcess, to see what they both do. You can get the backtrace with command like this: $ gdb --batch --ex "t a a bt" -pid=`pidof evolution` &>bt.txt Please check the bt.txt for any private information, like passwords, email address, server addresses,... I usually search for "pass" at least (quotes for clarity only). Please install debuginfo packages for the evolution only, definitely not for the webkitgtk4 as of now.
I updated to Evo 3.22.1 yesterday, and also switched to Wayland, and the bug hasn't shown up again yet; if it does, I'll get the backtrace.
Thanks for the update. I'll close this for the time being. Feel free to reopen when you've more information. Thanks in advance.
Bug #775537 contains a similar issue, with more debugging info, and more importantly the reporter can reproduce this, thus I mark this as a duplicate of it. *** This bug has been marked as a duplicate of bug 775537 ***