@linux Sharing a 'small' inconvenience I had to fix with #opensuse#slowroll (I suspect #tumbleweed is the same) - I couldn't launch snaps (spotify, bitwarden) after update - error was: cannot determine seccomp compiler version in generateSystemKey fork/exec /usr/lib/snapd/snap-seccomp: no such file or directory
The fix (I first tried re-installing, didn't work) was to:
a. locate snap-seccomp - was in /usr/libexec/snapd
b. symlink: ln -s /usr/libexec/snapd /usr/lib/snapd
Are you sure snapcraft requires the original developer publish snaps? This seems unlikely, but they may have updated their policies.
Edit: they aren’t, Signal for example is an unofficial snap not published by the Signal developers but rather “snapcrafters” - snapcraft.io/signal-desktop. This is very similar to how Flathub handles unofficial packages, except Flathub seems to have more gatekeeping (Snapcrafters doesn’t allow just anyone, but you don’t have to be part of that group to publish).
Snapcraft has hosted multiple malicious applications, so I wouldn’t exactly call it a safe place either.
Have. I like btrfs, you only get that with Oracle and they have philosophical issues, but also random brokenness with things like selinux policies.
Old packages aren’t really an issue for me, but missing packages that haven’t been put into EPEL can be a pain. Depends what you want to accomplish or need.
I feel similarly about Fedora’s quick EOL, which was how I got onto an enterprise desktop distro too. The paper cuts are why I ended up switching to Mint.
Just in time for Fedora to use it by default and create some interest. I get the maintenance burden though, RHEL patches their kernel like crazy. They still use XFS as default which I think is pretty unique at this point.