KDE is an international technology team creating user-friendly free and open source software for desktop and portable computing. KDE’s software runs on GNU/Linux, BSD and other operating systems, including Windows.
If you encounter a bug, proceed to https://bugs.kde.org/, check whether it has been reported.
If it hasn't, report it yourself.
PLEASE THINK CAREFULLY BEFORE POSTING HERE.
Developers do not look for reports on social media, so they will not see it and all it does is clutter up the feed.
cross-posted from: https://sh.itjust.works/post/53430732
When I check my battery, it says "Librewolf is currently blocking sleep and screen locking (Playing audio)". This happens even when there is no audio playing. What's causing this, how do I fix it?
Most likely, some web page is playing an ad, a video or some audio stream, but without sound activated.
That, or a bug where the block was not removed after being put in place for some stream.
There are no ads in Librewolf, Ublock Origin is installed by default.
When I tested this, I only loaded one page that could play videos, so nothing is playing in the background.
The same thing happens on Firefox.
There are no ads in Librewolf, Ublock Origin is installed by default.
Not as simple as that and not 100%. Anyway.
If you go to about:preferences, search for autoplay and go to Autoplay Settings, can you confirm default is Block Audio and Video and no exceptions interfering?
If ensuring that doesn't help, would you be able to share a URL that triggers this behavior?
This is a comment I posted on the other community.
Yes, librewolf is running. I intentionally have it open. But there is no audio playing.
When I kill the process, it does not unblock, even though there is no librewolf process left.
When I reboot the computer and restart librewolf, it does not block.
When I play a video in the browser, it blocks again.
When I close that tab, it is still blocked.
When I close the browser, it is still blocked, even though there is no librewolf process left.
(This is the Flatpak version, if that helps)
Then it's probably a bug that should be reported.