Using the same plug name "kde-frameworks-5-plug" for all providers leads to problems when an application updates its base or changes its default provider because a new framework snap gets published for the same base. In that case, snapd will keep the old framework snap connected and will happily connect the new framework snap in addition to the old one. This breaks applications because they won't find the correct framework snap mounted at $SNAP/kf5. Prevent this by using the same strategy that the gnome extensions use: plug name = content snap name See https://forum.snapcraft.io/t/snap-accumulates-content-interface-connections-to-multiple-platform-snaps/27523/8 - [x] Have you followed the [guidelines for contributing](https://github.com/snapcore/snapcraft/blob/master/CONTRIBUTING.md)? - [x] Have you signed the [CLA](http://www.ubuntu.com/legal/contributors/)? - [x] Have you successfully run `./runtests.sh static`? - [x] Have you successfully run `./runtests.sh tests/unit/project_loader/extensions`? ----- I built a snap (anki-ppd) with this change and everything works as expected. Also CC @jriddell. I'm not sure about the subsystem prefix; it seemed more complete than just "extensions".