Build and passes on Kubuntu CI now.

Kubuntu CI builds

In D18005#387324, @ngraham wrote:

However, just removing files from the repo doesn't actually remove them from users' machines; their packaging system does that. Perhaps we should alert packagers that for the 5.15 release, they shouldn't remove these files from users' machines when they disappear from the repo.

i.e. not before July 2019?

Setting this even Plasma session wide crashes Thunderbird, which is NOT acceptable.

Ok. Maybe wider testing in Disco 19.04.

In T10189#171295, @mparillo wrote:

So I installed it (should have done this first)

$ sudo apt install -y xdg-desktop-portal

In T10189#171260, @rikmills wrote:

In our case adding a 50-firefox.sh (arbitrary name) containing export GTK_USE_PORTAL=1 to /usr/share/kubuntu-default-settings/kf5-settings/plasma-workspace/env/ seems to work.

In T10189#171262, @clivej wrote:

Might have to patch xdg-desktop-portal-kde too with:

https://cgit.kde.org/xdg-desktop-portal-kde.git/commit/?id=ccea985840cf5b05b0359067854abc3da080e737

In T10218#171213, @ngraham wrote:

Yes. I expect at least D17780 (in some form) to land in 5.15. Possibly T10220 too, if we move fast enough.

In our case adding a 50-firefox.sh (arbitrary name) containing export GTK_USE_PORTAL=1 to /usr/share/kubuntu-default-settings/kf5-settings/plasma-workspace/env/ seems to work.

In T10189#171232, @clivej wrote:

Set it via a script in /etc/xdg/plasma-workspace/env/ ?

Using export GTK_USE_PORTAL=1

I think the problem with local desktop files is that if you remove Firefox or it has an updated desktop file the local one is still showing up.
Is there really no way to make a modified system-wide desktop entry?

We cannot modify the firefox desktop file.

Are upstream changes being looked at likely for plasma 5.15?

I know it's a store.kde.org package and not a distro package, but is there any way we can ship with it anyway? Do we have some facility for automatically installing store.kde.org content?

In T10230#171174, @ngraham wrote:

Sure, here are some screenshots.

We already had the 11pt discussion, and decided against. It just makes the things bigger and more clownish looking (as if a 3 year old with bad eyesight had designed it), and bumps the UI scaling in ways that hurt on older hardware with lower size/res screens.

I have always thought the Ubuntu font looks quite 'unamazing' on KDE, but that is a very subjective, personal and likely hardware and setup dependant thing.

I have someone on IRC asking....

In D17375#373278, @ngraham wrote:

That's what I thought. Then it doesn't fully fix 401810, since people not using Kubuntu or Neon will still not have a way to change the update frequency.

In D17375#373049, @ngraham wrote:

This helps for Kubuntu (and Neon ?) users, but what about everyone else?

Seems good to me, and a quick test on a stock Kubuntu install gets the updater registering new updates when the system does its own refresh.

@tsimonq2 is going to document, based on lubuntu's switch, what we would need to do. Once we have that then we can make an informed assessment on whether this can be targeted for 19.04.

I think this is needed in 18.12 branch as well?

And we have a casualty from this ;)

Can easily make a test exfat volume to mount in virtualbox, so should be simple to test. Similar code to install samba via packagekit exists in kdenetwork-filesharing source, so this should be possible.

Ok. Could be doable. My initial comment stands though. I would want a legal OK from higher up.

$ seeded-in-ubuntu fuse-exfat
fuse-exfat's binaries are not seeded.

Doubt we can do this unless this can be shown to be wrong AND it gets ok'd by Ubuntu/Canonical legally.