Description of problem: As of current Fedora 22, keyboard focus sticks to the first instance of gnome-terminal even when later instances get the focus. Version-Release number of selected component (if applicable): gnome-shell-3.15.92-2.fc22 How reproducible: Always Steps to Reproduce: 1. Login to GNOME Wayland session. 2. Launch first instance of gnome-terminal. 3. Type some characters. 4. Launch second instance of gnome-terminal. 5. Focus second instance of gnome-terminal. 6. Type some characters. Actual results: Input appears in first instance of gnome-terminal. Expected results: Input appears in second instance of gnome-terminal. Additional info: - This only happens in a GNOME Wayland session. - Issue does not depend on the focus mode. - Video chip is an AMD RV620.
Still broken in gnome-shell-3.16.1-1.fc22.
I've just updated to f22 (from f21) and am also seeing this. Graphics card is an AMD radeon 7970 (TAHITI 0x1002:0x6798 0x1002:0x3000), using the FOSS "radeon" driver. I think. Normally I'd check the xorg log ;) gnome-terminal version is 3.16.1-1.fc22 Doesn't happen with an alternative terminal emulator (terminator).
No improvement for the current Fedora 22 branch including gnome-shell-3.16.2-1.fc22.
Can you confirm comment #2 that this only happens with gnome-terminal? In that case I wouldn't discard a terminal issue ...
(In reply to Florian Müllner from comment #4) This issue only appears for gnome-terminal.
Ctrl+Shift+t also does not work in Wayland.
Also happens on an Intel Broadwell integrated graphics chip, 8086:1616. I've only seen it in gnome-terminal. I can't always duplicate it.
Focus issue has been resolved for the current Fedora 23 branched tree but not for Fedora 22.
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 bug. Thank you for reporting this bug and we are sorry it could not be fixed.
Verified fixed in Fedora 24.
Issue was actually resolved by errata issued for Fedora 22 during its support cycle, e.g. in the last live respin F22-x86_64-WORK-20151217.