[snap] At first run on bionic, keyboard input is delayed by more than 10 seconds (by fontconfig cache generation)
Bug #1771380 reported by
Olivier Tilloy
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
chromium-browser (Ubuntu) |
Fix Released
|
Medium
|
Olivier Tilloy |
Bug Description
This seems to happen only the first time the chromium snap is run after installing it afresh (not after upgrading).
Steps to reproduce:
1) $ snap remove chromium # in case it was already installed
2) $ snap install chromium
3) $ snap run chromium
4) wait for the welcome page to be fully loaded, then press Ctrl+L to focus the omnibox (aka address bar)
Expected result: the omnibox is instantly focused and its text is selected, key strokes are registered and input into it
Current result: there's a long delay before the omnibox is actually focused and its text selected, more than 10 seconds.
Changed in chromium-browser (Ubuntu): | |
importance: | Undecided → Medium |
To post a comment you must log in.
It's not just the omnibox that's unresponsive for some time at startup. It appears that anything that involves keyboard input is delayed, e.g. opening the task manager with Shift+ESC, or opening a new tab with Ctrl+T (however opening a new tab by clicking on the button to the right of the first tab is instantaneous, but then pressing a key to start typing in the omnibox lags by the same delay).