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

Popup does not vanish with mod-key-release anymore #207

Closed
Grinzold opened this issue Feb 2, 2022 · 12 comments
Closed

Popup does not vanish with mod-key-release anymore #207

Grinzold opened this issue Feb 2, 2022 · 12 comments

Comments

@Grinzold
Copy link

Grinzold commented Feb 2, 2022

Hi there,

with 'popup-timeout=0' the popup does not vanish anymore. It just stays indefinitely.

Expected behaviour: it should vanish with the release of the modifier keys.

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 21.10
Release: 21.10
Codename: impish

$ gnome-shell --version
GNOME Shell 40.5

$ grep -r '"version":' .
./metadata.json: "version": 33

Not sure if this translates to version v6.4

@ebeem
Copy link
Collaborator

ebeem commented Feb 2, 2022

It's related to v6.4, issue #200 has the same problem (but with a special case).
In your case shouldn't something is fishy. If the popup doesn't disappear without performing an special action, then you must have a modifier key used by default which doesn't make sense. Can you please let us know if you have any special use case that causes this behavior or a package/configuration you are using that you think it causes it?

@ebeem
Copy link
Collaborator

ebeem commented Feb 2, 2022

Can you please check with an earlier release of wsmatrix? like v6.3 or v6.2.
Let me know if you face the same problem or that fixes it.

@ebeem
Copy link
Collaborator

ebeem commented Feb 3, 2022

Also let me know please if you happen to run this Ubuntu machine in a virtual machine.

@Grinzold
Copy link
Author

Grinzold commented Feb 3, 2022

No virtual machine

It was working perfectly until a few days ago. I am not sure what was updated when. Maybe gnome was also updated...
Is there an 'installation history' for gnome-extensions somewhere? (I use the gnome extension website to manage the extensions.)

I use the modifiers: +

This is in my prefs:

switch-to-workspace-down=['Down']
switch-to-workspace-left=['Left']
switch-to-workspace-right=['Right']
switch-to-workspace-up=['Up']

In the metadata.json there is written version 33. How do you translate this to v6.4 or v6.3...?

Thanks for your help.

@Grinzold
Copy link
Author

Grinzold commented Feb 3, 2022

The problem above, I have with my desktop. I also use a laptop w/ identical versions. No problem there.

Is there any log/debug output to be enabled?

@ebeem
Copy link
Collaborator

ebeem commented Feb 3, 2022

Trying out https://github.com/mzur/gnome-shell-wsmatrix/releases/tag/v6.3 and lettings us know whether it fixes it or not will probably help.

@Grinzold
Copy link
Author

Grinzold commented Feb 4, 2022

Sorry for my ignorance, but how do I do that?

Just unpack everything under .local/share/gnome-shell/extensions?

Any log/debug output to check what is going on?

How do I do a fresh start? E.g. get rid of the 'dconf' entries?

@ebeem
Copy link
Collaborator

ebeem commented Feb 4, 2022

you don't need to do anything with dconf yet, just remove the old extension folder in ~/.local/share/gnome-shell/extensions, the folder's name should be something like [email protected].
Then replace it with the one you download and extract from the release page

@Grinzold
Copy link
Author

Grinzold commented Feb 5, 2022

All have the same behaviour. I went down to version v6.0. With timeout=0 the popup is stuck until I click with the mouse or I hit esc...

Version is always shown as '-1', though. Can't you put there the actual version?

@ebeem
Copy link
Collaborator

ebeem commented Feb 6, 2022

Thanks for your feedback, it seems like you're not the only one facing a similar issue. #200 also mentions the issue and it's probably a GNOME issue.
I will investigate further and keep you updated.
Thanks for your feedback.

@mzur
Copy link
Owner

mzur commented Apr 29, 2022

Maybe related to #219?

@mzur
Copy link
Owner

mzur commented May 1, 2022

This sounds very much like #219. Since the assumed cause is a missing event returned by Clutter, maybe a Clutter update broke this behavior. This can continue in #219.

@mzur mzur closed this as completed May 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants