So huge congrats, fist time ever to launch gnome-shell on wayland on non-intel hardware. Big win.
But, I was only able to change the window getting the keyboard input by clicking on the title bar. Just clicking on a window did not change the keyboard input. This made using chrome impossible, as it did not have a title bar. I could click in the url bar, but the keyboard input remained in another window (like a terminal or evolution)
Similar issue here regarding mouse focus under XWayland: menu items "Edit > Preferences" and "Edit > Profile Preferences" of GNOME terminal sometimes do not react when the left mouse button is pressed. Normal behaviour under normal GNOME session.
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.
More information and reason for this action is here:
Looks like a gnome-shell/mutter issue rather than gnome-session (ie it's filed against the wrong component)
(In reply to Joachim Frieben from comment #1)
> Similar issue here regarding mouse focus under XWayland: menu items "Edit >
> Preferences" and "Edit > Profile Preferences" of GNOME terminal sometimes do
> not react when the left mouse button is pressed. Normal behaviour under
> normal GNOME session.
That's a different issue, what you describe is bug 1188289 which requires 2 patches, one in mutter to disable the COW and one in Xwayland to remove the XYToWindow() routine which is not needed anymore once the COW is disabled in mutter with Wayland.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.