Observed random blank ARC notifications |
||||
Issue descriptionChrome OS: 10032.21.0/ 63.0.3239.26 dev channel eve device Steps: No exact steps to repro this issue as this was a random notification. I had installed CNN app and was receiving frequent news alerts from this app. Result: Observed random blank ARC notifications in the notification center. Nothing happens on clicking settings (gear) icon in the notification. Attached are the screenshots and logs.
,
Nov 10 2017
I assume something gets into inconsistency state around async calls of mojo/wayland IPC.
,
Nov 14 2017
I don't repro yet, but let me try to fix a possible race.
,
Nov 21 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/d1ba6a22d197e182ba495aee0290dc29e79df1d4 commit d1ba6a22d197e182ba495aee0290dc29e79df1d4 Author: yoshiki iguchi <yoshiki@chromium.org> Date: Tue Nov 21 12:19:45 2017 Don't re-show a removed notification This patch makes the code distinguishing an update event from a post event (= create or update). Previously, we use only a post event as a mix of update or create events. But it may cause recreating removed- notification. This patch solves this issue by adding update-only event. This may also fix the issue of blank ARC notification ( crbug.com/780333 ). This CL works with: - crrev.com/c/768340 - ag/3251247 - ag/3251248 Bug: 780333 Change-Id: Icbded9b80838a1e863e682fb4174c6ed20a25f44 Reviewed-on: https://chromium-review.googlesource.com/768340 Reviewed-by: Mattias Nissler <mnissler@chromium.org> Reviewed-by: Eliot Courtney <edcourtney@chromium.org> Commit-Queue: Yoshiki Iguchi <yoshiki@chromium.org> Cr-Commit-Position: refs/heads/master@{#518224} [modify] https://crrev.com/d1ba6a22d197e182ba495aee0290dc29e79df1d4/components/arc/common/notifications.mojom [modify] https://crrev.com/d1ba6a22d197e182ba495aee0290dc29e79df1d4/ui/arc/notification/arc_notification_manager.cc [modify] https://crrev.com/d1ba6a22d197e182ba495aee0290dc29e79df1d4/ui/arc/notification/arc_notification_manager.h
,
Nov 22 2017
Should be fixed. Please feel free to reopen if the issue still happens. |
||||
►
Sign in to add a comment |
||||
Comment 1 by dhadd...@chromium.org
, Nov 3 2017