Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No window in focus after switching workspaces #250

Open
dseomn opened this issue Mar 13, 2023 · 13 comments
Open

No window in focus after switching workspaces #250

dseomn opened this issue Mar 13, 2023 · 13 comments
Labels
upstream issue Something that should be fixed in GNOME

Comments

@dseomn
Copy link

dseomn commented Mar 13, 2023

Recently, some of the times when I switch workspaces with a keyboard shortcut, it looks like there's no window in focus. It used to focus whichever window was last focused in the workspace I just switched to, I think. I'm not positive this extension is the issue, but it does seem to only happen when I have this extension enabled.

Versions:
gnome-shell-wsmatrix 7037a9e
gnome-shell 43.3-2 (from Debian)

Settings:

$ dconf dump /org/gnome/shell/extensions/wsmatrix/
[/]
multi-monitor=true
num-columns=4
num-rows=3
popup-timeout=0
show-workspace-names=false
@mzur mzur added the needs info Needs more information to continue label Mar 30, 2023
@mzur
Copy link
Owner

mzur commented Mar 30, 2023

Can anyone provide steps to reproduce this?

@esauvisky
Copy link
Contributor

esauvisky commented Mar 31, 2023

I can confirm this is happening and indeed it only happens when wsmatrix is enabled. This has begun recently, probably after gnome-shell 43.3.

I use pop-shell with window hints and in the video below you can clearly see that after switching workspaces, focus changes properly to the window in the foreground and then quickly switches back to the last focused window.

arec-15.13.35.mp4

Unfortunately I still didn't figure out a way to reproduce, but will do some research given I'm not the only one affected.

@mzur
Copy link
Owner

mzur commented Apr 2, 2023

I couldn't reproduce this so far with GNOME 43.4 in Arch. It seems like you both have popup-timeout=0 or don't display the popup at all. Does anything change if you let the popup show? What happens id you disable the second monitor (if you have one)?

@dseomn
Copy link
Author

dseomn commented Apr 2, 2023

Ooh, good call, that seems relevant. I just changed popup-timeout to 300 for a bit, and didn't see this bug at all. When I switched workspaces, it looked like no window had focus while the popup was still open. But once the popup closed, the right window had focus. I don't have a second monitor.

@mzur
Copy link
Owner

mzur commented Apr 3, 2023

Since I didn't see this in GNOME 43.4 maybe we can wait until this version lands in Debian and you can see if the issue is still there. Maybe the issue is only present in GNOME 43.3.

@nicjohnston
Copy link

Since I didn't see this in GNOME 43.4 maybe we can wait until this version lands in Debian and you can see if the issue is still there. Maybe the issue is only present in GNOME 43.3.

Waiting for 43.4 works for me. I've been affected by this bug as well (43.3), but I'm running such a messed up version of Manjaro that I wouldn't even bother to try and gather debug info.

@esauvisky
Copy link
Contributor

I couldn't reproduce this so far with GNOME 43.4 in Arch. It seems like you both have popup-timeout=0 or don't display the popup at all. Does anything change if you let the popup show? What happens id you disable the second monitor (if you have one)?

Managed to reproduce. I did not use 0 or disabled, but I was using a very small value (because of a different quirk in which you have to wait for the popup to despawn to be able to alt+tab to a different window), and after raising it to 500 was able to figure out how to reproduce. My hunch is that both quirks are related as well.

Will send a video with steps shortly

@esauvisky
Copy link
Contributor

Fixed for me on 43.4. Sorry forgot about the video but the way to reproduce was:

  • Set a very short popup despawn time.
  • Switch from a workspace containing an Electron app to an adjacent one with a GTK3 window.
  • Wait for the modal to despawn.
  • Switch back to the previous workspace with the electron app.
  • You'll notice that the focus is on the GTK3 window still. You can press alt+space to check.

@esauvisky
Copy link
Contributor

@dseomn if you don't mind: do you also happen to use "Switch Windows Directly" as your main Alt+Tab/application switcher?
image

Although 43.4 fixed the root issue, there's another smaller one that I'm trying to fix related to all this and knowing that would be helpful.

By the way what fixed it was mutter not gnome-shell

@mzur mzur added upstream issue Something that should be fixed in GNOME and removed needs info Needs more information to continue labels Apr 19, 2023
@mzur
Copy link
Owner

mzur commented Apr 19, 2023

Thanks for the update. I'll tag this as an upstream issue then. Feel free to discuss the other issue and close when you are ready.

@dseomn
Copy link
Author

dseomn commented Apr 19, 2023

@dseomn if you don't mind: do you also happen to use "Switch Windows Directly" as your main Alt+Tab/application switcher?

I use "switch windows" (not directly). And while looking at that settings page, I realized that apparently the settings I set via dconf aren't even shown fully in the UI. In case those settings are relevant:

$ dconf dump /org/gnome/desktop/wm/keybindings/
[/]
switch-applications=@as []
switch-applications-backward=@as []
switch-windows=['<Super>Tab', '<Alt>Tab']
switch-windows-backward=['<Shift><Super>Tab', '<Shift><Alt>Tab']

@PabloKowalczyk
Copy link

Same issue here: GNOME Shell 44.1 on Ubuntu 23.04 and wsmatrix v8.0.

@ashishnitinpatil
Copy link

Same issue: GNOME shell 44.3 on Ubuntu 23.04 (wsmatrix seems latest / Version: 40 as per gnome-extensions info).

$ dconf dump /org/gnome/shell/extensions/wsmatrix/
[/]
show-popup=true

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
upstream issue Something that should be fixed in GNOME
Projects
None yet
Development

No branches or pull requests

6 participants