org.chromium.chrome fails to open blimp client token when running on M w/ SELinux enabled |
|||
Issue description
running w/ client_engine_integration.py + SELinux enabled (i.e., adb shell setenforce 1), the client can't open /data/data/org.chromium.chrome/blimp_client_token. This happens both w/ incremental and non-incremental builds of the client.
relevant part of the logcat:
09-16 16:55:34.840 10661 10661 W Chrome_FileThre: type=1400 audit(0.0:245): avc: denied { open } for path="/data/data/org.chromium.chrome/blimp_client_token" dev="dm-2" ino=5038241 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:object_r:app_data_file:s0 tclass=file permissive=0
09-16 16:55:34.841 10611 10611 V chromium: [VERBOSE1:blimp_client_context_impl.cc(151)] Trying to get assignment.
09-16 16:55:34.842 10611 10661 E chromium: [ERROR:get_client_auth_token.cc(18)] Could not read client auth token file at /data/data/org.chromium.chrome/blimp_client_token
09-16 16:55:34.847 10611 10611 D cr_tabmodel: [TabPersistentStore.java:1180] Loaded tab lists; counts: 0,0
09-16 16:55:34.887 10611 10661 F chromium: [FATAL:assignment_source.cc(115)] Check failed: !assignment.client_auth_token.empty(). No client auth token provided.
,
Sep 26 2016
I tried with Nexus 5x version M, and ran the following steps: - run 'adb shell setenforce 1' - Reboot device - run 'out-linux/Debug/bin/client_engine_integration run', which opens the client file '/data/data/org.chromium.chrome/blimp_client_token' And the log shows blimp started successfully, without warnings as 'Could not read client auth token file' Tommy, could you comment about how to reproduce the issue?
,
Sep 26 2016
I have not seen this issue this week. I have done nothing to my device. No idea what has changed :-/
,
Jun 14 2017
|
|||
►
Sign in to add a comment |
|||
Comment 1 by jbudorick@chromium.org
, Sep 22 2016Status: Assigned (was: Available)