Kiosk mode not surviving reboot

jcook84

@pjft
I have the same problem. Both the standard menu shutdown and a power button script shutdown have the same result. (Edit: ES-Dev)

edmaul69

@jcook84 if you change the emulationstation theme do you lose that on reboot as well? If so you might need to fix the permissions for the emulationstation folder. I had this issue.

jcook84

@edmaul69
Theme selection is persistent. Still no luck with with having Kiosk setting hold through the reboot. Not a huge deal because it will remain if I edit the es_settings.cfg; Ideally, I'll be the only one in the house using full UI anyway

jcook84

@srdrgz
I typically edit the unwanted Retroarch hotkey combos out of the controller configs in /retroarch-joypads/.

edmaul69

@jcook84 i do this as well. I also add disc eject, disc next and disc prev to the individual controller configs for famicom disc system and psx.

jcook84

@edmaul69
Good idea!

So I edited es_settings.cfg to my liking (kiosk UI, snes-mini theme, ect...) then I used "chattr" to lock it ALL down. I can switch to full UI and do whatever I need to do, but after a restart it reverts back to kiosk.
locking:
sudo chattr +i es_settings.cfg
to unlock it:
sudo chattr -i es_settings.cfg

pjft

@jcook84 can you send over the content of the settings file after trying to change it from full to Kiosk and exiting to the Shell, together with the es_log.txt file? You may use pastebin for the effect, it should help setting what may be happening.

Of course you'd need to revert you're permissions changes :/

Zigurana

I think I've found the root-cause for this. The proposed solution is under review atm.

Jenslyn87

@zigurana Great! I have this problem with a pi I'm building for my friend, and I really would love to see it fixed before I give it to him. Please let me / us know when the fix is available :)

gabrielssanches

@jcook84 said in Kiosk mode not surviving reboot:

@edmaul69
Good idea!

So I edited es_settings.cfg to my liking (kiosk UI, snes-mini theme, ect...) then I used "chattr" to lock it ALL down. I can switch to full UI and do whatever I need to do, but after a restart it reverts back to kiosk.
locking:
sudo chattr +i es_settings.cfg
to unlock it:
sudo chattr -i es_settings.cfg

that did the trick. I'll leave that way until next update.

Thx

Zigurana

This was also fixed in the latest pr, please install the experimental / dev branch (from source) and try again.

Let me know how you fare!

LinuxArcadeGuy

@zigurana said in Kiosk mode not surviving reboot:

This was also fixed in the latest pr, please install the experimental / dev branch (from source) and try again.

Let me know how you fare!

~~sorry not fixed in v2.7.3RP~~

nevermind, had to reboot using ES NOT thru ssh...

LinuxArcadeGuy

@linuxarcadeguy still not stable, has issues, survives... then doesn't survive

Zigurana

@linuxarcadeguy
That makes no sense at all.
You will need to provide more information about your setup and way of working if you want me to be any help.
What HW are you using? How are you rebooting / exiting ES? Under what circumstances does the UI mode stick and when does it not?

pjft

Are you using the actual dev version, it just installed the latest stable from source?

LinuxArcadeGuy

@pjft said in Kiosk mode not surviving reboot:

Are you using the actual dev version, it just installed the latest stable from source?

installed from source

Trailjacker

I am having the same issue. KIOSK mode doesn't survive a reboot.

reeebs

the same here.
it was OK since last week, when I did a manual general update of all installed packages (from source) - since that, it stopped working properly and started to be affected by this thing: it works for the session, but can't survive reboot.
and setting "Kiosk" into the config file works good, but if you once use the konami code and turn it back to full interface, it restarted the loop of not survivng reboot no more.
(osmc + retropie on a raspberry pi 3)

Trailjacker

@zigurana Did the solution ever get reviewed or do you need help testing it with users?

Zigurana

Changes are accepted in a two-step way:

Code gets reviewed and is merged in the master branch. This can be installed by installing via de experimental menu, dev branch or somesuch.
After sufficient exposure, the master branch gets merged into the stable branch, which is what is used for binary generation, and what you pull when installing from source.

The fix has been accepted (passed step 1)
So, try installing the dev branch, and see if your issue is solved.