Description of problem: Lovely. I have a new long draft of email opened. When I minimize ([Win]+H) the main window of Evolution (with folders and lists of messages), then the Composer window is suddenly disabled (the text is grayish and it doesn't get focus and keyboard input even when being clicked on it with mouse). Version-Release number of selected component (if applicable): evolution-ews-3.22.2-1.fc25.x86_64 evolution-3.22.2-1.fc25.x86_64 evolution-help-3.22.2-1.fc25.noarch evolution-data-server-3.22.2-1.fc25.x86_64 How reproducible: 100%. Works like clock Steps to Reproduce: 1. see above 2. 3. Actual results: I cannot have just the Composer window opened, so I could see activity in other windows. Expected results: Minimizing one window of Evolution shouldn't affect my ability to write in others. Additional info:
Thanks for a bug report. I tried to reproduce it, but no luck. It can be that the evolution process got stuck/crashed for some reason. I suppose you run a Wayland session (also because I updated to the current Fedora 25 as of today -2 hours +/-, and the X session, neither the Classic mode of GNOME doesn't start at all). Anyway, could you install debuginfo apckages for the evolution-data-server and evolution (these two are enough for now, no need for the webkit debug info, which is simply too huge), make sure the package versions will match with their binary package counter parts. Then run the evolution from a terminal, reproduce the issue and once the evolution is stuck, get the backtrace of it to see what it tries to do, please? 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).
Created attachment 1228065 [details] output of gdb --pid=$(pidof evolution) Here we are.
Okay, it shows the main thread being stuck in some libEGL code. Could you try to test when you run evolution from a terminal as: $ WEBKIT_DISABLE_COMPOSITING_MODE=1 evolution please?
(In reply to Milan Crha from comment #3) > Okay, it shows the main thread being stuck in some libEGL code. Could you > try to test when you run evolution from a terminal as: > > $ WEBKIT_DISABLE_COMPOSITING_MODE=1 evolution > > please? Yes, with this variable set I cannot reproduce anymore.
Thanks for the confirmation. Evolution contains a change [1] which sets it on its own on start. That had been added for 3.22.3, which is planned for the release next week. [1] https://bugzilla.gnome.org/show_bug.cgi?id=774067