Page 1 of 1

Screen saver web page issue

Posted: 09 Aug 2022, 14:45
by cch
Since upgrading to Porteus Kiosk 5.4.0, the screensaver web page option is not working properly for me. I have a Google Slides slideshow set to display. On 5.3.0, this worked fine.

I have session restart set for 5 minutes and the screen saver set to 6 minutes. At 5m30s since the kiosk is touched, the session restarts as expected. At 6m, the screen saver loads. Shortly after that, it disappears. No matter how long the kiosk is idle at this point, the screen saver never comes back. If the kiosk is interacted with, the screen saver will start again after 6 minutes of idle time, but will again stop by itself.

As a test, I eliminated the session restart. I also tried a different web site to rule out the Google Slides slideshow as the issue. The same problem happens if I set the screensaver web page to https://www.msn.com.

I don't have automatic updates, so perhaps this is fixed in the kiosk current branch. If not, I wanted to point it out as an issue for the next release.

Screen saver web page issue

Posted: 09 Aug 2022, 14:58
by fanthom
Hello cch,

1) Which browser are you using?

2) Please set the screensaver webpage to some static HTML like:
https://www.kernel.org

and check if you are able to recreate the problem.

Thanks

Screen saver web page issue

Posted: 09 Aug 2022, 15:59
by cch
Hi,

Using Chrome. Also, I made an error in my previous report. The screen saver will start again if the kiosk is untouched. The session idle timer goes off again as well. So after the screen saver disappears, 5 minutes later the session restarts, 1 minute later the screen saver starts, then stops after 30-40 seconds, then repeat.

I set the screen saver web page to kernel.org and have the same issue. Also, the issue is occurring on devices with touch screens, but I tested on one without just to rule out any phantom inputs.

Screen saver web page issue

Posted: 09 Aug 2022, 17:57
by fanthom
Please provide your kiosk config (remove passwords, etc).

Thanks

Screen saver web page issue

Posted: 09 Aug 2022, 18:26
by cch
Sure:

Code: Select all

connection=wired
dhcp=yes
browser=chrome
homepage=https://login.pointclickcare.com/poc/userLogin.xhtml?loginInputType=cardReadIn
session_idle=5
hide_mouse=yes
disable_navigation_bar=yes
kiosk_config=http://cchwsus01.cch.net/kiosklantest.txt
persistence=session
scheduled_action=Monday-1:00 Tuesday-1:00 Wednesday-1:00 Thursday-1:00 Friday-1:00 Saturday-1:00 Sunday-1:00 action:reboot
disable_private_mode=yes
screensaver_idle=6
shutdown_menu=reboot restart-session 
screensaver_webpage=https://www.kernel.org/
wallpaper=http://cchwsus01.cch.net/kiosklogo.png
disable_zoom_controls=yes
additional_components=uefi.zip

Screen saver web page issue

Posted: 10 Aug 2022, 10:54
by fanthom
cch,

I was able to reproduce the issue.

Seems its caused by the Chrome browser which generates as input event approx 50 seconds after first start (probably when checking for updated components like e.g. widevine plugin) and it breaks the idle time.

If you want to reproduce this bug then its enough to set the homepage to some internal Chrome page e.g. 'chrome://version' and run this command over SSH:

Code: Select all

while true, do xprintidle; sleep 1; done
after 40- 50 seconds the idle time will reset.
According to my tests the Firefox browser is not affected by this bug.

Luckily Google removed this troublesome input event in Chrome 104.x so next kiosk release should be good as well.

Thank you for reporting.

Screen saver web page issue

Posted: 10 Aug 2022, 13:02
by cch
Excellent, thanks for letting me know!

Screen saver web page issue

Posted: 10 Aug 2022, 13:03
by fanthom
It could be also that the event is not fixed at all as Chrome 104.x is recent enough to not download any components. After a few months it may try and then the issue may be recreated ...

If this is really the case then 'automatic updates' service (keeping Chrome updated) is the only way to have this function working properly.
Firefox is the other workaround.

Will find out in a few months I guess.

Thanks