DNS for snaps like Firefox and Chromium fails

[David Kastrup]

While this sounds somewhat similar to the currently reported showstopper, none of the workarounds in that report helps for me and all snaps are affected.

This started about a week ago. I am currently making do with using the natively installed Epiphany while using Firefox to refer to my login data.

There is a report on Stackexchange that sounds like what I experience: https://askubuntu.com/questions/1510668/network-problems-with-snap-apps

My own system, however, is not Kubuntu but an Ubuntu Studio variation. Also there have been some very manual recoveries in its history (because the system was completely broken after some updates, I had to boot a recovery system, mount the file system of the broken system and do updates with changed root settings).

As a result, I cannot rule out that not all permissions and other package details may be the same as on a pristine system: after all, it would appear that few other people see this problem. However, I am out of my depth regarding how to address this, why the problem suddenly manifested itself about a week ago (the last manual recovery is a few months back) and how to get back to a working system.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: snapd 2.62+24.04build1
ProcVersionSignature: Ubuntu 6.8.0-25.25.3-lowlatency 6.8.1
Uname: Linux 6.8.0-25-lowlatency x86_64
ApportVersion: 2.28.1-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: XFCE
Date: Fri Apr 19 11:27:37 2024
InstallationDate: Installed on 2011-10-14 (4571 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
SourcePackage: snapd
UpgradeStatus: No upgrade log present (probably fresh install)

[Launchpad Janitor (janitor)]

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

[pmeerw (pmeerw)]

is an issue with 6.8.0-25 kernel (lowlatency), solved with 6.8.0-28 kernel

[David Kastrup (dak)]

I can certify that after today's system upgrade (mainly including the 6.8.0-28-lowlatency kernel), booting into the new kernel made the difference between Chromium-browser not working and working (I had previously replaced my Firefox browser with a native version from Mozilla's APT repository because I needed it working, so I could not easily test with that).

Definitely a showstopper kind of bug; surprised there weren't more reports to be found.