Re: [E-devel] enlightenment blanking issue

On 6/20/22 16:23, Carsten Haitzler wrote:
> On Mon, 20 Jun 2022 15:46:15 +0200 [email protected] said:
>
>> On 6/10/22 10:22, Carsten Haitzler 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
>>
>> I use last e and efl git master versions but this function is not
>> available for me
>
> that menu only appears if some application has used the screensaver suspend
> dbus api that i added recently to e. if no one used the api then that menu
> will not be there. i do see chromium uses it if it is there. if it's not there
> 9the dbus api) then browsers seem to use the x screensaver extension to suspend
> blanking.
>
Enlightenment blanking issue appears after watching Twitter video inside
Firefox, even after closing Twitter window.
But not for all Twitter videos: sometimes blanking works normally,
sometimes not...

--
Maderios