After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 755103 - XWayland surfaces on hotplugged outputs cannot be focused
XWayland surfaces on hotplugged outputs cannot be focused
Status: RESOLVED NOTGNOME
Product: mutter
Classification: Core
Component: wayland
3.17.x
Other Linux
: Normal normal
: ---
Assigned To: mutter-maint
mutter-maint
Depends on:
Blocks:
 
 
Reported: 2015-09-16 08:37 UTC by Daniel Stone
Modified: 2015-10-19 17:28 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Daniel Stone 2015-09-16 08:37:16 UTC 
SSIA.

I have Chrome running through XWayland, which mostly works. If it's on an external output (DP-2) which gets unplugged, it moves to the internal panel (eDP-1); so far, so good. But on replugging DP-2 and moving Chrome back, it can never acquire the focus. Mouse events are delivered just fine, but no keyboard events will ever be delivered.

New XWayland surfaces on that newly-plugged output will never gain focus either: the only solution is to restart the entire session so the output is live from the beginning.

Not sure if this is a Mutter or XWayland bug.

mutter-3.17.91-1.fc23.x86_64
xorg-x11-server-Xwayland-1.17.2-2.fc23.x86_64
Comment 1 Daniel Stone 2015-10-19 17:28:53 UTC 
Fixed in XWayland.