New issue
Advanced search Search tips

Issue 805895 link

Starred by 4 users

Issue metadata

Status: Archived
Owner: ----
Closed: Dec 13
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug-Regression


Show other hotlists

Hotlists containing this issue:
Hotlist-1


Sign in to add a comment

WiFi works ok on Chromebit in desktop mode, but doesn't work while in kiosk mode

Reported by n...@novisign.com, Jan 25 2018

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:57.0) Gecko/20100101 Firefox/57.0
Platform: 63.0.3239.140 (Official Build) (32 - bit)

Example URL:

Steps to reproduce the problem:
1. Take a working Chromebit, in kiosk mode (provisioned or non-managed) from its network to another network.
2. In the other new WiFi network, access the Chromebit desktop mode (by pressing Ctrl+Alt+S and then logging in).
3. Set the WiFi network to the new network and make sure the internet works.
4. Now, turn off the device and then turn it on (the only way: plugging it off and then on).
5. Let it enter into the kiosk mode.
6. Whatever app you have as the kiosk app, the internet won't work.

What is the expected behavior?
The expected behavior should be that the internet will work in the kiosk mode (no matter what type of kiosk mode), as it works in the desktop mode.

What went wrong?
From some reason, it seems that in kiosk mode, the kiosk mode doesn't know to take a new chosen WiFi network. Maybe power-washing Chromebit will do the trick, but that is an extreme act.

Did this work before? Yes ChromeOS 62

Chrome version: 63.0.3239.140  Channel: stable
OS Version: 63.0.3239.140
Flash Version: 

This already happened to us in 2 different Chromebits, but only in Chromebits (as all the other ChromeOS devices are wired to the network and do not use WiFi). It never happened in ChromeOS 62, only in ChromeOS 63.
 

Comment 1 by mmenke@chromium.org, Jan 25 2018

Components: -Internals>Network OS>Systems>Network UI>Shell>Kiosk
Hello!
This bug is receiving this notice because there has been no acknowledgment of its existence in quite a bit of time
- If you are currently working on this bug, please provide an update.
- If you are currently affected by this bug, please update with your current symptoms and relevant logs.

If there has been no updates provided by EOD Wednesday, 12/12/18 (5pm EST), this bug will be archived and can be re-opened at any time deemed necessary.

Thank you!
Hello!
This bug is receiving this notice because there has been no acknowledgment of its existence in quite a bit of time.
- If you are currently working on this bug, please provide an update.
- If you are currently affected by this bug, please update with your current symptoms and relevant logs.

If there has been no updates provided by EOD Wednesday, 12/12/18 (5pm EST), this bug will be archived and can be re-opened at any time deemed necessary.

Thank you!
Status: Archived (was: Unconfirmed)
Due to lack of action this bug has been Archived. If work is still being done on this issue or you are still experiencing this issue please feel free to re-open with the appropriate information.

Sign in to add a comment