Porteus

This error has resurfaced in 5.2. I still have the following in my config from when it was an issue in a previous version.

run_command=grep -q 'update-interval' $chflags || echo '--check-for-update-interval=999999999' >> $chflags; rm /home/guest/.config/google-chrome/SingletonLock

Hi Dimitri,

1) Please remind me how to reproduce this problem.

2) Please also provide your kiosk config (remove passwords and other sensitive data from it).

Thank you.

I don't know how to reproduce it. We took an old windows machine and overwrote the ssd with porteus. Loaded config then shipped client to customer. All was fine until restart browser command was sent from server.

Here's everything except passwords and server info. Would anything on the server end cause it, like the overlapping client IDs?

allow_icmp_protocol=yes
homepage=--app=http://edit.mysmartcommunity.net
disable_private_mode=yes
disable_navigation_bar=yes
persistence=full
scheduled_action=Monday-04:00 Tuesday-04:00 Wednesday-04:00 Thursday-04:00 Friday-04:00 action:killall gui-app chrome; sleep 3; sync; reboot
disable_input_devices=yes
hide_mouse=yes
default_sound_card=0.3
shutdown_menu=no
kernel_parameters=acpi=force reboot=warm,cold,bios,smp,triple,kbd,acpi,efi,pci,force
timezone=America/New_York
run_command=grep -q 'update-interval' $chflags || echo '--check-for-update-interval=999999999' >> $chflags; rm /home/guest/.config/google-chrome/SingletonLock
additional_components=uefi.zip 08-ssh.xzm 09-x11vnc.xzm
gpu_driver=modesetting

Dimitri,

If the error is not reproducible then i won't be able to fix it I'm afraid.

As a workaround please wipe persistent data with:
persistence=wipe

reboot the kiosk and then go back to:
persistence=full

Thanks

I think this was because of a repurposed client. It was originally deployed with version 4.9 then 5.2 installed over that. Issue has not returned after unlocking priofile.

Great

Update - We've deployed 2 clients with 5.3 and both are giving us the locked profile error. We did the bite by bite formatting and it still gave the locked profile error. I downgraded one client to 5.2 and the error went away. The other client is on its way back from the customer so I should have it back in a couple of days.

The locked profile warning is a little different than previous. When browser loads we see the google homepage instead of the config's homepage. I send a restart browser command from the server, the browser window closes and I see the locked profile warning sitting behind it.

Any suggestions?

Hi Dimitri,

Will you be able to provide SSH and VNC access to this kiosk so I could debug the problem?

If yes then please contact with support@porteus-kiosk.org.


Thanks

Once the unit arrives I'll set it up and provide access. Thanks