New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 914637 link

Starred by 2 users
Status: Assigned
Owner:
poromov@chromium.org
Cc:
vaandres@chromium.org
noelad...@gmail.com
bigo@chromium.org
█ jayhlee@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Chromebooks are not launching any kiosk app when selected from login screen

Project Member Reported by bigo@chromium.org, Dec 13 
Chrome version: 69/70
OS version: Chrome OS
Case#:17714090

Description: 
We have a large number of Chromebooks that are not launching any kiosk app the only 2 fixes so far have been to powerwash the device or remove the kiosk app from the admin console and re-push it.
Affected username(s) and device serial numbers:
Chrome OS version (found by navigating to "chrome://version"):
70.0.35.38.110
Exact text of any error messages:
waiting for application window
Steps to reproduce:
Launch any kiosk app (NWEA Map Testing, DRC Insight, etc and they connect to the network but then stop at waiting for application window.


Steps to reproduce: 
1. Setup apps to be pushed to Chromebook kiosk (Not auto-launch)
2. Start the Chromebook and attempt to launch the app from the menu

Current Behavior / Reproduction: 
The app launches, but hangs on "Waiting for application"

Expected Behavior: 
The app should load after selecting it.

Drive link to logs: Attached.
drive-download-20181207T133821Z-001 (1) (1).zip
4.5 MB Download

Comment 1 by noelad...@gmail.com, Dec 13

debug-logs_20181212-115752.tgz
2.4 MB Download
debug-logs_20181212-122746.tgz
2.2 MB Download

Comment 2 by poromov@chromium.org, Dec 13

Labels: Needs-Feedback
Is it that the kiosk apps were successfully auto-launching on the same device with version <M70, but stopped to auto-launch after the devices were updated to M70?

Comment 3 by noelad...@gmail.com, Dec 13 

@2 The apps in this report were not auto launch kiosk apps but the ones you select from the login screen.  The users reported the same experience in 69 & 70.  We were able to do a quick workaround by either power washing the device or pulling the affected apps from the admin console then re deploying them.  Most of the test admins had tested these apps 2 weeks ago to get ready for testing and everything was working fine then.

Comment 4 by poromov@chromium.org, Dec 13 

But was "manual" launch work previously on these devices? Which version did they have?

Comment 5 by noelad...@gmail.com, Dec 13 

@4 Yes these apps have worked in the past and when they tested them 2 weeks ago they were working fine and 70

Comment 6 by benhenry@google.com, Jan 11

Status: Assigned (was: Untriaged)
This issue has an owner, a component and a priority, but is still listed as untriaged or unconfirmed. By definition, this bug is triaged. Changing status to "assigned". Please reach out to me if you disagree with how I've done this.
►

Sign in to add a comment