Earlier I noticed on a newly installed Debian (stable) system running Gnome (X11) that the screen was not blanking at all and thus the screen was not locking, neither was… (மேலும் படிக்க)
Earlier I noticed on a newly installed Debian (stable) system running Gnome (X11) that the screen was not blanking at all and thus the screen was not locking, neither was the system suspending. After a while I found the command `gnome-session-inhibit --list` (and later the helpful Inhibition Indicator gnome extension ) which returned `firefox: video-playing (idle)`, indicating firefox was inhibiting the idle action (which is to blank the screen) due to playing a video.
Strange since there was no video playing. Mind you i do have several Firefox windows open in multiple workspaces comprising over 100 tabs on a good day. However, most of these tabs had gone to sleep or were forced to sleep by me with the Auto Tab Discard add-on. I didn't notice anything obvious in about:performance. ChatGPT said to try running `Array.from(document.querySelectorAll('video'))` in the console which returned an empty array. I thought that command checked every tab but it only applied to the tab I started the dev tools from. Maybe if there was a way to add a for loop to check all active tabs, it could be a useful command.
Since it was getting to the point I'd have to restart Firefox to fix this, I tried some more drastic measures first, like putting every tab to sleep with Auto Tab Discard. Now about:processes only listed core Firefox processes like: itself, Fork Server, Network, Utility, Extensions, 3x About Pages, and 3x Preallocated. Even then firefox was still inhibiting the idle action! I think close all of the internals I just listed, so only "Firefox" was listed in about:performance, and still firefox was inhibiting the idle action!
Finally I closed Firefox and finally `gnome-session-inhibit --list` didn't list firefox anymore and screen started blanking again. So I guess that was a bug? How to troubleshoot that better and track down the cause? or should I just go ahead and post this already as a Firefox bug?
Thanks