This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Firefox setting lots of ScreenSaver inhibit lock, never clearing them

  • No replies
  • 0 have this problem
more options

When playing videos in various websites (Jellyfin, Mastodon, Youtube) hypridle is receiving many 'ScreenSaver inhibit' messages that are never cleared.

A similar topic pointed to dom.screenwakelock.enabled being the culprit and disabling that fixed that users issue. But I've done that and the problem persists (It did remove one extra lock, but that was the one that was getting cleared.

Chromium sets and clears 1 lock correctly.

System: NixOS unstable DE: Hyprland

I'm using `exec-once = hypridle >> ~/log.txxt` to monitor the logs.

This behaviour is new in the last few months.

It is only present on one of my two systems that is very similar, they both use the same nixos config. The one with the issue is a i5-4590S based system with no external GPU, the one that doesn't have the issue is a Ryzen 7 5800X3D with RX5500. But that may be a red herring, I don't always update the both at the same time, so they may have different software versions.

When playing videos in various websites (Jellyfin, Mastodon, Youtube) hypridle is receiving many 'ScreenSaver inhibit' messages that are never cleared. A similar topic pointed to dom.screenwakelock.enabled being the culprit and disabling that fixed that users issue. But I've done that and the problem persists (It did remove one extra lock, but that was the one that was getting cleared. Chromium sets and clears 1 lock correctly. System: NixOS unstable DE: Hyprland I'm using `exec-once = hypridle >> ~/log.txxt` to monitor the logs. This behaviour is new in the last few months. It is only present on one of my two systems that is very similar, they both use the same nixos config. The one with the issue is a i5-4590S based system with no external GPU, the one that doesn't have the issue is a Ryzen 7 5800X3D with RX5500. But that may be a red herring, I don't always update the both at the same time, so they may have different software versions.

You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.