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

Desktop App Menu Flickers #308

Closed
micadeyeye opened this issue Dec 2, 2020 · 4 comments
Closed

Desktop App Menu Flickers #308

micadeyeye opened this issue Dec 2, 2020 · 4 comments

Comments

@micadeyeye
Copy link

micadeyeye commented Dec 2, 2020

I am having some problems with FVWM. And I was wondering if someone can assist me to solve them. All pop-ups/drop-downs only flicker and by the time I want to choose an option, they are gone. Here are come concrete examples: clicking on the UMAtrix browser extension in order to enable JS via some URLs would rather only result in the User Interface showing for 1.5sec and it is all gone. NOScript extension drop-down too would not stay on so that I can choose. I can confirm that this problem is also seen in Libreoffice. I cannot click on any of the menu options. The "FILE" menutab, for example, shows for 1.5sec or so and it's gone. I can confirm that it is persistent across all pkgs. To make matter worst, I cannot enter password in some textfields. I would have to go type them in a textfile and then copy-paste into the textfield. For these difficult textfields, by the time I type the first three or more characters, all previous ones are gone. I can confirm that this problem is only peculiar to FVWM; all the pkgs, when used in other desktop environments - OpenBox, MATE, GNOME, etc, - are not having the problems.

I would appreciate your assistance.

@issue-label-bot
Copy link

Issue Label Bot is not confident enough to auto-label this issue. See dashboard for more details.

@ThomasAdam
Copy link
Member

ThomasAdam commented Dec 2, 2020

Hey @micadeyeye

Sorry to hear this isn't working for you, Before I dive into this, are you able to confirm if this problem you're experiencing is specific to Fvwm, or have you seen this elsewhere? I know you say it doesn't happen in GNOME, but is there any difference?

Kindly,
Thomas

@danespen
Copy link

danespen commented Dec 2, 2020 via email

@micadeyeye
Copy link
Author

Thanks to you two.
It was indeed the keyboard; a key in it must have been stuck. It is however funky seeing that the problems were not occurring in other desktop environments. FVWM heavily uses the keys unlike other DEs.

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