martin rudalics <rudalics@gmx.at> writes:

>> The problem is still present (using 43701a8) with XMonad: switching to a
>> different virtual desktop leads to a blank screen. It still responds to (at
>> least) some keyboard shortcuts (I can close with C-x C-x) and if the menu
>
> Is that C-x C-c or is C-x C-x special for you?
>
>> bar or the toolbar are active they also respond to some mouse clicks.
>>
>> Interestingly, the problem does not show up if I launch Emacs in an XMonad
>> session inside XMonad using xephyr.
>
> I'm a bit too dense to understand what you are doing and what does not
> work for you.  Is the behavior of Xmonad showing an Emacs frame OK as
> long as you do not switch to a different virtual desktop?  Are tool and
> menu bar shown in the blank screen case?  Does a blank screen blank out
> other things besides Emacs.  Does it work when Emacs is not supposed to
> be shown on that "different virtual desktop"?
>
> In either case please try to identify the commit that broke this - I
> have my slight doubts that it is 483c5e9.  Could it be already a190b4c?

Bisected the following behaviour on Xmonad to 483c5e9.  In the
screenshots below a red or black border indicates which frame Xmonad
thinks is selected or unselected, respectively.  Similarly a filled or
hollow box cursor shows which frame Emacs thinks is selected or
unselected, respectively.

0. emacs -Q