No on-screen keyboard

[Jozer99]

Fresh install of Octopi 0.17 on a Pi 3B with Raspberry Pi official touchscreen. When I install Boot to Browser via the install script, everything seems to go fine. When I use the touchscreen, entering a text box does not bring up the soft-keyboard. I can't modify or enter any text.

[Jozer99]

Found a manual fix; on the Pi screen, go to the menu and TouchUI settings, and toggle the onscreen keyboard to active (inactive by default). On older versions, this was configured automatically for the local browser session.

[Jozer99]

Update: this fix needs to be re-applied on every reboot of the pi. Is there a way to make this auto-configured by the Boot-to-Browser installer, or at least persistent across reboots?

[lciscon]

I've encountered this issue as well. Fresh install. This is a critical issue.

[lciscon]

It looks like the cookie data is not being saved for some reason.

[stale]

This issue has been automatically marked as inactive because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[Jozer99]

This issue has not been addressed, please fix!

[lciscon]

Could it be related to the fact that the CONFIG_DIR line appears to be commented out by default in the touchui.default file?

# Path for the profile - defaults to ram disk to reduce writes
#CONFIG_DIR=/run/touchui-chromium/

[lciscon]

Actually I think it is because the /run directory is set as a tmpfs, so it is stored in RAM rather than the SD. changing the CONFIG_DIR to something that is not set as a tmpfs should fix it. I'm going to test this this afternoon.

[lciscon]

I have confirmed that that is the issue. If you Change the CONFIG_DIR value in chromium.xinit to point to a directory that is not RAM-based it works fine. /tmp and /run are both ram based by default (at least in my Raspberry PI configuration).

For example if you change it to this:

CONFIG_DIR=/home/pi/tmp

Then the TouchUI settings persist between reboots.

[BillyBlaze]

Thanks for reporting, this issue is fixed on the maintenance branch and will be released soon. You might need to restart your Pi after installing the next update.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.