this post was submitted on 07 Mar 2024
691 points (98.1% liked)
linuxmemes
21172 readers
805 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack members of the community for any reason.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
- These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudo
in Windows.
- No porn. Even if you watch it on a Linux machine.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
Please report posts and comments that break these rules!
founded 1 year ago
MODERATORS
It's definitely Wayland on Nvidia, I had the same issues, Element had a flickering black screen. Switching the default session from Wayland to X11 fixed all issues.
From my experience it happens with any XWayland window that fails to hit your display refresh rate. Makes programs such as vscode or element almost impossible to use on high Hz screens, as their max fps is locked to 60.
Yep. I decided to try a quick search and it sounds like it's a common issue. Switched back to x11 and I'm stable again.