Chromium new tabs stop working when the core snap updates
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
snapd |
Confirmed
|
High
|
Unassigned |
Bug Description
I've been using the refresh awareness feature: https:/
That prevents chromium snap from updating while in use, which prevents a bug where opening a new tab stops working and gives SIGTRAP. (Very suboptimal, since now programs need to be closed and snap refresh manually called to get it to update, but I digress.)
However, today I got an update to the "core" snap and new tabs stopped working again.
Related: #1913027 and #1616650
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: chromium-browser 1:85.0.
ProcVersionSign
Uname: Linux 5.8.0-45-generic x86_64
ApportVersion: 2.20.11-
Architecture: amd64
CasperMD5CheckR
CurrentDesktop: ubuntu:GNOME
DRM.card0-DP-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DVI-D-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: enabled
dpms: On
status: connected
edid-base64: AP/////
modes: 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080 1600x1200 1680x1050 1280x1024 1280x1024 1440x900 1440x900 1280x960 1280x800 1152x864 1280x720 1280x720 1280x720 1280x720 1024x768 1024x768 832x624 800x600 800x600 720x576 720x576 720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480 720x400
DRM.card0-HDMI-A-2:
enabled: enabled
dpms: On
status: connected
edid-base64: AP/////
modes: 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080 1600x1200 1680x1050 1280x1024 1280x1024 1440x900 1440x900 1280x960 1280x800 1152x864 1280x720 1280x720 1280x720 1280x720 1024x768 1024x768 832x624 800x600 800x600 720x576 720x576 720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480 720x400
Date: Wed Mar 24 11:29:04 2021
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p3 ext4 504G 159G 319G 34% /home
tmpfs tmpfs 16G 267M 16G 2% /dev/shm
/dev/nvme0n1p3 ext4 504G 159G 319G 34% /home
InstallationDate: Installed on 2019-11-30 (479 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=
Snap.Changes: Error: command ['snap', 'changes', '--abs-time', 'chromium'] failed with exit code 1: error: no changes found
Snap.ChromeDriv
Snap.ChromiumVe
SourcePackage: chromium-browser
UpgradeStatus: Upgraded to focal on 2020-05-11 (316 days ago)
dmi.bios.date: 07/06/2018
dmi.bios.release: 5.13
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P4.90
dmi.board.name: AB350M Pro4
dmi.board.vendor: ASRock
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.
dmi.sys.vendor: To Be Filled By O.E.M.
This is indeed a problem in snapd, I believe the snapd team is already aware of it and working on a fix.