KDE/Plasma Status Update 2020-09-03
Yesterday I have updated my builds of Plasma for Debian to Plasma 5.19.5, which are now available from the usual sources, nothing has changed.
[Update 2020-09-03: KDE Apps 20.08.1 are also now available]
On a different front, there are good news concerning updates in Debian proper: Together with Scarlett Moore and Patrick Franz we are in the process of updating the official Debian packages. The first bunch of packages has been uploaded to experimental, and after NEW processing the next group will go there, too. This is still 5.19.4, but a great step forward. I expect that all of Plasma 5.19.4 will be available in experimental in the next weeks, and soon after also in Debian/unstable.
Again, thanks to Scarlett and Patrick for the good collaboration, this is very much appreciated!
Hey Norbert, thanks for the work you put into this. I just installed debian on a laptop and tried using your repos. I have added your key to the trusted folder, however I get this:
W: GPG error: https://download.opensuse.org/repositories/home:/npreining:/debian-kde:/other-deps/Debian_Unstable ./ InRelease: The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY B8AC39B0876D807E
E: The repository ‘https://download.opensuse.org/repositories/home:/npreining:/debian-kde:/other-deps/Debian_Unstable ./ InRelease’ is not signed.
The repos added are the following:
deb https://download.opensuse.org/repositories/home:/npreining:/debian-kde:/other-deps/Debian_Unstable/ ./
deb https://download.opensuse.org/repositories/home:/npreining:/debian-kde:/frameworks/Debian_Unstable/ ./
deb https://download.opensuse.org/repositories/home:/npreining:/debian-kde:/plasma519/Debian_Unstable/ ./
deb https://download.opensuse.org/repositories/home:/npreining:/debian-kde:/apps2008/Debian_Unstable/ ./
deb https://download.opensuse.org/repositories/home:/npreining:/debian-kde:/other/Debian_Unstable/ ./
Am I missing something here? apt https transport is installed.
Yes, the repos are signed with my OBS key which is linked every time I list the repos, please look at one of the previous posts for explanations how to import.
Did you sign the repos? I’m getting a GPG error.
Yes, repos are signed with my OBS key. This is mentioned in many of the previous blogs on KDE, with a link to the key that needs to be imported.
Ah yes, that’s the one I forgot about. I figured your latest post on the release was the relevant one. Thank you for getting back to me so fast.
Thanks a lot for working together with other Debian developers to refresh Plasma there and thanks to them for finally moving things forward!
This made my day. Very happy to read efforts are shared again with Debian Qt/KDE maintainers!
Good job man. Thanks for sharing with us. Looking forward to upgrade from Debian SID repos
Thanks Norbert, thanks from a Debian user.
Thanks Norbert by a Debian Testing user
this is very good news, Norbert,
it feeds the hope to get an up-to-date KDE in the next official Debian release(s).
Great news!
For some reason with Plasma 5.19.5, I don’t see any configuration UI for GTK style in System Settings > Application Style.
I have these packages installed:
kde-config-gtk-style:amd64 4:5.19.5-1~np1
kde-config-gtk-style-preview:amd64 4:5.19.5-1~np1
Is that expected, or I’m missing something?
Hmm, I see a button in the lower part of the windows labelled “Configure GNOME/GTK Application Style”, right next to “Configure Icons and Toolsbars”. Is the GNOME/GTK button missing on your side?
You are right, I totally missed that, because before GTK configuration was another entry together with “Application Style” and “Window Decorations”. Thanks for the tip!
hanks Norbert by a Debian Sid user
Plasma 5.19.5 works great. Thanks! Still have to disable qt logging but for the rest it is working really nice.
Could you also update kwin-lowatency to 5.19.5?
I noticed you tried to build kwin-lowlatency 5.19.5 but it failed. I had the same problem and somehow fixed it by removing /usr/share/locale in kwin-data.install. Not sure if it is entirely correct but it seems to work.
Thanks indeed, I had to do this for the previous version, too, but forgot to do it for the new! Thanks for reminding me.
Hi, again, thank you very much for your continuous efforts for updating KDE to Debian users! Out of curiosity in the last weeks I’m getting a few packages kept back, do you have any idea why? This is on Debian Testing/Bullseye.
$ apt list –upgradable
Listing… Done
libkdsoap-bin/unknown 1.9.0-1~np1 all [upgradable from: 1.9.0-1~np1]
libkdsoap1/unknown 1.9.0-1~np1 amd64 [upgradable from: 1.9.0-1~np1]
libkf5dav-data/unknown 1:5.74.0-1~np1 all [upgradable from: 20.04.3-1~np1]
libkf5dav5/unknown 1:5.74.0-1~np1 amd64 [upgradable from: 20.04.3-1~np1]
libpython2-stdlib/testing,unstable 2.7.18-2 amd64 [upgradable from: 2.7.17-2]
python2-minimal/testing,unstable 2.7.18-2 amd64 [upgradable from: 2.7.17-2]
python2/testing,unstable 2.7.18-2 amd64 [upgradable from: 2.7.17-2]
$ sudo apt full-upgrade
(…)
The following packages have been kept back:
libkf5dav-data libkf5dav5 libpython2-stdlib python2 python2-minimal
Hi João,
the Python packages hanging is due to a different reason, you probably have still some packages depending on “python” as is. This is independent from my packages.
Why the kdav stuff is not updated is strange. They have moved from apps to frameworks, so I guess you have to manually force installation. This should happen automatically if you install a package that depends on them, but otherwise you have to do “dist-upgrade” or update manually.
Thank you for your reply. I just did a new upgrade and now, for some reason those python packages were upgraded. I guess some installed package dependencies were at play here. The kdav packages are still held back. Do note I always do an “apt full-upgrade” which is the same as “apt-get dist-upgrade”.
$ sudo apt full-upgrade
(…)
The following packages have been kept back:
libkf5dav-data libkf5dav5
The following packages will be upgraded:
libpython2-stdlib python2 python2-minimal
3 upgraded, 0 newly installed, 2 to remove and 2 not upgraded.
I then installed those 2 packages manually and now all is good. Not sure why this happened, because of moving them to the frameworks repository? Or maybe the different version numbering? Can it be related to the “unknown” distribution, possibly missing on the package information? Anyway I got it sorted now, thanks! However perhaps this may be of use for someone else.
do you think is it possible, that you do something like KEBIAN ? like buster but with a newer complete version of kde which is complete out like 5.16 or 5.17 or the kde 5.18 LTS, which will get at least two future bugfix releases ?
Sorry, buster ships too old a libQt, thus compiling recent Plasma is not possible on it. Already 5.18 requires Qt 5.14 which is not available, and thus one would need to recompile (and possibly fix) all Qt depending packages, which is less a fun I guess.