Hi guys, any updates on this bug?

Do you have more observations? There is clean reasons in the logs of the original report to indicate that the device has crashed. 

e.g.
For 20160407-102619 run, device boots up and launches an kiosk app. It runs until 

2016-04-07T10:29:25.407899-07:00 INFO session_manager[420]: [INFO:browser_job.cc(119)] Terminating process: 
2016-04-07T10:29:25.407935-07:00 INFO session_manager[420]: [INFO:system_utils_impl.cc(49)] Sending 15 to 444 as 1000

which looks like a shutdown sequence started. It could be from power button or test script. But does not look like a crash.

We are not running this platform anymore. Closing.

My mistake. We'll set up Tricky running Hypersign, and update the bug shortly.

Tricky device is unable to run kiosk app hypersign after password is entered, app hangs idle with a blank screen. 
Device info: CHROMEOS_RELEASE_DESCRIPTION=8172.28.0 dev-channel tricky test

please see logs

Deleted: log-051616-171634.tar.gz 629 KB

log-051616-171634.tar.gz 629 KB Download

Did not see crash in the logs. The device just shuts down, probably because that the hypersign app exits. Are we sure we get a proper setup (i.e. license key, display id, password etc) ?

The tricky device is running and Hypersign is also running but is only  displaying the graphic background, and the while line at the bottom is where the captioning runs. 

Deleted: 20160517_154135.jpg 1004 KB

	20160517_154135.jpg 1004 KB View Download

Thanks for the screenshot. This looks more like a bug in the app or a setup problem.