Ubuntu
chromium-browser package

[snap] after accepting daily updates Chromium doesn't accept keyboard input

Bug #1863412 reported by Paul White
30
This bug affects 7 people
Affects Status Importance Assigned to Milestone
chromium-browser (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

I booted my laptop this morning and was offered a large number of updates. I installed them all and started Chromium only to find that I was unable to type any character into the address bar. When using the mouse to select a bookmark to load a web page I found that keyboard input was also ignored.

I was running Chromium when last using this Ubuntu installation and made no changes before closing down. The only changes since that last session were made by the updates that I installed so I have attached an extract of apt's history.log.

Google Chrome and Firefox work perfectly. Xubuntu doesn't seem to be affected by recent updates.

Work around found:
Remove ~/snap/chromium/common/.cache and restart Chromium

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: chromium-browser 80.0.3987.87-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu16
Architecture: amd64
CurrentDesktop: GNOME
DRM.card0-DP-1:
 enabled: enabled
 dpms: On
 status: connected
 edid-base64: AP///////wAdZRUCAQAAACoVAQSlNB544gywoldRnycKUFS/zwDRwLMAlQCBgIGKgQCBSgEBAjqAGHE4LUBYLEUACSUhAAAeAAAA/wAwMDAwMDAwMQogICAgAAAA/QA4Sx5TDwAKICAgICAgAAAA/ABFRjIyMGEKICAgICAgAGI=
 modes: 1920x1080 1680x1050 1280x1024 1280x1024 1280x1024 1440x900 1280x960 1280x800 1024x768 1024x768 1024x768 800x600 800x600 800x600 800x600 640x480 640x480 640x480 640x480 720x400
DRM.card0-HDMI-A-1:
 enabled: disabled
 dpms: Off
 status: disconnected
 edid-base64:
 modes:
DRM.card0-HDMI-A-2:
 enabled: disabled
 dpms: Off
 status: disconnected
 edid-base64:
 modes:
DRM.card0-HDMI-A-3:
 enabled: disabled
 dpms: Off
 status: disconnected
 edid-base64:
 modes:
DRM.card0-eDP-1:
 enabled: enabled
 dpms: On
 status: connected
 edid-base64: AP///////wANrsQVAAAAACgXAQSVIhN4Au8FkFRSkyklUFQAAAABAQEBAQEBAQEBAQEBAQEBXjWAlnA4FEAsHCQAWMEQAAAYAAAA/gBOMTU2SEdFLUVBQgogAAAA/gBDTU4KICAgICAgICAgAAAA/gBOMTU2SEdFLUVBQgogAB0=
 modes: 1920x1080
Date: Sat Feb 15 11:00:22 2020
DiskUsage:
 Filesystem Type Size Used Avail Use% Mounted on
 /dev/sda2 ext4 73G 16G 54G 23% /home
 tmpfs tmpfs 3.9G 174M 3.7G 5% /dev/shm
 /dev/sda2 ext4 73G 16G 54G 23% /home
InstallationDate: Installed on 2019-05-17 (274 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517)
MachineType: Novatech N350DW
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic root=UUID=35cc812a-75e8-4a5a-83d0-bd336006d2f6 ro quiet splash vt.handoff=7
Snap.Changes: Error: command ['snap', 'changes', '--abs-time', 'chromium'] failed with exit code 1: error: no changes found
Snap.ChromeDriverVersion: ChromeDriver 80.0.3987.100 (3f00c26d457663a424865bbef1179f72eec1b9fe-refs/branch-heads/3987@{#864})
Snap.ChromiumVersion: Chromium 80.0.3987.100 snap
SourcePackage: chromium-browser
UpgradeStatus: Upgraded to focal on 2019-11-08 (98 days ago)
dmi.bios.date: 03/10/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5.12
dmi.board.asset.tag: Tag 12345
dmi.board.name: N350DW
dmi.board.vendor: Novatech
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Novatech
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd03/10/2017:svnNovatech:pnN350DW:pvrNotApplicable:rvnNovatech:rnN350DW:rvrNotApplicable:cvnNovatech:ct10:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: N350DW
dmi.product.sku: Not Applicable
dmi.product.version: Not Applicable
dmi.sys.vendor: Novatech

See original description
Revision history for this message
Paul White (paulw2u) wrote :
Paul White (paulw2u)
description: updated
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in chromium-browser (Ubuntu):
status: New → Confirmed
Revision history for this message
Paul White (paulw2u) wrote :

Work around found: Remove ~/snap/chromium/common/.cache after closing browser. Chromium works as it should when restarted. I'll leave this bug report in place as the problem shouldn't have happened and needs investigation.

description: updated
Revision history for this message
Cliff Carson (ccarson1) wrote :

The work around indeed worked for me but when I tried to recover my Bookmarks from an archive file after pressing "Choose a file" chromium terminated. Think this message in syslog is associated with the error:

Feb 15 13:17:54 cliffps chromium_chromium.desktop[6306]: Gtk:ERROR:../../../../gtk/gtkiconhelper.c:494:ensure_surface_for_gicon: assertion failed (error == NULL): Failed to load /snap/chromium/1026/data-dir/icons/Adwaita/16x16/status/image-missing.png: Unrecognized image file format (gdk-pixbuf-error-quark, 3)

Revision history for this message
Paul White (paulw2u) wrote :

See bug 1863460, gnome-calculator also affected.

Revision history for this message
Chris Guiver (guiverc) wrote :

On morning of Feb 14 (my local time; AEST) I awoke my suspended box, applied all updates, closed chromium & programs and rebooted.

On reboot, once system was going (and 'settled') I loaded my usual programs and later chromium, to discover no keyboard input was allowed into chromium. I fought with this for some time before putting up a help request on irc

https://irclogs.ubuntu.com/2020/02/15/%23ubuntu+1.txt
[05:33] <guiverc> my `chromium-browser` isn't accepting any text input into page/url/window... i've logged out, restarted but no difference. `snap refresh --beta chromium` to try a different version; no change. any clues appreciated

I had worked out if I had active a 'text entry' box, I couldn't use ^N to open a new page, however if a text entry box wasn't on page & my cursor wasn't in the url line ^N would respond (to open new page). Except for keyboard, chromium responded normally to mouse input.

In time Oerheks answered my plea for help on irc, `rm` cache directory didn't do anything for me (~/snap/chromium/common/.cache/chromium/Default/Cache)

I started erasing my config directory

[11:58] <guiverc> oerheks, success !!! (my continual re-load of chromium must have re-introduced issue whatever it was (into cache possibly), I redid some of prior commands (rm cache) & now it's working)... Thanks HEAPS !!

So in the end it was removing cache that fixed it maybe, though I'd also removed a good deal of my config too before I noticed the beneficial effect..

I had tested another already running snap; telegram-desktop, and that accepted keyboard input during the time chromium wasn't.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.