Same here, argh…
Also using Tumbleweed, all my snaps stopped working with above error - in fact, it’s the exact same error, ever since I updated systemd to 249 (had about 3k updates that poured in that night)
OK, it’s been (almost) a week now since each and every snap is showing above error - I’m royally fed up to be honest, this is a joke!!! @Aleksey I recommend to switch to Flatpak one Tumbleweed like me - everything works there (and unlike I don’t even have to deal with those block-characters like in Snapd) and I don’t have issues… what a shame
@SpaceDude thanks, I already switched to flatpack with Telegram - indeed it is much more reliable and seems based on more recent packages or Ubuntu version, the only inconvenience - there is no unread messages counter in the tray icon and was forced to copy settings manually. However I can’t switch with acestream as there is no such package there.
this thread was opened 2 days ago, late on a friday … if it has been almost a week, why did you not report it when it started happening but now complain that (paid) developers do not immediately pick it up over a (free) weekend ?
i’m sure the snapd team will look at it once they are seeing it tomorrow when their work week starts … please be patient …
Good point - and I will be patient as I do like Snap! Given the magnitude of my snap issues I honestly thought I may have configured my system wrong or something - searching for some other users having the same issue I only came across @Aleksey’s issue with Telegram, that’s when I chimed in.
But @ogra you’re absolutely right, I should have reported it… even though not many OpenSUSE Tumbleweed users seem to use Snap
In any case, thank you for your feedback - I’m anxiously awaiting the fix!
I’ve proposed a fix to snapd and cherry picked that to the snapd package, which already landed in the system:snappy repository. You can try zypper dup to get the latest version.
@mborzecki does not crash now, but have same error like acstreamplayer:
> telegram-desktop
WARNING: cgroup v2 is not fully supported yet, proceeding with partial confinement
telegram-desktop: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /var/lib/snapd/lib/gl/libGLX.so.0)
telegram-desktop: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /var/lib/snapd/lib/gl/libGLdispatch.so.0)
Well, that explains the failure. Since snap does not ship nvidia drivers, they are brought in from the host and need to execute inside the namespace of the snap. In your case, libGLX was apparently built using a newer libc than what is available in core20 (the current base snap of telegram-desktop). This is unexpected, as nvidia took care to provide binary drivers were compatible with older libc. Did you install those drivers yourself or from the repositories provided by nvidia for opensuse?
@ogra@Aleksey just updated my Tumbleweed system - it also included an update for snapd - and all is good again: all my snaps work again as I would expect them to work!
Confidence restored, currently chewing on my foot…
Next time I’ll post my problem sooner. Thanks everyone!
Yeah, this is a different problem now, but I’m afraid I don’t have a good solution here. I think a similar issue was reported on Ubuntu 21.10, but they patched in at the distro level.
In short, libGLX these days comes from the distro. Historically this was part of the nvidia drivers package, was linked with old glibc versions and thus compatible with even old base snaps. With glvnd, nvidia drivers only ship libGLX_nvidia.so, while libGLX comes from the host. Tumbleweed was rebuilt with new glibc, so all libraries require at least 2.34 GLIBC symbol version. However, this makes libGLX also incompatible with anything that isn’t built with this new glibc release.
Maybe snapd can provide the nvidia libraries, like flatpak does with org.freedesktop.Platform.GL.nvidia-*. That’s how flatpak manages to avoid this problem.
