As per this issue, it seems dependencies (in this case, KDE Frameworks 5) of installed snaps (in this case, KeePassXC) are not automatically installed / updated when the snap package is updated.
Point in case, my 2 systems (Ubuntu Studio 22.04 and Pop!OS 22.04) recently automatically updated to KeePassXC 2.7.8. Right after updating, KeePassXC fails to run without any error shown to the user.
When running keepassxc from the console, the following error is thrown:
ERROR: not connected to the kf5-5-113-qt-5-15-11-core22 content interface.
After some digging, I found out the kf5-5-113-qt-5-15-11-core22 snap package was missing (which could be seen as an issue on it’s own - why doesn’t snap provide more useful info such as ERROR: kf5-5-113-qt-5-15-11-core22 package not installed. ?).
After manually installing this package, KeePassXC worked flawlessly again.
Other users mentioned they removed and re-installed KeePassXC in order to work around this issue (probably because they, like me at first, had no idea they could simply install the missing dependency), but this leads to the existing config being purged as well (quite a pita if you forgot to make a backup).
However, this also means that this issue only surfaces when upgrading existing snaps.
The maintainer of KeePassXC insists this is a snapd issue, and has tried to get it fixed back in 2022. Fast forward 2 years and the issue is still here. As a matter of fact, the maintainer is so fed up with snaps because of issues like this, he’s on the verge of abandoning Snap in favor of Flatpak Personally, I think both formats have their issues and benefits, and I’d prefer sticking to snap if possible.
So in an effort to move it ahead, I’m posting here.
Thanks for your reply @angela683 . I think I did all of the above (except for contributing code as my skillset is unfortunately lacking in that area), and also added info to the bugreport on Launchpad.
How should I go about advocating for improvement, besides posting here and on Launchpad?
They’re unhelpful when they add the phishing link in later. Well, less helpful I guess if you ignore the one letter in blue!
For this problem this vaguely reminds me of similar discussions recently in another snap, Opera, where the tl;dr was store policies were overriding the autoconnection of the content interface.
Is it possible the same is going on here? When I look at KeepassXC I see:
An unconnected DBus plug (I’m sure there are valid reasons but this one doesn’t look like one to me?, especially given it clearly isn’t necessarily as it being unconnected by default doesn’t break “much”), and in the assertion:
@James-Carroll unfortunately this doesn’t appear to be the same issue - in this case keepassxc has no existing content plug rules defined - so this feels more like a bug in snapd to me - @pedronis@zyga can you comment?
Personally, I think both formats have their issues and benefits, and I’d prefer sticking to snap if possible.
So in an effort to move it ahead, I’m posting here.