Skip to content
Discussion options

You must be logged in to vote

So I looked into this. It appears this is a Hyprland issue with their protocol. If you use hyprsunset directly, this issue also occurs. I've tested with sunsetr using both the Hyprland CTM backend and the hyprsunset backend (manages hyprsunset) and both have this exact issue. This tells me that this is likely happening at the compositor level and its interaction with Chromium since it responds the same way to both CTM managers, ours, and theirs.

I won't be able to fix this, but if you open up an issue on Hyprland directly, they will likely find a fix for this faster than I ever could. Right now what I could recommend is to try your luck with Firefox, Librewolf, or Brave maybe. Please let …

Replies: 4 comments

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Answer selected by Kommynct
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
upstream Requires upstream fix
2 participants