The blanking Block in the menu Raster added is a useful feature. I have noticed some apps (vlc for example) use a slightly different dbus call than the one implemented in the code.
dbus-monitor output playing a video on VLC: method call time=1659900465.195458 sender=:1.264 -> destination=org.freedesktop.ScreenSaver serial=6 path=/ScreenSaver; interface=org.freedesktop.ScreenSaver; member=Inhibit string "vlc" string "Playing some media." Notice path =/ScreenSaver and not /org/freedesktop/ScreenSaver. VLC relevant code: https://code.videolan.org/videolan/vlc/-/blob/master/modules/misc/inhibit/dbus.c#L60 I also note that as far as I can tell Gnome checks for both dbus paths: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/blob/master/plugins/screensaver-proxy/gsd-screensaver-proxy-manager.c#L125 (NOTE: I do not use gnome nor do I make it a habit of reading that code base, just stumbled across that as it is linked to in the freedesktop specs for org.freedesktop.ScreenSaver) Perhaps e should also check for both dbus messages so that VLC shows up in the blanking menu list when it is active. Whether it is right or wrong for VLC and other problematic apps to use path=/ScreenSaver in this dbus call. Seems a little odd to me but VLC is a very common and widely used application. On Fri, Jun 10, 2022 at 4:23 AM Carsten Haitzler <[email protected]> wrote: > On Fri, 10 Jun 2022 08:45:44 +0200 [email protected] said: > > > On 6/9/22 23:53, Carsten Haitzler wrote: > > > On Thu, 9 Jun 2022 22:41:08 +0200 [email protected] said: > > > > > >> On 6/9/22 12:16, Carsten Haitzler wrote: > > >>> On Thu, 9 Jun 2022 10:41:25 +0200 [email protected] said: > > >>> > > >>>> On 6/9/22 09:55, Carsten Haitzler wrote: > > >>>>> On Wed, 8 Jun 2022 19:50:27 +0200 [email protected] said: > > >>>>> > > >>>>>> On 6/8/22 19:17, Carsten Haitzler wrote: > > >>>>>>> On Wed, 8 Jun 2022 15:39:17 +0200 [email protected] said: > > >>>>>>> > > >>>>>>> actually wait - is this a laptop? or using ddc? dimming timeout > set? > > >>>>>>> then the 30 sec may be the dimming timeout. e will run a timer > after > > >>>>>>> that that then totally blanks the screen. this timer is > cancelled when > > >>>>>>> the screensaver is cancelled (when the screen dims the screen is > > >>>>>>> basically in screensaver mode) > > >>>>>> It's just a laptop > > >>>>> > > >>>>> ok - that explains the 30 sec then - that's the dimming timeout. > does > > >>>>> the screen dim automatically after 30 sec of idle input? > > >>>> No, screen doesn't dim after 30 sec of idle input. > > >>>> Screen blanks after 2 minutes (according to settings), but > sometimes, > > >>>> maybe once a day, it doesn't blank at all. If i restart e, it blanks > > >>>> normally. > > >>> > > >>> that's odd. screen should dim. you have backlight support? does it > work > > >>> manually with the gadget? > > >> > > >> Yes that's odd...I have backlight support and gadget in shelf. See > > >> settings in attached file > > > > > > so backlight controls work? you can manually change brightness? does > the > > > backlight dim after 30 sec of no input if you leave things idle? btw > your > > > normal backlight is 5% .. that's really odd.... it should be HIGHER > than the > > > dim level of 30%... > > > > I set backlight higher than dim level, and dim works now. > > Maybe this explains why, sometimes, blanking doesn't work, but it > > happens randomly... > > well now you at least have saner backlight settings (these are not > defaults - > the defaults are 100% and 30% for normal and dim levels). the first thing > you > should look for is if the screen dims after 30 sec od idle - if it does > then > screensaver is then activating. e uses the x screensaver notify event > fromto > dim the backlight (and screensaver deactivate to un-dim (go back to > bright)). > once idle e runs a timer that then waits for "the rest of the time" until > the > screen needs to go blank. so if dim timeout is 30 sec, and blanking time > is 2 > min, then e runs a timer for 1.5min. when this timer is hit then e will > "fade > to blank" and fade out the rest of the backlight to off too. x's dpms > timeouts > are set to expire a little bit after this "fade to black" (about 10 seconds > after as you can see in xset's dpms settings) so the screen will completely > power off then (but will appear black by this point). > > so the first thing to do is to notice... is the dimming happening? if it > is not > then there is a problem earlier on with screensaver notify events not > happening. that means either the x screensaver has been suspended in some > way > (it was totally turned off - some apps go mess with screensaver settings - > xset > q will tell you if screensaver is on or off and the timeout) and some apps > may > take a screensaver "block" from x and ask it to temporarily suspend the > screensaver. chromium and chrome based browsers will do this when playing > videos - sometimes ads on a web page can cause this if they play videos. > youtube does it... the best way to eliminate this is to close your browser > and > see if the problem continues. steam will also kill off blanking even if it > just > runs as a service in the background and no game is running. this s an > ongoing > issue with sdl/steam actively trying to keep the screen alive. in git i > just > added support for a dbus service used by some other wm's and de's that > does the > same as the x screensaver suspend/block feature - but it's asking whoever > runs > the dbus service to suspend blanking/screensaver - in this case e will > advertise this service and it gets the requests. now e knows who asked to > block > the screensaver and will list who asked in a submenu of the main e menu > under > "blanking block". some apps will prefer to use this dbus service instead > of the > x screensaver suspend extension feature, thus it may help identify the > problem > too. you can remove that blank clock by just selecting it in the menu and e > will remove that blocker. like here: > > http://www.enlightenment.org/ss/e-62a2fefb1df8c2.44000455.png > > it's very basic but enough to debug it. i'll make it prettier in future > with > eventually a proper dialog or some gadget with popups or some shelf > indicators > etc. > > > >>>>>>>> On 6/7/22 22:24, Carsten Haitzler wrote: > > >>>>>>>>> On Tue, 7 Jun 2022 17:56:57 +0200 [email protected] said: > > >>>>>>>>> > > >>>>>>>>>> Hi > > >>>>>>>>>> I don't understand why, sometimes, screen blanking doesn't > work on > > >>>>>>>>>> enlightenment. > > >>>>>>>>>> Most of time, it works but sometimes not. Before I thought > this > > >>>>>>>>>> issue comes from intel driver (modesetting i915) but now, i'm > sure > > >>>>>>>>>> this not the case because i get same issue when i launch > > >>>>>>>>>> enlightenment using nvidia driver (optimus technology) > > >>>>>>>>>> Conditions: enlightenment-git efl-git > > >>>>>>>>>> Settings: > > >>>>>>>>>> screen blanking 2.2 minutes > > >>>>>>>>>> DPMS > > >>>>>>>>> > > >>>>>>>>> what are you running at the time? browser? does it have > youtube open > > >>>>>>>>> with a video? steam? something else. various apps will suspend > > >>>>>>>>> blanking themselves... check blanking/dpms settings: xset q > > >>>>>>>>> > > >>>>>>>> I run only Firefox and Thunderbird. No video inside Firefox, > only > > >>>>>>>> blank page See e settings attached files > > >>>>>>>> I start e with startx with only that in my x.session > > >>>>>>>> redshift -P -O 4000 > > >>>>>>>> numlockx on > > >>>>>>>> optirun enlightenment_start > > >>>>>>>> > > >>>>>>>> Strange: xset q shows 'timeout 30' but e setting is 2 minutes > > >>>>>>>> > > >>>>>>>> xsetq > > >>>>>>>> > > >>>>>>>> Keyboard Control: > > >>>>>>>> auto repeat: on key click percent: 0 LED mask: > > >>>>>>>> 00000002 XKB indicators: > > >>>>>>>> 00: Caps Lock: off 01: Num Lock: on 02: > Scroll > > >>>>>>>> Lock: off 03: Compose: off 04: Kana: off 05: > > >>>>>>>> Sleep: off 06: Suspend: off 07: Mute: off > 08: > > >>>>>>>> Misc: off 09: Mail: off 10: Charging: off 11: > Shift > > >>>>>>>> Lock: off 12: Group 2: off 13: Mouse Keys: off > > >>>>>>>> auto repeat delay: 660 repeat rate: 25 > > >>>>>>>> auto repeating keys: 00ffffffdffffbbf > > >>>>>>>> fadfffefffedffff > > >>>>>>>> 9fffffffffffffff > > >>>>>>>> fff7ffffffffffff > > >>>>>>>> bell percent: 50 bell pitch: 400 bell > duration: 100 > > >>>>>>>> Pointer Control: > > >>>>>>>> acceleration: 20/10 threshold: 4 > > >>>>>>>> Screen Saver: > > >>>>>>>> prefer blanking: yes allow exposures: yes > > >>>>>>>> timeout: 30 cycle: 0 > > >>>>>>>> Colors: > > >>>>>>>> default colormap: 0x20 BlackPixel: 0x0 > WhitePixel: > > >>>>>>>> 0xffffff Font Path: > > >>>>>>>> > > >>>>>>>> > /usr/share/fonts/misc,/usr/share/fonts/TTF,/usr/share/fonts/100dpi,/usr/share/fonts/75dpi,built-ins > > >>>>>>>> DPMS (Energy Star): > > >>>>>>>> Standby: 130 Suspend: 131 Off: 132 > > >>>>>>>> DPMS is Enabled > > >>>>>>>> Monitor is On > > >>>>>>>> > > >>>>>>>> > > >>>>>>>> -- > > >>>>>>>> Maderios > > >>>>>>> > > >>>>>>> > > >>>>>> > > >>>>>> > > >>>>>> -- > > >>>>>> Maderios > > >>>>>> > > >>>>> > > >>>>> > > >>>> > > >>>> > > >>>> -- > > >>>> Maderios > > >>>> > > >>> > > >>> > > >> > > >> > > >> -- > > >> Maderios > > > > > > > > > > > > -- > > Maderios > > > > > -- > ------------- Codito, ergo sum - "I code, therefore I am" -------------- > Carsten Haitzler - [email protected] > > > > _______________________________________________ > enlightenment-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
