Questo sito potrebbe offrire funzionalità limitate durante le operazioni di manutenzione per migliorare l'esperienza utente. Se un articolo non risolve il tuo problema e vuoi richiedere supporto, la nostra comunità di supporto è pronta ad aiutarti tramite @FirefoxSupport su Twitter e /r/firefox su Reddit.

Cerca nel supporto

Attenzione alle mail truffa. Mozilla non chiederà mai di chiamare o mandare messaggi a un numero di telefono o di inviare dati personali. Segnalare qualsiasi attività sospetta utilizzando l'opzione “Segnala abuso”.

Ulteriori informazioni

Firefox setting lots of ScreenSaver inhibit lock, never clearing them

  • 1 risposta
  • 0 hanno questo problema
  • 2 visualizzazioni
  • Ultima risposta di TyDraniu

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.

Tutte le risposte (1)

more options

It may be a bug. Can you report it on https://bugzilla.mozilla.org and share here a bug number? Thanks!

È stato utile?

Richiedi supporto

Bisogna accedere al proprio account per rispondere nelle discussioni. Se non si possiede ancora un account, inserire una nuova richiesta.