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:
interface Plug Slot Notes
content[icon-themes] keepassxc:icon-themes gtk-common-themes:icon-themes -
content[kf5-5-113-qt-5-15-11-core22-all] keepassxc:kf5-5-113-qt-5-15-11-core22 kf5-5-113-qt-5-15-11-core22:kf5-5-113-qt-5-15-11-core22-slot -
content[sound-themes] keepassxc:sound-themes gtk-common-themes:sound-themes -
dbus - keepassxc:session-dbus-interface -
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:
type: snap-declaration
format: 1
authority-id: canonical
revision: 1
series: 16
snap-id: jf2HsR51rlftaREcwhtxiEcDc76gL4O6
publisher-id: apCKcXygvsIEvn1HNfO28dUQ4l82DFEE
slots:
dbus:
allow-connection:
-
slot-attributes:
name: org.keepassxc.KeePassXC.MainWindow
deny-auto-connection: true
snap-name: keepassxc
timestamp: 2022-03-02T20:19:16.684500Z
sign-key-sha3-384: BWDEoaqyr25nF5SNCvEv2v7QnM9QsfCc0PBMYD_i2NGSQ32EF2d4D0hqUel3m8ul
@alexmurray Does this look similar to you as was with Opera?