Issue metadata
Sign in to add a comment
|
Global WM keyboard accelerators sometimes don't work when no windows are open |
||||||||||||||||||||||||
Issue description(originally filed at http://b/68786455) Google Chrome 62.0.3202.74 (Official Build) (64-bit) Platform 9901.54.0 (Official Build) stable-channel eve This device is currently in a state where global window manager accelerators like Ctrl+T, Ctrl+N, Alt+1, and Ctrl+Alt+Comma don't do anything when there are no windows open on the current desktop. As soon as I create a window by e.g. clicking on the Chrome icon in the shelf, the accelerators start working. They also work after I right-click on the desktop to open a context menu. I'm logged into my google.com and gmail.com accounts, and both desktops exhibit the problem. Oshima thought this might be caused by ARC stealing the events (this device is running ARC since it's corp-enrolled, although I don't have any visible Android apps running). I tried killing all Android apps listed in the task manager (I'm unable to kill Android system processes), but it didn't help. I think I've seen this before, probably on a different corp-enrolled device that was also running ARC (maybe caroline?). It doesn't always happen -- if I log out and back in, I think the problem will go away. Oshima said that he's seen this before too.
,
Nov 3 2017
->khmel@ who worked on shortcut support for ARC++ ARC++ creates a window for system related windows, which is invisible by default, and I'm wondering if it has something to do with this. + afakhry@ who is the owner of ash accelerator. + mustash folks in case there was a known regression on (m)ash side.
,
Nov 3 2017
I have seen this as well, on a corp enrolled samus. mustash did refactor this to use a mojo interface from ash to chrome, but that landed ~11 months ago. https://chromium.googlesource.com/chromium/src/+log/60ceadfbf73da2c341f0c4cf7e2a5766d4a55895/chrome/browser/ui/ash/chrome_new_window_client.h
,
Nov 3 2017
+yhanada who did some recent work for android shortcuts.
,
Nov 7 2017
I'm seeing this again almost immediately on the same device after signing out and back in. What's the plan for tracking down the cause?
,
Nov 7 2017
Increasing priority, as this is an annoying bug that's present on the stable channel and potentially affects many users.
,
Nov 7 2017
,
Nov 8 2017
So far I cannot reproduce. I tried different builds, enrolled and not, mp-signed and test images. It works stable to me. I also traced event dispatching but did not find and suspicious. Do we have more-less reliable steps to repro? Can be reproduced on test image?
,
Nov 8 2017
The usual workflow under which I've seen this is: 1. Sign in to google.com account. 2. Sign in to gmail.com account as well. 3. Use both accounts for a while (without opening any Android apps). 4. At some point, notice that global accelerators stop working on both desktops unless there's at least one window open. I tried to repro this just now on a recent eve dev build (using two test accounts), but the problem hasn't shown up yet. Is there anything I can do to get more info the next time I see it?
,
Nov 8 2017
Thanks Daniel, I will try to use your scenario intensively. So far there is nothing special to look up, only if you find some regularity. To confirm, your scenario does not involve multi-profile configuration (primary + secondary profiles) and you just sign out one and sign in another account. Both accounts have ARC running. Right?
,
Nov 8 2017
This *does* involve multiprofile. I think I've only seen the bug on this eve device running 62, and it's always logged into both my google.com and gmail.com accounts. I don't think I've seen the bug on a caroline device that's also logged into both accounts, but it's still using 61.0.3163.123, so that's a useless data point if this is a regression in 62. Re "both accounts have ARC running", don't we only allow ARC to run on the primary account (i.e. google.com, in this case) right now?
,
Nov 8 2017
#11, Yes we use only primary account. Thanks for update
,
Nov 14 2017
This definitely happens inconsistently. I've been using the same system (now on 62.0.3202.82) with the same two accounts logged in for a few days and haven't re-encountered the problem yet. Earlier, I had rebooted while still on 62.0.3202.74 and saw the problem again almost immediately.
,
Nov 14 2017
I've just heard about this problem on Eve for just one public account. Trying to find repro on that device.
,
Feb 27 2018
It's been a long time since I've seen this, but it's happening again on a different device right now: Google Chrome 63.0.3239.140 (Official Build) (64-bit) Platform 10032.86.0 (Official Build) stable-channel caroline On my gmail.com account, I don't have any windows open and I'm unable to use Ctrl+N, Ctrl+Alt+Comma, etc. As soon as I open a window, those accelerators start working. On my primary google.com account, I have this window open and am able to use global accelerators.
,
Mar 6 2018
I'm hoping this is issue 780146 . I'll undupe if I still see it in M65. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by derat@chromium.org
, Nov 2 2017