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

Issue 655172 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Oct 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Kiosk app freezes on AOpen Chromebox after upgrade to 53.0.2785.129+

Reported by yyefet@chromium.org, Oct 12 2016

Issue description

Version: 53.0.2785.129+
OS: ChromeOS (CFM)

Enterprise CFM customer claims that their customer kiosk app started to freeze after device (AOpen Chromebox Commercial) upgraded to 53.0.2785.129 on Sept. 21st.

While this is a custom kiosk app issue (which is generally unsupported).. there does seem to be odd system/network related errors in the logs.


I found the following log errors repeat hundreds of times over and over:

====================
ERR shill[2154]: [ERROR:object_proxy.cc(582)] Failed to call method: fi.w1.wpa_supplicant1.Interface.Scan: object_path= /fi/w1/wpa_supplicant1/Interfaces/1: org.freedesktop.DBus.Error.LimitsExceeded: The maximum number of pending replies per connection has been reached
ERR shill[2154]: [ERROR:dbus_method_invoker.h(111)] CallMethodAndBlockWithTimeout(...): Domain=dbus, Code=org.freedesktop.DBus.Error.LimitsExceeded, Message=The maximum number of pending replies per connection has been reached
====================
(See full logs from 3 affected devices below)


Note: Customer is convinced issue started after upgrade.


What steps will reproduce the problem?
(1) launch kiosk app on CFM
(2) after a few minutes, app starts to freeze.


What is the expected output?
Kiosk app should run normally

What do you see instead?
Kiosk app freezes


PII protected device logs:
https://drive.google.com/drive/folders/0B6fESMmJITTNSGdnU3NKZHZqdlE?usp=sharing

 
Cc: harpreet@chromium.org mlight@chromium.org
Owner: sduraisamy@chromium.org
Is this still occurring in the latest R54 stable? Please close this if this is not reproducible anymore.

Comment 3 by yyefet@chromium.org, Oct 25 2016

Status: WontFix (was: Untriaged)
Closing bug.  Issue fixed in r55

Sign in to add a comment