Lxqt-support, automatic review failed "content interface expose binaries or libraries"

store
1

Hello, I would like to know the reason why the new revision of lxqt-support was blocked. Is it because it now has automatic connection? This hadn’t happened before.

The beginning of the error is “content interface expose binaries or libraries”, and then it specifically mentions the files that make lxqt-support what it is.

lxqt-support is generated using only the LXQT and Kvantum repositories; it’s the same as the previous revisions, I only changed the versions being built because a new version of LXQT was released (2.3.0).

2

Hi @Kyuyrii , the snap indeed seems to be exposing binaries or libraries via a globally auto-connected slot. Please either remove the offending files from the exposed directories or follow the process for aliases, auto-connections and tracks (https://snapcraft.io/docs/process-for-aliases-auto-connections-and-tracks) and create a post in the ‘privileged-interfaces’ category (privileged-interfaces - snapcraft.io) requesting its use.

1 Like
3

In this case, I already requested automatic connection, and it was after receiving it that Snap started being rejected during automatic verification; before, it launched without problems.

And there’s nothing to remove from it; it contains files necessary for the lxqt-plugin to function, as well as Kvantum, and also offers some things that may be necessary to launch LXQT apps on Snapcraft.

The lxqt-archiver Snap even uses lxqt-support to function.

Since this is the first time I’m having this kind of problem, I’m confused about exactly what needs to be done.

The lxqt-support Snap is similar to kf6-core, which is from KDE, but while kf6-core has things about QT and KDE, lxqt-support has things about LXQT.