ungoogled-chromium 102 blocks DPMS suspend (potentially also screensavers) #190
Comments
|
does this happen only under arch? |
|
I do not have any other systems I could test in unfortunately :/ (besides windows and macos, which I wouldnt expect to help in this case?) |
|
have you tested vanilla chromium? |
I was afraid to test it since it might break my profile in some way, but just did and it was fine. Just tested on arch's vanilla How do I proceed from here? Can any of you replicate this issue? |
|
What is your DE? Cannot reproduce on Gentoo under xfce. |
I am using i3 |
|
I also can't reproduce, currently using sway. |
|
Updating this issue with related bug reports for any future readers: |
Since version 102, after playing any video (youtube, twitch were tested), even after closing the tab, DPMS suspend is blocked.
This did not occur before on any of the previous versions, downgrading to
ungoogled-chromium-101.0.4951.64-1makes it behave properly, whereas bothungoogled-chromium-102.0.5005.61-1andungoogled-chromium-102.0.5005.61-2have the issue.(compiled from the AUR package locally, using latest arch vanilla
makepkg.conf, changing onlymarch,mtune,-jflag andBUILDDIRset to tmpfs)To reproduce
Test normal behavior
-- Launch chromium
-- Trigger a screen locker that sets dpms timeout (
sxlocketc..) or just set dpms timeout to something short to test-- Verify that display goes to sleep/suspend as expected
Test incorrect behavior:
-- Launch chromium
-- Open a youtube video tab and play the video.
-- Pause or close the tab completely
-- Trigger dpms timeout suspend as before
-- Verify that display does not enter sleep
using
xset dpms force suspendit will work as it will ignore X client wake events.The text was updated successfully, but these errors were encountered: