You are not logged in.
As the title says with FF 150 I have a situation specific to OpenBox in which watching full screen videos
will be interrupted by the system screen blanker. This issue does not exhibit on KDE. I can't speak
for other environments. I can tell you that "xset s off" command on OB does not eliminate the issue
( either at the command line or inserted in autostart ).
I've tested other browsers e.g. -- chromium and falkon as well. Chromium works just fine, but falkon ( i believe
derived from FF ) exhibits the same issue.
I attempted to downgrade FF to v149 but the issue exhibited there as well... although oddly enough,
before the update ( done Saturday 25 ) it worked just fine.
I can't seem to find any recent updates to OB ( but I'm no expert ) ...just the FF update.
Anybody have any ideas where to go next?
Last edited by W54J04S07T (2026-04-29 14:03:39)
Offline
I can tell you that "xset s off" command on OB does not eliminate the issue
Is it rather DPMS than screen blank?
FF 150 seems to have moved a lot of stuff towards xdg-desktop-portal and on openbox you'll at most use xdg-desktop-portal-gtk and also have no org.freedesktop.ScreenSaver interface, see https://bbs.archlinux.org/viewtopic.php … 1#p2296071
Also check about:config and filter for xdg - you might be able to disable this behavior.
Online
I can tell you that "xset s off" command on OB does not eliminate the issue
Also check about:config and filter for xdg - you might be able to disable this behavior.
Which of these:
widget.use-xdg-desktop-portal.file-picker 2
widget.use-xdg-desktop-portal.location 2
widget.use-xdg-desktop-portal.mime-handler 2
widget.use-xdg-desktop-portal.native-messaging 0
widget.use-xdg-desktop-portal.open-uri 2
widget.use-xdg-desktop-portal.settingswould you recommend changing?
I installed xssproxy, and that didn't seem to do it so I assume something here
needs adjusting. Don't know what though.
Last edited by W54J04S07T (2026-04-27 23:53:03)
Offline
It doesn't look like any of these controls this.
You need to start xssproxy in the background (e.g.
xssproxy &in your .xinitrc or in some other spot you can launch commands that are only relevant for the openbox session)
Offline
Also check whether FF causes org.freedesktop.ScreenSaver related errors and
set -dpmswill disable DPMS (+dpms reactivates it)
Online
It doesn't look like any of these controls this.
You need to start xssproxy in the background (e.g.
xssproxy &in your .xinitrc or in some other spot you can launch commands that are only relevant for the openbox session)
On a system with multiple DEs ( KDE, LXDE, OpenBox ) this works!
On a pure OpenBox system on bare metal... does not seem to work... /sigh ![]()
Offline
Please don't paraphrase, https://bbs.archlinux.org/viewtopic.php?id=57855
"does not seem to work" means
* xssproxy doesn't start
* doesn't provide the org.freedesktop.ScreenSaver interface
* portal complains about not supporting the org.freedesktop.ScreenSaver interface
* the org.freedesktop.ScreenSaver interface doesn't functionally prevent the system to blank the screen or enter dpms
?
Edit: xdg-desktop-portal is an optional dependency for FF - do you have that installed on the bare-bones system?
Last edited by seth (2026-04-28 18:39:50)
Online
Also check whether FF causes org.freedesktop.ScreenSaver related errors and
set -dpmswill disable DPMS (+dpms reactivates it)
Is that "set" or "xset" ? I'm getting command syntax errors both ways.
Offline
"xset", sorry.
What error?
Online
Problem solved by actually getting xssproxy running.
Turns out xssproxy in the autostart of this particular system did not actually run...
Running it from a xterm session ( "xssproxy &" ) got things going.
ThankYou.
Offline
Online