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

Issue 662835 link

Starred by 2 users
Status: WontFix
Owner:
█ oka@chromium.org
Last visit > 30 days ago
Closed: Nov 2016
Cc:
llozano@chromium.org
derat@chromium.org
weifangsun@chromium.org
fukino@chromium.org
█ katierh@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

Files App doesn't open on the first boot of Kevin.

Project Member Reported by oka@chromium.org, Nov 7 2016 
https://feedback.corp.google.com/product/208/neutron?lView=rd&lReport=15173974905

Chrome: 55.0.2883.34 beta
Chrome OS: 8872.34.0
Device: kevin-signed-mpkeys

What steps will reproduce the problem?
(1) Install Kevin on the device.
(2) Login.
(3) Launch Files App and observe.

What is the expected output?
Files App should open.

What do you see instead?
Files App have empty dialog.

Comment 1 by oka@chromium.org, Nov 7 2016 

I found suspicious errors in the system_logs.txt
(1). a lot of
getrlimit(RLIMIT_NOFILE) failed

(2).
[1654:1654:1103/183532:ERROR:message_service.cc(469)] Failed to create native process.
[1654:1844:1103/183532:ERROR:service_manager.cc(306)] Error: invalid Name: CD7CEA3D1B358FB07361B2988355DD8F
[1,4139704320:00:35:32.794141] Native Client module will be loaded at base address 0x0000000000000000
[1654:1844:1103/183533:ERROR:service_manager.cc(306)] Error: invalid Name: 4354E8E66622D574A763F967566C7A64
[1,4139704320:00:35:33.071504] Native Client module will be loaded at base address 0x0000000000000000

(3).
[1654:1654:1103/183514:ERROR:component_loader.cc(154)] Failed to parse extension manifest.

There are bugs for
(1): https://bugs.chromium.org/p/chromium/issues/detail?id=662450
(2) and (3): https://bugs.chromium.org/p/chromium/issues/detail?id=662517

Comment 2 by oka@chromium.org, Nov 7 2016

Cc: derat@chromium.org katierh@chromium.org

Comment 3 by djkurtz@chromium.org, Nov 10 2016

Cc: llozano@chromium.org
Components: Platform>NaCl Infra>Client>NaCl
The "Failed to create native process" message seems the most serious.
You'll want to debug further to find out why that is failing.

Comment 4 by oka@chromium.org, Nov 10 2016 

Thank you. I will investigate the log further tomorrow.

Comment 5 by oka@chromium.org, Nov 18 2016 

Chrome: 55.0.2883.42 beta
Chrome OS: 8872.44.0
Device: kevin-signed-mpkeys

I confirmed Files App launched at least for USB boot.

Comment 6 by oka@chromium.org, Nov 18 2016

Status: Fixed (was: Started)
I couldn't reproduce the issue the following version.

Chrome: 55.0.2883.42 beta
Chrome OS: 8872.44.0
Device: kevin-signed-mpkeys

Comment 7 by satorux@chromium.org, Dec 6 2016

Status: WontFix (was: Fixed)
Fixed -> WontFix per comment 6.

Comment 8 by fukino@chromium.org, Dec 7 2016 

I tested 8872.34.0 on kevin, but still not reproducible.

Regarding the suspicious log in comment #1,
I see these:
  getrlimit(RLIMIT_NOFILE) failed
  Failed to parse extension manifest.
But I don't see this:
  Failed to create native process.4r5
►

Sign in to add a comment