Running firefox instance malfunctions after refresh of gnome-42-2204 snap
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
snapd (Ubuntu) |
In Progress
|
High
|
James Henstridge |
Bug Description
I noticed that my running instance of Firefox had become unstable, unable to load new pages and other malfunctions. According to "snap changes", the gnome-42-2204 snap had been updated overnight:
$ snap changes
ID Status Spawn Ready Summary
762 Done yesterday at 23:56 AWST yesterday at 23:56 AWST Auto-refresh snap "gnome-42-2204"
763 Done today at 11:41 AWST today at 11:41 AWST Auto-refresh snap "gnome-calculator"
In the journal, there were errors like:
Apr 15 13:06:41 scruffy firefox_
Apr 15 13:06:41 scruffy firefox_
Apr 15 13:06:41 scruffy firefox_
Apr 15 13:06:41 scruffy firefox_
Apr 15 13:06:41 scruffy firefox_
Looking at the running process's mount namespace, /proc/$
So the main persistent mount namespace for the snap was correctly updated. The problem is that the cloned namespace the app actually runs in (it's using the desktop interface, so runs in a separate namespace to set up $XDG_RUNTIME_
ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: snapd 2.59.1+23.04ubuntu1
ProcVersionSign
Uname: Linux 6.2.0-18-generic x86_64
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
CasperMD5CheckR
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr 15 13:19:38 2023
InstallationDate: Installed on 2021-03-28 (747 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210327)
RebootRequiredPkgs: Error: path contained symlinks.
SnapChanges: no changes found
SourcePackage: snapd
UpgradeStatus: Upgraded to lunar on 2023-03-19 (26 days ago)
tags: | added: dt-1264 |
Changed in snapd (Ubuntu): | |
importance: | Undecided → High |
Changed in snapd (Ubuntu): | |
status: | New → In Progress |
assignee: | nobody → James Henstridge (jamesh) |
We're able to reliably reproduce this with firefox built for core22 but not able to reproduce this with firefox for core20. Refresh of snapd or gnome-42-2204 triggers the issue, or something that seems likely related.