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

Issue 666524 link

Starred by 1 user
Status: Archived
Owner:
xiy...@chromium.org
Closed: Nov 2017
Cc:
█ kirtika@chromium.org
█ cernekee@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

Chrome OS manifest parsing issue.

Project Member Reported by roy...@google.com, Nov 17 2016 
We are noticing some apps are breaking in 54 which is consistently working in 53. This is a single app kiosk app, and customer is saying that the device doesn't launch the app. Admin console shows the device is offline (but the logs clearly show that the device is connected to the network and fetching time updates). It almost looks like the app failed to launch (Suggested by the logs below) but I can't say it confidently.

[20021:20021:1117/154658:ERROR:component_loader.cc(158)] Failed to parse extension manifest.
[20021:20021:1117/154658:ERROR:component_loader.cc(158)] Failed to parse extension manifest.

Complete log here: https://drive.google.com/corp/drive/folders/0Bx12NVyIouI0dnpseWl5V0QtRGc

Comment 1 by xiy...@chromium.org, Nov 17 2016 

component_loader is for component extensions and should not cause failures on kiosk launch.

The captured log does not have chrome user logs. I could see launches of kiosk apps but could not tell whether there are errors during the launch.

Do we have a repro?

Comment 2 by xiy...@chromium.org, Nov 18 2016

Cc: cernekee@chromium.org
+cernekee

Could you help to check out the net.log (and older ones) to see whether the device is having some wifi problems?

From my naive reading, the device seems not having wifi since 11/13 (net.3.log that how far I went back), e.g.

2016-11-13T18:06:27.709205-05:00 NOTICE wpa_supplicant[414]: wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="<...>" auth_failures=1 duration=10 reason=WRONG_KEY
2016-11-13T18:06:27.709242-05:00 NOTICE wpa_supplicant[414]: wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="<...>" auth_failures=2 duration=20 reason=CONN_FAILED
2016-11-13T18:06:27.711044-05:00 INFO shill[731]: [INFO:wifi.cc(862)] WiFi wlan0 supplicant updated DisconnectReason to 15
2016-11-13T18:06:27.716657-05:00 INFO shill[731]: [INFO:service.cc(411)] Service 0: state Associating -> Failure

Comment 3 by xiy...@chromium.org, Nov 18 2016 

It seems the device also has an ethernet. The bad kiosk run seems to be the one with timestamp 2016/11/16 03:10:23.

The device rebooted around that time. shill thinks the eth0 is ready:
2016-11-16T03:10:33.930052-05:00 INFO dhcpcd[3568]: eth0: sending REQUEST (xid 0xc3da68fe), next in 7.6 seconds
2016-11-16T03:10:33.933578-05:00 INFO dhcpcd[3568]: eth0: received ACK with xid 0xc3da68fe
2016-11-16T03:10:33.933613-05:00 INFO dhcpcd[3568]: eth0: acknowledged 192.168.24.2 from 192.168.24.1
2016-11-16T03:10:33.933626-05:00 INFO dhcpcd[3568]: eth0: leased 192.168.24.2 for 604800 seconds
2016-11-16T03:10:33.933637-05:00 INFO dhcpcd[3568]: event REBOOT on interface eth0
2016-11-16T03:10:33.933648-05:00 INFO dhcpcd[3568]: status changed to Bound

But chrome seems disagree (in ui.20161116-031023):

[518:518:1116/031058:ERROR:device_event_log_impl.cc(140)] [03:10:58.538] Network: network_portal_detector_impl.cc:463 Portal detection timeout:  name=Ethernet id=4654e2c9-eecd-45d7-b763-2f3a79d9c558
... this repeats many times.
[518:518:1117/154411:ERROR:device_event_log_impl.cc(140)] [15:44:11.665] Network: network_state_handler.cc:922 Default network in unexpected state: Ethernet (/service/2)State: idle

Comment 4 by sduraisamy@chromium.org, Nov 18 2016

Cc: kirtika@chromium.org

Comment 5 by mitsuji@chromium.org, Nov 22 2016

Status: Available (was: Untriaged)

Comment 6 by jayhlee@google.com, Nov 8 2017

Status: Archived (was: Available)
Archiving since we've not seen further reports.
►

Sign in to add a comment