ChromeOS issue: Japanese input becoming disabled suddenly/randomly on Chromebook. |
|||||||
Issue descriptionChromeOS version: originally reported by 60.0.3112.114. Now upgraded to 62.0.3202.82. ChromeOS device model: Dell Chromebook 11 Google Chrome Version 62.0.3202.82 Platform Version 9901.66.0 (Official Build) stable-channel wolf Firmware Version Google_Wolf.4389.24.62 Case#: 13844801 Description: issue with Japanese input becoming disabled suddenly/randomly on Chromebook. - Issue occurs about once a week. - Issue does not occur after wiping the device. Steps to reproduce: 1. Open Chromebook 2. Type in Japanese in any field 3. Issue happens suddenly/randomly 4. Check Google Chrome settings > Advanced > Languages and input > Input method > Manage input methods 5. Japanese is removed from the input methods section Current Behavior / Reproduction: Japanese input becomes disabled suddenly. Expected Behavior: Be able to input in selected languages without the setting disappearing suddenly. Additional information. -I am not 100% sure but I found a similar crbug case (crbug.com/761714). -It supposed to be fixed via M 62.0.3202.56, However, the issue is persist even upgraded to 62.0.3202.82. - Issue has been fixed once customer has deleted all affected user profiles from all affected devices. To fix.. - Wipe the device Drive link to logs: https://drive.google.com/open?id=1xpsZmH4gxAsBdAhxy5A9KZNjqACuj9pL (Date and time the issue has been reproduced: 10/10/2017 3:20 pm JST ) Account Info.(sample user name and device serial) https://drive.google.com/open?id=1uyMSaBfIOU5lyZuuv6zTdYyrRU3gNDlNu-Ty9A1KkR0
,
Nov 27 2017
Yuichiro-san is this related to 761714, and are you the right person to look into it?
,
Dec 11 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/5155214a1679dd8785e7db8bb8cada9b034fff81 commit 5155214a1679dd8785e7db8bb8cada9b034fff81 Author: Yingbing Wu <wuyingbing@chromium.org> Date: Mon Dec 11 05:08:06 2017 Make first party IME more robust. When first party IME is terminated unexpectedly, IME api will receive extension unload event and unregister all IMEs' components of the extension. Then the IMEs' menu on shelf will disappear. Although OS restart the first party IME extension at once, however, the IME menus can't be recovered. First party IME has more complicated initlization process other than the normal extension. Should not remove its states when it is crashed. Adds a condition in OnExtensionUnload to gurad not to unregister the first party IMEs. And records the extension id, then re-activate the extension when it reloads. Bug: 775507, 788247 , 786273 ,761714 Change-Id: I08731d2da82278483b843907aacb8256e0325e88 Reviewed-on: https://chromium-review.googlesource.com/803415 Commit-Queue: Shu Chen <shuchen@chromium.org> Commit-Queue: Yingbing Wu <wuyingbing@chromium.org> Reviewed-by: Shu Chen <shuchen@chromium.org> Reviewed-by: Yuichiro Hanada <yhanada@chromium.org> Cr-Commit-Position: refs/heads/master@{#523045} [modify] https://crrev.com/5155214a1679dd8785e7db8bb8cada9b034fff81/chrome/browser/extensions/api/input_ime/input_ime_api_chromeos.cc [modify] https://crrev.com/5155214a1679dd8785e7db8bb8cada9b034fff81/chrome/browser/extensions/api/input_ime/input_ime_api_chromeos.h
,
Dec 13 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/336b99553640c76a1bb09ee33f49dd575898cc7d commit 336b99553640c76a1bb09ee33f49dd575898cc7d Author: Yingbing Wu <wuyingbing@chromium.org> Date: Wed Dec 13 02:30:57 2017 Make first party IME more robust. When first party IME is terminated unexpectedly, IME api will receive extension unload event and unregister all IMEs' components of the extension. Then the IMEs' menu on shelf will disappear. Although OS restart the first party IME extension at once, however, the IME menus can't be recovered. First party IME has more complicated initlization process other than the normal extension. Should not remove its states when it is crashed. Adds a condition in OnExtensionUnload to gurad not to unregister the first party IMEs. And records the extension id, then re-activate the extension when it reloads. Bug: 775507, 788247 , 786273 ,761714 Change-Id: I08731d2da82278483b843907aacb8256e0325e88 Reviewed-on: https://chromium-review.googlesource.com/803415 Commit-Queue: Shu Chen <shuchen@chromium.org> Commit-Queue: Yingbing Wu <wuyingbing@chromium.org> Reviewed-by: Shu Chen <shuchen@chromium.org> Reviewed-by: Yuichiro Hanada <yhanada@chromium.org> Cr-Original-Commit-Position: refs/heads/master@{#523045}(cherry picked from commit 5155214a1679dd8785e7db8bb8cada9b034fff81) Reviewed-on: https://chromium-review.googlesource.com/818680 Cr-Commit-Position: refs/branch-heads/3282@{#193} Cr-Branched-From: 5fdc0fab22ce7efd32532ee989b223fa12f8171e-refs/heads/master@{#520840} [modify] https://crrev.com/336b99553640c76a1bb09ee33f49dd575898cc7d/chrome/browser/extensions/api/input_ime/input_ime_api_chromeos.cc [modify] https://crrev.com/336b99553640c76a1bb09ee33f49dd575898cc7d/chrome/browser/extensions/api/input_ime/input_ime_api_chromeos.h
,
Dec 15 2017
The following revision refers to this bug: https://chrome-internal.googlesource.com/chromeos/overlays/chromeos-overlay/+/ae409fee2790824062897bbe395e7ff4dfb4647e commit ae409fee2790824062897bbe395e7ff4dfb4647e Author: Yingbing Wu <wuyingbing@google.com> Date: Fri Dec 15 18:10:47 2017
,
Dec 18 2017
Now this should be fixed. Please reopen if it still happens.
,
Dec 19 2017
,
Dec 19 2017
This bug requires manual review: M64 has already been promoted to the beta branch, so this requires manual review Please contact the milestone owner if you have questions. Owners: cmasso@(Android), cmasso@(iOS), kbleicher@(ChromeOS), abdulsyed@(Desktop) For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Dec 22 2017
Added M64 label to hit search queries. This has been open for a while and not regressed in M64. Rejecting merge request. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by ryutas@chromium.org
, Nov 23 2017