Google Chrome locked profile

[Bambi]

We currently have the following issue.

If the Kiosk is unexpectedly rebooted ( power failure), we get the message Profile appears to be in use by another Google Chrome Process
In order to continue we need to manually click Unllock profile and Relaunch.

We are using a persistent storage, because we need to save some items in the localstorage of the browser.

Anyone have an idea on how to resolve this issue?

[fanthom]

Hello Bambi,

Chrome checks the hostname and creates a lock file.
If hostname changes then it "thinks" the profile is used on another PC and prevents browser startup.


Please either:

a) manually set 'hostname=' for each your kiosk so it never changes (recommended solution)

b) remove lock file on each kiosk using SSH (PK Server has an option to execute a command on the client side):
rm /home/guest/.config/google-chrome/SingletonLock

c) add this parameter to your remote config so this file is removed during each kiosk boot:
run_command=rm /home/guest/.config/google-chrome/SingletonLock

Thanks

[Dimitri]

Will this be addressed in a future release? Even better, could hardware specific items like host name, wifi and sound output be set during install and not be overwritten by remote config?

[fanthom]

Dimitri,

"Will this be addressed in a future release?"
Yes

"Even better, could hardware specific items like host name, wifi and sound output be set during install and not be overwritten by remote config?"
This would be dangerous as wifi password may be changed at some stage. Manual kiosk reinstallation would be needed in this case.
We dont want it.

Thanks