GNOME Bugzilla – Bug 750357
Stuck after restart
Last modified: 2017-08-08 20:42:32 UTC
Might just be a dup of bug 750146? Restarted Evolution after a crash (no idea where Fedora 22 put that, Fedora 21 at least popped up abrt). Evolution got stuck in my GMail IMAP account, not changing for half an hour and not displaying any (new, not yet downloaded) messages. Screenshot of the status bar attached. Trying to cancel those actions just adds a " (cancelling)" suffix to the tooltips, but nothing happens. $:andre\> gdb evolution GNU gdb (GDB) Fedora 7.9.1-13.fc22 (gdb) run Starting program: /usr/bin/evolution [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/libthread_db.so.1". ** (evolution:18139): CRITICAL **: categories_icon_theme_hack: assertion 'filename != NULL && *filename != '\0'' failed [New Thread 0xb0a10b40 (LWP 18145)] (evolution:18139): GLib-GObject-WARNING **: The property GtkSettings:gtk-button-images is deprecated and shouldn't be used anymore. It will be removed in a future version. (evolution:18139): Gtk-WARNING **: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files [New Thread 0xaf5ffb40 (LWP 18147)] Detaching after fork from child process 18164. [New Thread 0xa917bb40 (LWP 18175)] [New Thread 0xa7978b40 (LWP 18178)] [New Thread 0xa8179b40 (LWP 18177)] [Thread 0xa917bb40 (LWP 18175) exited] [Thread 0xa7978b40 (LWP 18178) exited] (evolution:18139): GLib-GObject-WARNING **: The property GtkSettings:gtk-menu-images is deprecated and shouldn't be used anymore. It will be removed in a future version. [Thread 0xa8179b40 (LWP 18177) exited] (evolution:18139): GLib-GObject-WARNING **: The property GtkCellRendererPixbuf:stock-id is deprecated and shouldn't be used anymore. It will be removed in a future version. [New Thread 0x9bcfab40 (LWP 18359)] [New Thread 0x9a4f7b40 (LWP 18358)] [New Thread 0x9ccfcb40 (LWP 18353)] [New Thread 0xa6164b40 (LWP 18352)] [New Thread 0x9c4fbb40 (LWP 18313)] [New Thread 0x9d4fdb40 (LWP 18310)] [New Thread 0xa917bb40 (LWP 18309)] [New Thread 0xa897ab40 (LWP 18308)] [New Thread 0x9f156b40 (LWP 18305)] [New Thread 0xac21db40 (LWP 18303)] [New Thread 0x9f957b40 (LWP 18297)] [New Thread 0xa4160b40 (LWP 18267)] [New Thread 0xa4961b40 (LWP 18266)] [New Thread 0xa997cb40 (LWP 18252)] [New Thread 0xaca47b40 (LWP 18158)] [New Thread 0xadf0bb40 (LWP 18155)] [New Thread 0xae830b40 (LWP 18154)] [New Thread 0xaff79b40 (LWP 18146)] ^C Program received signal SIGINT, Interrupt. 0xb7fdbbc8 in __kernel_vsyscall () (gdb) thread apply all bt
+ Trace 235121
(gdb) list 421 EShell *shell; 422 GSettings *settings; 423 #ifdef DEVELOPMENT 424 gboolean skip_warning_dialog; 425 #endif 426 GError *error = NULL; 427 428 #ifdef G_OS_WIN32 429 e_util_win32_initialize (); 430 #endif (gdb) info register eax 0xfffffdfc -516 ecx 0x4 4 edx 0x21 33 ebx 0xa4773a8 172454824 esp 0xbfffeda4 0xbfffeda4 ebp 0x4 0x4 esi 0x8077428 134706216 edi 0xa4773a8 172454824 eip 0xb7fdbbc8 0xb7fdbbc8 <__kernel_vsyscall+16> eflags 0x292 [ AF SF IF ] cs 0x73 115 ss 0x7b 123 ds 0x7b 123 es 0x7b 123 fs 0x0 0 gs 0x33 51
Created attachment 304539 [details] Status bar screenshot
(In reply to André Klapper from comment #0) > Might just be a dup of bug 750146? You a right, it's a very similar deadlock as in the above bug report. Even it's not exactly the same thing. Please try with the upcoming 3.16.3, to be released the next week. Thanks in advance.
If bug 751155 is a dup then this still happens. Local filtering might play a big role here.
*** Bug 751155 has been marked as a duplicate of this bug. ***
I realized that all these stacktraces refer to the very same header value in the filter and to the same single local filter rule: (match-all (header-contains \"X-Example-Header\" \"<#whatever>\")) So I've deleted the local filter rule about the <#whatever> header value. Now let's see if that'll improve things.
Haven't seen this for ages.