Kubuntu (/kuː.ˈbuːn.tuː/ koo-boon-too) is an official flavour of the Ubuntu operating system which uses the KDE Plasma Desktop instead of GNOME Shell. As part of the Ubuntu project, Kubuntu uses the same underlying systems. Every package in Kubuntu shares the same repositories as Ubuntu, and it is released regularly on the same schedule as Ubuntu.
Phab Wiki: https://phabricator.kde.org/w/kubuntu/
Committed to git and uploaded:
We do blacklist it: http://people.canonical.com/~ubuntu-archive/seeds/kubuntu.bionic/desktop
Package now called network-manager-config-connectivity-ubuntu
Another option might be to ship PIM on LTS releases, as business/institutions etc are more likely to use those, but excluded it from our interim isos. Make our releases with support for 9 months more lightweight ones.
We removed the gtk3-nocsd hack, so this is no longer relevant.
Anyway, I've been using the Flatpak backend in Kubuntu and there are some bugs that would make me not want to ship it or make it the default backend without more testing, bugfixing, and polishing. It's really promising though, and I encourage folks to try it out.
The root causes are different, but the issue of duplicate apps is the same, from a user perspective.
@ngraham No, you didn't run into the same issue. Flatpak does provide an appstream id, that doesn't mean it's the right one though ;) This is something to bring to blender devs, not kubuntu.
In the absence of a packaged Snap backend, I've been trying out the Flatpak backend with Flathub on Kubuntu and I ran into the same problem that @apol mentioned: duplicate entries (https://bugs.kde.org/show_bug.cgi?id=387790). The issue seems to be that the appstream IDs differ between the Flathub versions and the distro-packaged versions; e.g. Flathub Blender is org.blender.Blender.desktop, while Kubuntu's blender package is blender.desktop. Since the appstream IDs differ, Discover shows duplicate entries, leading to a confusing user experience. I bring this up here bevcause every single overlapping package in Kubuntu (seems like all of them, so far) needs its appstream ID adjusted to not overlap with the Flathub version.
Hi everyone, really excited to see attention to the subject!
Aleix is going to talk with snapcraft -devs, but sounds like we may be able to enable the snap backend when we do Plasma 5.12
I think we should either have one backend or no backends installed automatically by default (so that we don't give the impression that we're endorsing one or the other).
The snap backend is or was a proof of concept bit of code, and is still deliberately set to a default of OFF in cmake for building.
Well, it would be nice to see snaps offered for those who want them. Are the KDE store offerings available through Discover?
Personally my vote goes to Flatpak. It seems like it has better momentum at this point, and there's the added bonus that its backend is already packaged and available in Kubuntu.
This is in Bionic now and should fix symbols issues: https://launchpad.net/ubuntu/+source/libindi/1.4.1+dfsg-3ubuntu1
latest master of kmail now needs libini => 1.5