-
Notifications
You must be signed in to change notification settings - Fork 7
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
Not working with more than one display #30
Comments
Hi, I cannot reproduce the bug on Gnome-3.38 with the new fixes on #31. What is your setup exactly? |
Same problem here. It only happens when Gnome is set to switch workspaces only on the main display.
but it never gets to Maybe the problem comes somehow from the need to call EDIT: Ok, this is weird, it is working now and cannot reproduce it anymore. Just suspended the computer and now it's working. |
I was looking at this, I can confirm that by switching from The extension doesn't work with As far as I can tell that's because I'm on Ubuntu 20.10, Gnome Version 3.38.3, X11. I don't know where to check the extension version so here's {
"_generated": "Generated by SweetTooth, do not edit",
"description": "This extension aims to make Gnome Shell easier to navigate using only the keyboard. It is inspired by the vim plugins of Firefox and Chrome.",
"name": "Overview Navigation",
"settings-schema": "org.gnome.shell.extensions.overview-navigation",
"shell-version": [
"3.38"
],
"url": "https://github.com/nathanielsimard/overview-navigation",
"uuid": "[email protected]",
"version": 14
} I added a log to check for
Now this doesn't affect me really cause I don't use workspaces, but hope this helps. |
Thanks for this helpful extension. It works well if there's only one display active, but if I'm using both an external display and my laptop display, it no longer works. Hitting space to show/hide the letters works, but typing a letter doesn't do anything, and hitting shift (to close) doesn't do anything. Just wanted to report the bug, in case you weren't aware of it.
The text was updated successfully, but these errors were encountered: