On Fri, 16 Sep 2022 13:22:34 -0700 Marc MERLIN <marc_...@merlins.org> said:
> On Fri, Sep 16, 2022 at 08:14:59PM +0100, Carsten Haitzler wrote: > > this is suspicious. if e had set this, it'd be 1 second. not 60. dpms it > > always set to screenblank time + 10sec (and the suspend +11, off +12). you > > know e set it if this is what it says. e.g.: > > My xsession sets this once at X start. > > I restarted E right now to give it a chance to reset its own > Screen Saver: > prefer blanking: yes allow exposures: yes > timeout: 6 cycle: 0 > DPMS (Energy Star): > Standby: 16 Suspend: 17 Off: 18 > DPMS is Enabled > Monitor is On > > nothing happens after 6 seconds. so e set everything up right. 6 sec will be the lowest you can set in the gui (0.1 min). everything else matches up. 6 + 10, 6 + 11 and 6 + 12. :) > > Any axny x client can set screensaver timeout so beware what other > > apps/tools/services you run. > > Can E reset it later, or I need to restart it like I did? > Shouldn't E reset it when I use the settings to change values and apply? restart e. e will not go around continually resetting it. it will set it and do nothing more until you change the setting (or when e restarts). > > try close your web browser (chrome). :) > > Mmmh, I have 3 chrome processes running. close them. wait and see (only need to wait 6 seconds :)). i know 100% for sure that chrome has a bug. i've spotted it and instrumented it. e can't do anything about it as this is the x screensaver extension that allows any x client to suspend blanking. > > > What else could it be? > > > > web browser. steam too. i wouldnt trust synergy either... try not using > > that. either way - kill off things other than e. chrome has a nasty bug > > involving suspending the screensavers and it will never un-suspend this > > unless you kill off the browser. then it'll work. it is 100% a chrome bug > > the moment you play any media (e.g. youtube or any ad with video, spotify > > too etc.). i've checked and used a hacked up xscreensaver lib to print out > > when something tries to suspend blanking and chrome does this badly/wrong > > (and it talks to the xserver to do this - not e. has nothing to do with e). > > Yes, I understand this. Bummer that so many apps can go and mess with > those settings without going through E that's how x works. :) anyone can do anything. it's a free-for-all. (some exceptions like becoming a window manager). > Once an app does this, is there a way to override it, or have X split a list > of apps that are blocking blanking? x will not tell you which apps are doing it. you have to literally go close apps to narrow it down. :) > so yes, I killed all my chromes, and now it works. > Restarted synergys, and it still works. voila. chrome bug. as i said... i'm sure you know the people to complain to. :) > found this but the python code is too old, couldn't get it to work. > https://www.reddit.com/r/Chromium/comments/8hwibt/any_way_to_prevent_chrome_from_inhibiting/ > see https://github.com/jnerin/dbus-listen-inhibit/issues/2 this is completely different. it's separate to the x screensaver inhibit and crhome does the xscreensaver inhibit regardless of other dbus services. i know. i've instrumented it :) your path is to go complain to the chrome devs to fix their code and properly suspend then UNSUSPEND as many times as they suspend. all of this "blanking doesn't work" of late has entirely been web browsers finding out they can do this and when media plays (eg youtube) they go do this anyway assuming that if any video plays you never want the screen to blank - they don't even offer an option. they don't even account for the tab in which the media plays being visible. it's all be anti-social behaviour from the browsers. even if they fix their bug of inhibiting suspension then never releasing it (until you close them thus their inhibit is released when their x client connection dies), they are still anti-social in just assuming you want your blanking disabled if some viedeo plays. and that video might even just be some unwanted advertisement in a web page... so ... the people to jump up and down at are the browser devs. :) > also > https://bugs.chromium.org/p/chromium/issues/detail?id=931235 > > and > https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1600622 > mentions trying this, but it doesn't work either > sauron:~$ dbus-send --print-reply > --dest=org.gnome.SessionManager /org/gnome/SessionManager > org.gnome.SessionManager.GetInhibitorsmethod Error > org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager > was not provided by any .service fi > > Now, as I write this, I restarted one chrome, display blank stopped working, > killed it and display blank is still not working even after restarting E :( > > Is there anything E can do to help find the apps doing bad things, and > override them if possible? no - as the apps are talking to the xserver directly in regards to this. it's between the apps and the xserver. e also goes and tells the xserver to do things (eg set screensaver timeout and dpms). if you kill off everything but e - restart e and check with xset q - you can check what e set and you can probably confirm that e sets things right and doesn't go messing it up later on. it's always someone/something else doing it... :) > Thanks, > Marc > -- > "A mouse is a device used to point at the xterm you want to type in" - A.S.R. > > Home page: http://marc.merlins.org/ | PGP > 7F55D5F27AAF9D08 > -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- Carsten Haitzler - ras...@rasterman.com _______________________________________________ enlightenment-users mailing list enlightenment-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-users
