Bug 1401239

Summary: Minimizing one window of Evolution disables other windows as well
Product: [Fedora] Fedora Reporter: Matěj Cepl <mcepl>
Component: evolutionAssignee: Milan Crha <mcrha>
Status: CLOSED NEXTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 25CC: lucilanga, mbarnes, mcepl, mcrha, tpopela
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: evolution-3.22.3 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-12-06 09:55:15 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
output of gdb --pid=$(pidof evolution) none

Description Matěj Cepl 2016-12-03 21:39:17 UTC 
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:
Comment 1 Milan Crha 2016-12-05 13:05:43 UTC 
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).
Comment 2 Matěj Cepl 2016-12-05 13:52:36 UTC 
Created attachment 1228065 [details]
output of gdb --pid=$(pidof evolution)

Here we are.
Comment 3 Milan Crha 2016-12-05 15:15:24 UTC 
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?
Comment 4 Matěj Cepl 2016-12-05 17:01:52 UTC 
(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.
Comment 5 Milan Crha 2016-12-06 09:55:15 UTC 
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