Discover is able to install Snaps using current confinement but not Snaps using classic confinement. The snaps tested were OBS Studio (current) and Skype (classic/legacy). On the command line, `snap` installs `obs-studio` immediately, while with the `skype` snap it halts to print a warning message about legacy confinement before forcing the user to type the command again with the `--classic` flag. I believe the correct behaviour for Discover should be somewhere between showing a dialogue box that warns the user of the lack of sandboxing with classic snaps, and not showing classic snaps at all.
Git commit fa278f29ff9a5e6fea814e18574de3c271dba7b8 by Aleix Pol. Committed on 06/04/2018 at 18:21. Pushed by apol into branch 'master'. Snap: make it possible to install "Classic" apps Classic, which is an euphemism for unsafe, applications were not supported so far. Now it will ask the user for confirmation to install. M +2 -2 libdiscover/backends/SnapBackend/SnapBackend.cpp M +32 -9 libdiscover/backends/SnapBackend/SnapTransaction.cpp M +6 -2 libdiscover/backends/SnapBackend/SnapTransaction.h https://commits.kde.org/discover/fa278f29ff9a5e6fea814e18574de3c271dba7b8
I could not reproduce the obs-studio issue. It installs fine here. If you could investigate a bit further I'd appreciate it very much. WRT skype, now it allows to install it if the user accepts the lack of confinement.
Sorry, I meant to say that obs-studio installs fine in Discover, and that this only affects classic snaps. I'll test this as soon as I can (I'll try building Discover and, failing that, I'll let you know as soon as a binary version is available for KDE Neon). Thanks.
Ah okay, then it's fixed in master (i.e. 5.13). :)
*** Bug 393641 has been marked as a duplicate of this bug. ***