BUG: Context Menu Results in Phantom Focus

[LirionTen]

• Sway Version:
  1.11

• Configuration File:
  repro provided, but focus_follows_mouse no if it matters

• Description:

Sway can get into a faulty state, where a window has focus, but keyboard events go to another windows. I've been triggering this by mistake for months now, but only today did I recognize the triggering condition.

Steps to reproduce:

1. open two terminals side by side
2. click left window to give it focus
3. press the mod button to bring up Waybar (hidden by default in my setup),
4. while holding mod button to keep bar visible, right click on tray icon (flameshot in my case) to bring up its context menu.
5. with context menu visible, click on the right window

Result: the title bar of the right window shows it has received focus, but keyboard events still go to the left window. In my terminal, you can also see that the cursor doesn't change from an empty rectangle to a filled one, as it does when the window is ready to receive keyboard inputs.

Demonstration Video:

Probably related to #8912.
Possible dupe of #6967, but hopefully I've provided a reproducer.
Possibly related #6555

[litoj]

I have the same issue, for me it reliably happens when I click any menu in a gtk4 application and then click on any other window. The keyboard inputs still go to the gtk4 window (in my case using transmission-gtk).

From what I was able to test, it is still present on older linux kernel and sway v1.9. So, possibly, it has been always present.

[LirionTen]

@litoj while flameshot in my demo uses QT. hmm.

[lpcvoid]

I can reproduce this 100% of the time on Sway 1.10.1 and wlroots 0.18.2-3 as packaged on Debian.

[LirionTen]

@litoj, @lpcvoid , @Wielding,

Shot in the dark here: are you all using the nouveau driver by any chance?
Nouveau has been throwing errors in dmesg for a while now.

[lpcvoid]

Nope, I am using all-AMD hardware, so amdgpu.

[litoj]

I am also all amd

[Wielding]

AMD on both machines.

[marcinmdev]

I think I have similar issue - mostly when using Firefox (maybe due to frequency of use?). It manifests itself in keyboard having separate focus from mouse. It's pretty peculiar because:

• no particular errors in dmesg nor sway debug log
• it happens even without changing focus - I can click inside Firefox windows, change tabs, type, click and suddenly I cant type anything in input fields (mouse clicking always works)
• It goes away when I focus another window and move focus back into firefox.
• it happens randomly and rarely - maybe 2 or 3 times a day

Using NVIDIA proprietary driver, sadly. Sway 1.11 + wlroots19 in arch.

[LirionTen]

@swaywm @emersion, there's a dozen user confirmations and at least 4 linked issues about focus bugs in sway, one opened in 2022.

I've now provided a repro, which another user confirmed as working.

Can you please take a look at this disruptive long-term problem, or let us know what's blocking a fix all this time?

Thank you.