Issue metadata
Sign in to add a comment
|
Kiosk app doesn't start up when running Chrome OS on a Linux machine |
||||||||||||||||||||
Issue descriptionVersion: Since rev 363038 OS: Ubuntu 14.04 Kiosk app doesn't start up on ChromeOS builds when running on a Linux machine. What steps will reproduce the problem? (1) Build Chromium with target_os="chromeos" attribute (2) Start the built chrome on a Linux machine with "--user-data-dir=<dir> --login-manager --login-profile=user" parameters (3) Enroll the device (4) Set kiosk app via the Management Console (5) Reboot twice What is the expected output? Kiosk app starts. What do you see instead? The screen shows the name of the kiosk app and "Waiting for network connection", but the app doesn't start. This seems to be the CL which caused the regression (reverting it solves the problem): https://codereview.chromium.org/1488393002
,
May 3 2016
Which platform and build number is this? The cl mentioned in original bug has been checked in more than 5 month ago, since then we tested kiosk for the secondary apps feature. I doubt it could break the kiosk without anyone else report earlier.
,
May 3 2016
When running on a real ChromeOS device, everything is OK. The problem occurs when I want to run a simple ChromeOS chrome build on a Linux machine (using these instructions: https://chromium.googlesource.com/chromium/src/+/master/docs/chromeos_build_instructions.md), without installing it to a real device.
,
Sep 1 2016
I've had this issue on a ChromeBit. It has happened on a ethernet connection and wifi.
,
Sep 7 2016
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by tnagel@chromium.org
, May 3 2016