OBS builds of KDE/Plasma for Debian/Bullseye – Testing – Unstable

With the release of Debian/Bullseye last week, we can now support the stable Debian release (Bullseye) as well as Testing and Unstable releases with our build of KDE/Plasma (frameworks, plasma, gears, related programs) on the OBS builds. We used this switch to also consistently support three architectures: amd64, i386, and aarch64.

To give full details, I repeat (and update) instructions for all here: First of all, you need to add my OBS key say in /etc/apt/trusted.gpg.d/obs-npreining.asc and add a file /etc/apt/sources.lists.d/obs-npreining-kde.list, containing the following lines, replacing the DISTRIBUTION part with one of Debian_11 (for Bullseye), Debian_Testing, or Debian_Unstable:

deb https://download.opensuse.org/repositories/home:/npreining:/debian-kde:/other-deps/DISTRIBUTION/ ./
deb https://download.opensuse.org/repositories/home:/npreining:/debian-kde:/frameworks/DISTRIBUTION/ ./
deb https://download.opensuse.org/repositories/home:/npreining:/debian-kde:/plasma522/DISTRIBUTION/ ./
deb https://download.opensuse.org/repositories/home:/npreining:/debian-kde:/apps2108/DISTRIBUTION/ ./
deb https://download.opensuse.org/repositories/home:/npreining:/debian-kde:/other/DISTRIBUTION/ ./

Notes

Bullseye and pinning

These packages are shipped with Distribution: unstable and thus might have a too low pin to be upgraded to automatically. One can fix that by manually selecting the packages, or adjusting the pin priority. One example is given in the comment section below, copied here:

Package: *
Pin: origin download.opensuse.org
Pin-Priority: 950

in /etc/apt/preferences

Older sets

Note that older sets (plasma521, apps2012 and apps2008) don’t support all the different variants and will disappear soon.)

Enjoy.

47 Responses

  1. Thomas Florek says:

    Many thanks to you and the whole team for bringing current KDE/Plasma into Debian.
    Greetings, Tom

  2. Bernhard says:

    Hello, I just came across this blog and like the idea of running a current version of plasma on top of debian stable.

    The apt update is looking good, but dist-upgrade is not showing any updates. What am I missing?

    sudo apt update
    OK:5 https://download.opensuse.org/repositories/home:/npreining:/debian-kde:/other-deps/Debian_11 ./ InRelease
    OK:7 https://download.opensuse.org/repositories/home:/npreining:/debian-kde:/frameworks/Debian_11 ./ InRelease
    OK:8 https://download.opensuse.org/repositories/home:/npreining:/debian-kde:/plasma522/Debian_11 ./ InRelease
    OK:9 https://download.opensuse.org/repositories/home:/npreining:/debian-kde:/apps2108/Debian_11 ./ InRelease
    OK:11 https://download.opensuse.org/repositories/home:/npreining:/debian-kde:/other/Debian_11 ./ InRelease

    sudo apt dist-upgrade
    Paketlisten werden gelesen… Fertig
    Abhängigkeitsbaum wird aufgebaut… Fertig
    Statusinformationen werden eingelesen… Fertig
    Paketaktualisierung (Upgrade) wird berechnet… Fertig
    0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.

  3. Manfred Tremmel says:

    Great work, thanks a lot!

  4. Moltke says:

    I’m getting this
    > the following packages will be REMOVED:
    kde-cli-tools kde-plasma-desktop kinfocenter kscreen plasma-desktop plasma-workspace-wayland powerdevil sddm-theme-breeze sddm-theme-debian-breeze

    >apt-cache policy kde-plasma-desktop
    kde-plasma-desktop:
    Installed: 5:111
    Candidate: 5:111
    Version Table:
    *** 5:111 500
    500 http://deb.debian.org/debian bullseye/main amd64 Packages
    100 /var/lib/dpkg/status
    > apt-cache policy plasma-desktop
    plasma-desktop:
    Installed: 4:5.21.5-1~np1
    Candidate: 4:5.22.4-1~np2
    Version Table:
    4:5.22.4-1~np2 500
    500 https://download.opensuse.org/repositories/home:/npreining:/debian-kde:/plasma522/Debian_11 ./ Packages
    *** 4:5.21.5-1~np1 100
    100 /var/lib/dpkg/status
    4:5.20.5-4 500
    500 http://deb.debian.org/debian bullseye/main amd64 Packages
    I tried updating then reinstalling kde-plasma-desktop but that didn’t work.
    Am I missing something here?
    Thanks for any help in advance.

  5. Moltke says:

    Just wanted to say that I figured it out, and was finally able to update from 5.21.5 to 5.22.4 🙂

  6. Bolko says:

    The launcher kickerdash doesn`t work correctly, beacuase I cannot change to another launcher like kicker or kickoff afterwards anymore. How can I change the launcher from a terminal if rightklick on startbutton doesn`t work anymore?

    • I cannot understand what your problem is. Could you please be more specific in your explanations?

      • Bolko says:

        Rightclick on Startbutton, “show alternatives”, There are 3 Optione:
        1. “Application Launcher” = kickoff launcher
        2. ‘Application Dashboard’ = kickerdash launcher
        3. “Application Menu” = kicker launcher
        I choose Nr.2 but I doesn’t like it, so I wantet to switch back, so again rightclick on start button, “show alternatives”, but nothing happens, the 3 options arent shown anymore and switching is not possible..

        That is not your fault. It is a bug in the kickerdash-launcher., I think

  7. Peje says:

    I get a lot of file size errors upgrading debian unstable:
    E: Failed to fetch https://ftp.gwdg.de/pub/opensuse/repositories/home:/npreining:/debian-kde:/plasma522/Debian_Unstable/amd64/plasma-disks_5.22.4-1~np1_amd64.deb File has unexpected size (108400 != 108468). Mirror sync in progress? [IP: 134.76.12.6 443]
    Hashes of expected file:
    – SHA256:bdcc5a77baa35a68a49c96515c1d490283201b8c839aea7ea6ce8f31846306ad
    – SHA1:e27b19581b9562797ebb3f1a82f33fb37cd109ea [weak]
    – MD5Sum:3de00a7e13b5c754aa751115e5cfa273 [weak]
    – Filesize:108468 [weak]
    E: Failed to fetch https://ftp.gwdg.de/pub/opensuse/repositories/home:/npreining:/debian-kde:/plasma522/Debian_Unstable/amd64/plasma-pa_5.22.4-1~np1_amd64.deb File has unexpected size (209044 != 209420). Mirror sync in progress? [IP: 134.76.12.6 443]
    Hashes of expected file:
    – SHA256:4177afac1fd7cee8104d45124cc71978b6d20328642b827ba798cfe2533d1e40
    – SHA1:2cb9e9856bcae81fb34dcbf9904e886d3a7f433f [weak]
    – MD5Sum:ff02abc7318243d3881fbc3857a24480 [weak]
    – Filesize:209420 [weak]
    E: Failed to fetch https://ftp.gwdg.de/pub/opensuse/repositories/home:/npreining:/debian-kde:/plasma522/Debian_Unstable/amd64/polkit-kde-agent-1_5.22.4-1~np1_amd64.deb File has unexpected size (57392 != 57424). Mirror sync in progress? [IP: 134.76.12.6 443]
    Hashes of expected file:
    – SHA256:34cfae32ce6942282e3826e3008411d78005f3441386ea61d88533343145eec0
    – SHA1:a89218b1416314c87ab13ab8f8a8c41cdf3b5f16 [weak]
    – MD5Sum:2b356b4afd4d70d24d5487761cd78e45 [weak]
    – Filesize:57424 [weak]

  8. Anonymous says:

    This might already be known but digikam 4:7.3.0-1~np1 fails to load.

    digikam: symbol lookup error: /usr/lib/digikam/libdigikamgui.so.7.3.0: undefined symbol: _ZN2cv3dnn14dnn4_v202011173NetC1Ev

  9. Thomas Florek says:

    Confirmed, in unstable.
    Showfoto works.

  10. Concerning digikam: the dnn module of OpenCV had *two* incompatible API changes when going from 4.5.0 to 4.5.1 to 4.5.2. Not good.

    I kicked off a rebuild, but the OBS servers still have the old OpenCV version and not the one from testing. So I need to wait more and start another rebuild … what a pain.

    • THere was a bug in the OBS setup that has been fixed, and the packages are now again as expected and working.

      • Thomas Florek says:

        Thanks, Norbert, confirmed, digikam is okay again.
        System is working flawlessly with the recently updated packages.

  11. Jonathan Spark says:

    Hi Norbert. Great work on this package repo and great talk on the state of KDE/Plasma in Debian at Debconf!
    I’ve recently switched from openSUSE to Debian and am not clear on whether this OBS repo should be considered a robust addition to a Bullseye install or if it is something more for trying new Plasma versions in an ad-hoc manner. Can you give some guidance here?
    Many thanks
    Jonathan.

    • Welcome in Debian! Your question is good, and not easy to answer. So I will continue as long as possible (a Qt version bump will stop this) to provide packages of the latest Plasma/Gears/Frameworks. I myself am running these packages, and several people are using them since long time on (formerly) testing and now bullseye. So they are definitely usable. Still, you might encounter problems due to whatever reasons, that need intervention. If you are not comfortable fixing some dependency problems using apt/aptitude/dpkg at times, it might be better to stay with the packages in Debian proper.

      • Jonathan Spark says:

        Very interesting, thank you. I’m not averse to tackling some dependency issues when needed, as I have had to do a few times on openSUSE Tumbleweed when adding OBS repositories. Looks like I have a decision to make!

        Thanks, Norbert. I appreciate your candid and detailed reply.

      • Roy Shapiro says:

        And… I just needed to perform exactly such an intervention.
        For some reason plasma-workspace marked as 4:5.22.5-1~np3 refused to upgrade from the one marked as 4:5.22.5-1~np1.
        As it turned out upon running ‘sudo apt upgrade plasma-workspace’ manually, there seemingly was a “broken” package, “libqalculate21 : depends on: libqalculate21-data” (which “can not be installed”).
        Perplexed, I tried “sudo apt –dry-run remove libqualculate21” just to see what that will entail, and surprisingly, it showed that it will autoinstall both libqualculate22 and upgrade the whole plasma-workspace successfully if ran without –dry-run, which is exactly what running “sudo apt remove libqalculate21” successfully did.
        Maybe there can be some trigger instituted to remove \ upgrade libqalculate21 to libqalculate22 automatically? Or is it just a local hitch on my system?
        Anyway, thank you so much for all your hard work!
        Running latest Plasma on Debian Stable was a dream that, thanks to you, came true!

        • Yes, apt only very unwillingly removes packages. And since it does not know the relation between libqalculate21 and libqalculate22, even more. Then, you might have set libqalculate21 to “manually installed”, which makes apt even more resistent 😉 I deselected it in aptitude and selected the correct versions manually, that helped.

          Good that it worked at the end.

          • Roy Shapiro says:

            Yes, as far as I remember / noticed, it was marked as manually installed (or, rather, apt didn’t state that it was installed automatically as it usually does) for whatever reason, although I did not, in fact, installed it manually. Likely it was pulled as a dependency of something that I did install manually and marked as such. It seems to happen sometimes.

  12. Jose A says:

    Hi Nolbert.
    First of all, thanks a lot for yours efforts! The best desktop for the best distribution, as it should be.
    I have a problem trying to open the virtualkeyboard module:

    kcmshell5 kcm_virtualkeyboard

    “kcm_virtualkeyboard” should not be loaded.
    Could not find module ‘kcm_virtualkeyboard’. See kcmshell5 –list for the full list of modules.

    But it is in the list of modules and I found on the system at /usr/lib/x86_64-linux-gnu/qt5/plugins/kcms/kcm_virtualkeyboard.so and /usr/share/kpackage/kcms/kcm_virtualkeyboard/contents/ui/main.qml

    • Indeed, that is interesting. The virtual keyboard also doesn’t show up in the settings application. I have no idea …

    • Jonathan Spark says:

      I think this is because the virtual keyboard module is Wayland only. Are you using Plasma on X11 perhaps?

  13. Jose A says:

    Yes, I have installed plasma-workspace-wayland and the module opens! However, no virtual keyboard is listed. Luckily I found miliit-keyboard available from Debian Salsa (Qt/KDE team) and after I compiled it, works finally!

  14. vivantart says:

    Hello, Norbert! There is something wrong with kwin rendering when I update from 5.20 (Bullseye) to 5.22. The Krunner, for exemple, have a darker background like a “border” when it’s showing and corners with white artifacts. The “application name” from the icon on Latte dock is showing like this too. My “Minimal Menu” grid launcher appears to be inside this darker background too. If I change to Xrender instead OpenGL 2.0 or 3.1 everything looks fine. What could it be? It’s an Intel Graphics UHD 630 from i5 10400T. I could send you some screenshots if you want to…

    By the way, thank you for the great work!

    • vivantart says:

      Norbert, I found out it’s really a bug.
      Like this: https://www.reddit.com/r/kde/comments/oeyyts/plasma_panel_shadow_issues/

      It affects tooltips and pontual stuff (dialog, osd, etc.) I don’t know yet why Manjaro with 5.22 doesn’t have this shadows issue. I tried to clean cache as mentioned on bug lists from kde but it didn’t work.

      • Indeed, Wayland. Sorry, I don’t do wayland, why should I pester myself with a half-baked system that is far from production, when X11 works perfectly 😉
        So, good that you found it, and it will probably be fixed at some point in the future, nothing I can do about.
        I suggest using X11.

        • vivantart says:

          Well… The fact is I’m not using wayland at all. I’ll stick with X11 until Wayland works properly.

  15. Vivantart says:

    Norbert, after the last update, that problem is gone. Now, only the problem of the well-known white corners (“korners”, as people have said) remains. Hopefully 5.23 and the Breeze enhancement can fix this soon. I should mention that your last latte-dock package broke it and Latte keeps crashing, so I updated using unstable branch to 0.10.2 version and that fixed it.

    • Thanks for the report. Concerning the breeze case, I guess this is still missing wayland support, and it will get better over time.

      Concerning latte-dock, indeed, the version I had was not compatible with frameworks 5.86, I have updated the OBS build to the latest version. Thanks for the report.

  16. Anonymous says:

    Just encountered that kimageformat-plugins is held back with latest update:

    sudo apt install kimageformat-plugins

    The following packages have unmet dependencies:
    kimageformat-plugins : Depends: libavif9 (>= 0.8.4) but it is not installable
    E: Unable to correct problems, you have held broken packages.

    Debian has newer package only: libavif12

    • Rebuilds are currently hanging, and I don’t know why. Testing and Stable rebuilds work, but Unstable is hanging. I kicked off a complete rebuild of the 5.86 packages that hopefully does it …

  17. Michael says:

    Hi, thank you so much for your work bringing updated KDE to Debian. This is my dream come true of a perfect system – Debian Stable with backport kernel + latest KDE Plasma.

    Will Plasma 5.23 be delivered through the same repositories you are providing for Plasma 5.22 once it’s released?

    • Yes, I plan to make Plasma 5.23 and later versions available via the OBS repositories in the same way as I did for previous versions. Only if the requirements for Plasma cannot be satisfied in Debian/stable (like a too low Qt version), this will come to an end.

  1. 2021/09/21

    […] to your apt sources (replacing DISTRIBUTION with one of Debian_11 (for Bullseye), Debian_Testing, or Debian_Unstable). For further details see this blog. […]

Leave a Reply

Your email address will not be published.

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>