KDE/Plasma 5.23 “25th Anniversary Edition” for Debian

In the last week, KDE released version 5.23 – 25th Anniversary Edition – of the Plasma desktop with the usual long list of updates and improvements. This release celebrates 25 years of KDE, and Plasma 5.23.0 was released right on the day 25 years ago Matthias Ettrich sent an email to the de.comp.os.linux.misc newsgroup explaining a project he was working on. And Plasma 5.23 (with the bug fix 5.23.1) is now available for all Debian releases. (And don’t forget KDE Gears/Apps 21.08!)

As usual, I am providing packages via my OBS builds. If you have used my packages till now, then you only need to change the plasma522 line to read plasma523. 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:/plasma523/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/ ./

The sharp eye might have detected also the apps2108 line, yes the KDE Gear suite of packages hgas been updated to 21.08 some time ago and is also available in my OBS builds (and in Debian/experimental).

Uploads to Debian

Plasma 5.23.0 has been uploaded to Debian, and is currently in transition to testing. Due to incorrect/insufficient Break/Depends, currently Debian/testing with the official packages for Plasma are broken. And as it looks this situation will continue for considerable time, considering that kwin is blocked by mesa, which in turn is blocked by llvm-toolchain-12, which has quite some RC bugs preventing it from transitioning. What a bad coincidence.

KDE Gears 21.08 are all in Debian Unstable and Testing, so the repositories here are mostly for users of Debian Bullseye (stable).

Krita beta

Krita has released the second beta of Krita 5.0, and this is available from the krita-beta repository, but only for amd64 architectures. Just add

deb https://download.opensuse.org/repositories/home:/npreining:/debian-kde:/krita-beta/DISTRIBUTION/ ./

Enjoy the new Plasma!

109 Responses

  1. Dmitriy says:

    Thank you, Norbert!

  2. Luc says:

    Thank you, Norbert. Both for the work & content as well as for the communication around it. It helps enourmously!

  3. usman says:

    Thanks. Walking through the freeze season for the first time, this blog really help me to understand the situation.
    – unstable user since January –

  4. Jérôme says:

    Thanks to you, I’m back with KDE after leaving KDE 4.0 and I’m pleased to see it so polish now.

  5. Jonathan Spark says:

    Many thanks for your work here. I decided to take the plunge and go 5.23 on my Bullseye. Works and looks great so far.

    • Hi. Great work. How long and frequent do you plan to update this repo for Plasma 5.23 on Bullseye? Do you add minor point releases? I am interested and evaluating to use your repo for the Neptune Distro which is based upon Debian to provide the newer Plasma version to our users.

  6. Ralf says:

    Thanks, Norbert, for all your work on packaging KDE! Gone are the days where it takes many months from a KDE release to a first upload into Debian. 🙂

    > Due to incorrect/insufficient Break/Depends, currently Debian/testing with the official packages for Plasma are broken.

    This had me worried since I was unsure what I have to do to avoid breaking my system (other than just not installing any updates), but it seems there is an easy workaround. So for anyone who wants to know more, here are the details: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996761

  7. Tomasz says:

    Thanks for the update. Overall it works quite good, I have just two smaller issues with my setup with Nvidia drivers and the desktop effects. First, the “blur” effect, which leads to artefacts on the screen, for example if you let the Yakuake screen slide in and out. And second with the “magic lamp” effect for minimizing windows which does not work at all. I disabled the two effects and the rest seems to be ok. Thanks for your work.

  8. Thomas Florek says:

    @Tomasz,
    regarding desktop effects in current plasma releases, look pls at the discussion
    https://bugs.kde.org/show_bug.cgi?id=443410

    • Tomasz says:

      Thanks Thomas, but the discussion you linked is about the cube effect. I don´t think it´s related. I also use a whole bunch of virtual desktops and activities but I use the “raster” effect instead of the cube. Sad nevertheless that features are being cut down for those who are used to use them.

  9. Shmerl says:

    Some recent problem with upgrading:

    The following packages have unmet dependencies:
    kimageformat-plugins : Depends: libavif9 (>= 0.8.4) but it is not installable

    Currently testing / unstable have libavif12, not llibavif9.

    • Thanks, I’ll kick of a rebuild. It is not that important, the version in Debian is fine. Here I only add jpeg2000 support.

    • Thomas Florek says:

      @shmerl, here on sid:
      # LANG=C apt depends kimageformat-plugins
      kimageformat-plugins
      Depends: libavif12 (>= 0.9.2)

  10. Btw. latte dock does not want to install on Debian_11 because of size mismatch in the package

    E: Failed to fetch https://ftp.gwdg.de/pub/opensuse/repositories/home:/npreining:/debian-kde:/other/Debian_11/amd64/latte-dock_0.10.2-1~1_amd64.deb File has unexpected size (1309744 != 1310372). Mirror sync in progress? [IP: 2001:638:60f:110::1:2 443]

  11. Another weird issue. Kdenlive searches by default for the wrong mlt path /usr/share/mlt instead of /usr/share/mlt-7 and I only could bring it to work with providong that path via command line.
    With that I get kdenlive started but it does not find any HD or FullHD profiles only some 4k DCI ones. Not sure whats wrong here and if that can be addressed with an update of some sorts

    • Hmm, this is strange. I cannot see any of this on my system. I not even know what mlt is doing, but in the settings of kdenlive there the “MLT Profiles folder” and it points to “/usr/share/mlt-7/profiles”, and I see a lot of 4k etc profiles.

  12. Shadow says:

    Hi, Norbert.
    I updated my debian testing with KDE 5.21 today (october 25tj) and now my desktop no longer loads. It seems there are a several KDE 5.23 packages installed mixed with 5.21, and as you said, fixes will take long.
    My question is, can I use your repos to install 5.23 succesfully? Or at least go back to 5.21?
    What command should I type to update all Kde packages?
    Thank you!

    • Hi
      you have two options, one is to downgrade libkdecoration5v5, the solution that brings you to 5.21 and stays completely in Debian.
      The other option is to activate my repositories and install the missing 5.23 packages from there.
      Both are fine.

      • Shadow says:

        Thanks. It loaded correctly now, but I’m seeing some differences: Bluetooth is enabled (when I had it disabled), I cannot connect to any Wifi anymore (journalxtl says: “no secrets: No agents were availablew for this request. Failed for conncetion ‘{SSID_NAME}'”

        I see 8-9 packages installed from 5.23, like:
        kde-config-gtk-style,
        kde-config-sddm,
        kde-config-updates,
        kde-style-breeze,
        kde-style-oxygen-qt5,
        libkdecorations2private9
        and polkit-kde-agent-1

        You suggest to downgrade those packages to 5.21 or install kde 5.23 form your repos?

        Thank you!

      • Shadow says:

        This is the first time using that kind of DEB source URL. If I wanted to APT-pinning, how would I do that with your repo:
        “deb https://download.opensuse.org/repositories/home:/npreining:/debian-kde:/plasma523/Debian_Testing/ ./”
        What’s its name in order to use it in “/etc/apt/preferences”?

        Thank you for your work.

        • Shadow says:

          Ok, i learned a bit more about apt pinning and I could pin according to “origin URL” with:

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

          Now I have KDE 5.23.1 from your repos and Wifi worked again.

  13. Mac says:

    Hi,

    I am having issues with upgrading the following packages since maybe two days ago:
    akregator
    kaddressbook
    kdepim-runtime
    kmail
    knotes
    korganizer
    libkf5kmanagesieve5
    libkf5mailtransport5

    They all fail with a similar error. Here is the one triggered by akregator:
    E: Failed to fetch https://provo-mirror.opensuse.org/repositories/home:/npreining:/debian-kde:/apps2108/Debian_11/amd64/akregator_21.08.2-1~np1_amd64.deb File has unexpected size (2499456 != 2499572). Mirror sync in progress? [IP: 2a07:de40:401::70 443]
    Hashes of expected file:
    – SHA256:46273eb6e3d94bb0cc6ec241ff70db65fb7227f0f045d1b0dee6b2a2d62c1580
    – SHA1:5d54f7e5e47e511db2acbb617b95670946480f01 [weak]
    – MD5Sum:b9e3452137ed2cbc3b649111c5bbda20 [weak]
    – Filesize:2499572 [weak]

    Thanks

  14. Fernando Sousa says:

    Not all heroes wear caps! Thank you so much!

  15. Kostiantyn says:

    Hey
    There’s an error in this article, “obs-npreining-kde.list” file should be in “/etc/apt/sources.list.d/” folder, not in “/etc/apt/sources.lists.d/”

  16. Jose Javier says:

    Debian Testing working great, thanks and regards.

  17. Shmerl says:

    Hi Norbert!

    I was just installing Debian with KDE and noticed that it still defaults to maui theme for sddm instead of breeze which looks much nicer and fits Plasma defaults.

    I even filed a bug about it a while ago: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949340

    Can you please help fixing it. Not a deal breaker but would improve Debian KDE experience.

    Thanks!

  18. Luc says:

    I just noticed you have KDE-Frameworks: 5.87 shown in the screenshot above. After upgrade I have 5.86. Did I do something wrong?

    • Thomas Florek says:

      @Luc, OBS repos not enabled?

      • Luc says:

        thanks Thomas, I oversaw I enabled Testing in my sources.list. Now set to Unstable

        • Luc says:

          I corrected the repo, and pinned:

          Package: *
          Pin: origin downloadcontent.opensuse.org
          Pin-Priority: 900

          But how do I make aptitude to pick the NP repo?

          aptitude install plasma-framework -t sid

          does list only the 5.86 versions, not the 5.87 ones .

  19. Thomas Florek says:

    # LANG=C apt policy plasma-framework
    plasma-framework:
    Installed: 5.87.0-1~np2
    Candidate: 5.87.0-1~np2
    Version table:
    *** 5.87.0-1~np2 500
    500 https://download.opensuse.org/repositories/home:/npreining:/debian-kde:/frameworks/Debian_Unstable ./ Packages
    100 /var/lib/dpkg/status
    5.86.0-1 500
    500 https://deb.debian.org/debian testing/main amd64 Packages
    500 https://deb.debian.org/debian unstable/main amd64 Packages

  20. Manfred Tremmel says:

    KDE Plasma 5.23.3 really works great here on wayland, but there’s one thing missing: screen sharing/recording. I’ve installed all the needed packages (pipewire, xdg-desktop-portal and xdg-desktop-portal-kde), everything is running, but OBS and Chrome aren’t able to access screens or windows using pipewire.

    In /var/log/user.log there are entries like this:
    Nov 13 18:09:14 thinkpad org.freedesktop.impl.portal.desktop.kde[2808]: xdp-kde-screencast: zkde_screencast_unstable_v1 does not seem to be available

    As far as I’ve seen, the needed stuff should have been included by this merge request https://invent.kde.org/libraries/plasma-wayland-protocols/-/merge_requests/1/

  21. Manfred Tremmel says:

    I’ve just received the framework updates (5:5.87.0-1~np2 -> 5:5.88.0-1~np1), on bullseye, now the infocenter (kinfocenter) and the settings (systemsettings5) crash on startup with segmentation fault. The system monitor (plasma-systemmonitor) when you try to show the about information.
    X11 or wayland makes no difference.

    Is it a known problem?

    • Vivantart says:

      +1

    • Sorry, I was halfway through the update when I feel asleep. Not all packages are updated, and that is I guess the problem. Will try tomorrow…

      • Luc says:

        Have a nice sleep, Norbert! Thanks for your work.

      • Manfred Tremmel says:

        This can happen, and adding your repository is our own risk. Thanks a lot for doing this great job (not ironic, I’ve packaged 12 years for openSUSE/packman, I know how much work is needed to keep so many packages up to date). I’m sure it will be fixed soon and inbetween I’ll downgrade the package to 5.87.0 on my working computer (always good to have a computer with cachted packages ;-)) and disable the repository.
        For testing my old Notebook will keep in think with the repo.

      • JohnDoe says:

        I haven’t tested all KCMs, but at least kcm_landingpage, kcm_colors and kcm_fonts are crashing during their QML UI initialization (both when opening through systemsettings5 or via kcmshell5), others like kcm_lookandfeel or kcm_style at least load fine (haven’t tested changing any settings though). The crashing ones all crash with the same backtrace deep in the bowels of libQt5Qml when dereferencing a NULL pointer. Rebuilding plasma-workspace (because the crashing KCMs are from this package) and systemsettings (because it’s the only thing not KF5 or Qt5 in the backtrace) against the updated KF5 libraries didn’t change anything, so I don’t think this is due to an incomplete update but rather a genuine regression somewhere in KF5.

        The exact same crash seems to happen on Debian unstable too BTW: https://bugs.kde.org/show_bug.cgi?id=445453

      • JohnDoe says:

        Update to my other comment: I was able narrow it down to qml-module-org-kde-qqc2desktopstyle. If I downgrade that package to the previous version (5.87.0-1~np2) then the crashing kcm modules start working again.

  22. Luc says:

    frameworks 5.88 was installed this moring. Systemsetting crashes See below for some debug info.

    luc@wolder:~/tmp_latte$ /usr/bin/systemsettings5
    file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/RefreshableScrollView.qml:175:13: QML Binding: Not restoring previous value because restoreMode has not been set.
    This behavior is deprecated.
    You have to import QtQml 2.15 after any QtQuick imports and set
    the restoreMode of the binding to fix this warning.
    In Qt = 6.0 the default is Binding.RestoreBindingOrValue.

    file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/RefreshableScrollView.qml:175:13: QML Binding: Not restoring previous value because restoreMode has not been set.
    This behavior is deprecated.
    You have to import QtQml 2.15 after any QtQuick imports and set
    the restoreMode of the binding to fix this warning.
    In Qt = 6.0 the default is Binding.RestoreBindingOrValue.

    file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/RefreshableScrollView.qml:175:13: QML Binding: Not restoring previous value because restoreMode has not been set.
    This behavior is deprecated.
    You have to import QtQml 2.15 after any QtQuick imports and set
    the restoreMode of the binding to fix this warning.
    In Qt = 6.0 the default is Binding.RestoreBindingOrValue.

    file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/RefreshableScrollView.qml:175:13: QML Binding: Not restoring previous value because restoreMode has not been set.
    This behavior is deprecated.
    You have to import QtQml 2.15 after any QtQuick imports and set
    the restoreMode of the binding to fix this warning.
    In Qt = 6.0 the default is Binding.RestoreBindingOrValue.

    QQmlEngine::setContextForObject(): Object already has a QQmlContext
    KCrash: crashing… crashRecursionCounter = 2
    KCrash: Application Name = systemsettings5 path = /usr/bin pid = 4176
    KCrash: Arguments: /usr/bin/systemsettings5
    KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi

    [2]+ Gepauzeerd /usr/bin/systemsettings5
    luc@wolder:~/tmp_latte$ Unable to find file for pid 4140 expected at “kcrash-metadata/4140.ini”
    QSocketNotifier: Invalid socket 8 and type ‘Read’, disabling…
    QSocketNotifier: Invalid socket 10 and type ‘Read’, disabling…
    QSocketNotifier: Invalid socket 14 and type ‘Read’, disabling…
    Unable to find file for pid 4176 expected at “kcrash-metadata/4176.ini”
    QSocketNotifier: Invalid socket 8 and type ‘Read’, disabling…
    QSocketNotifier: Invalid socket 10 and type ‘Read’, disabling…
    QSocketNotifier: Invalid socket 14 and type ‘Read’, disabling…

  23. Luc says:

    herewith DRKonqi debug info:

    Application: Systeeminstellingen (systemsettings5), signal: Segmentation fault

    [KCrash Handler]
    #4 0x00007f371be9a7c2 in QV4::QQmlTypeWrapper::virtualInstanceOf(QV4::Object const*, QV4::Value const&) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
    #5 0x00007f371bd882b7 in QV4::Runtime::Instanceof::call(QV4::ExecutionEngine*, QV4::Value const&, QV4::Value const&) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
    #6 0x00007f371bd74295 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
    #7 0x00007f371bd78cf7 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
    #8 0x00007f371bd1456d in QV4::Function::call(QV4::Value const*, QV4::Value const*, int, QV4::ExecutionContext const*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
    #9 0x00007f371be8b3c5 in QQmlJavaScriptExpression::evaluate(QV4::CallData*, bool*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
    #10 0x00007f371be904c4 in QQmlBinding::evaluate(bool*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
    #11 0x00007f371be94367 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
    #12 0x00007f371be92144 in QQmlBinding::update(QFlags) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
    #13 0x00007f371be9e7e3 in QQmlObjectCreator::finalize(QQmlInstantiationInterrupt&) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
    #14 0x00007f371be3386c in QQmlComponentPrivate::complete(QQmlEnginePrivate*, QQmlComponentPrivate::ConstructionState*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
    #15 0x00007f371be35afe in QQmlComponentPrivate::completeCreate() () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
    #16 0x00007f371be36bf0 in QQmlComponent::createObject(QQmlV4Function*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
    #17 0x00007f371be37693 in QQmlComponent::qt_metacall(QMetaObject::Call, int, void**) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
    #18 0x00007f371be6f6fd in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
    #19 0x00007f371bd5aba6 in QV4::QObjectMethod::callInternal(QV4::Value const*, QV4::Value const*, int) const () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
    #20 0x00007f371bd761cf in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
    #21 0x00007f371bd78cf7 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
    #22 0x00007f371bd1456d in QV4::Function::call(QV4::Value const*, QV4::Value const*, int, QV4::ExecutionContext const*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
    #23 0x00007f371be8b3c5 in QQmlJavaScriptExpression::evaluate(QV4::CallData*, bool*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
    #24 0x00007f371be3f58b in QQmlBoundSignalExpression::evaluate(void**) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
    #25 0x00007f371be3fa70 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
    #26 0x00007f371be6f1ad in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
    #27 0x00007f371cfd34dd in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
    #28 0x00007f371bee6cf3 in QQmlTimer::qt_metacall(QMetaObject::Call, int, void**) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
    #29 0x00007f371be6f6fd in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
    #30 0x00007f371bd583ce in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
    #31 0x00007f371bd5a95a in QV4::QObjectMethod::callInternal(QV4::Value const*, QV4::Value const*, int) const () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
    #32 0x00007f371bd761cf in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
    #33 0x00007f371bd78cf7 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
    #34 0x00007f371bd1456d in QV4::Function::call(QV4::Value const*, QV4::Value const*, int, QV4::ExecutionContext const*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
    #35 0x00007f371be8b3c5 in QQmlJavaScriptExpression::evaluate(QV4::CallData*, bool*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
    #36 0x00007f371be3f58b in QQmlBoundSignalExpression::evaluate(void**) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
    #37 0x00007f371be3fa70 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
    #38 0x00007f371be6f1ad in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
    #39 0x00007f371cfd34dd in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
    #40 0x00007f371be9ece8 in QQmlObjectCreator::finalize(QQmlInstantiationInterrupt&) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
    #41 0x00007f371be3969c in QQmlIncubatorPrivate::incubate(QQmlInstantiationInterrupt&) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
    #42 0x00007f371be39c27 in QQmlEnginePrivate::incubate(QQmlIncubator&, QQmlContextData*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
    #43 0x00007f371be34c52 in QQmlComponent::create(QQmlIncubator&, QQmlContext*, QQmlContext*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
    #44 0x00007f371c5895da in KDeclarative::QmlObject::completeInitialization(QHash const&) () from /lib/x86_64-linux-gnu/libKF5Declarative.so.5
    #45 0x00007f371e51b476 in KQuickAddons::ConfigModule::mainUi() () from /lib/x86_64-linux-gnu/libKF5QuickAddons.so.5
    #46 0x00007f371e62dab9 in KCModuleLoader::loadModule(KCModuleInfo const&, KCModuleLoader::ErrorReporting, QWidget*, QStringList const&) () from /lib/x86_64-linux-gnu/libKF5KCMUtils.so.5
    #47 0x00007f371e638b45 in ?? () from /lib/x86_64-linux-gnu/libKF5KCMUtils.so.5
    #48 0x00007f371e639808 in KCModuleProxy::realModule() const () from /lib/x86_64-linux-gnu/libKF5KCMUtils.so.5
    #49 0x00007f371e676f92 in ModuleView::updatePageIconHeader(KPageWidgetItem*, bool) () from /lib/x86_64-linux-gnu/libsystemsettingsview.so.3
    #50 0x00007f371e67844c in ModuleView::addModule(KCModuleInfo*, QStringList const&) () from /lib/x86_64-linux-gnu/libsystemsettingsview.so.3
    #51 0x00007f371405195f in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/systemsettingsview/systemsettings_sidebar_mode.so
    #52 0x00007f3714051db9 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/systemsettingsview/systemsettings_sidebar_mode.so
    #53 0x0000557e7dda54b5 in ?? ()
    #54 0x0000557e7dda81df in ?? ()
    #55 0x00007f371cfc978c in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
    #56 0x00007f371e5d6557 in KXmlGuiWindow::event(QEvent*) () from /lib/x86_64-linux-gnu/libKF5XmlGui.so.5
    #57 0x00007f371db9674f in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
    #58 0x00007f371cf9ce9a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
    #59 0x00007f371cf9fe11 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
    #60 0x00007f371cff5413 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
    #61 0x00007f371aabac7b in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
    #62 0x00007f371aabaf28 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
    #63 0x00007f371aabafdf in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
    #64 0x00007f371cff4a90 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
    #65 0x00007f371cf9b8db in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
    #66 0x00007f371cfa3b10 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
    #67 0x0000557e7dda1e30 in ?? ()
    #68 0x00007f371c9407ed in __libc_start_main (main=0x557e7dda15f0, argc=1, argv=0x7ffccb00b378, init=, fini=, rtld_fini=, stack_end=0x7ffccb00b368) at ../csu/libc-start.c:332
    #69 0x0000557e7dda2b5a in ?? ()
    [Inferior 1 (process 4490) detached]

  24. Sedat says:

    Confirmed here on Debian/unstable AMD64: kinfocenter crashes after KF v5.88.0 upgrade.

    See KDE Bug #445430 “[systemsettings] [Bug 445430] kinfocenter crash after app start”

    [1] https://www.mail-archive.com/kde-bugs-dist@kde.org/msg621843.html
    [2] https://www.mail-archive.com/kde-bugs-dist@kde.org/msg621944.html

  25. Sedat says:

    These packages are missing:

    root# git diff KDE/KF-5-87-0 KDE/KF-5-88-0 | egrep ‘^[+|-]’ | sort
    — a/KDE/KF-5-87-0
    +++ b/KDE/KF-5-88-0
    -kimageformat-plugins
    -ktexteditor-data
    -ktexteditor-katepart
    -libkf5contacts5:amd64
    -libkf5contacts-data
    -libkf5i18n5:amd64
    -libkf5i18n-data
    -libkf5i18n-dev:amd64
    -libkf5i18n-doc
    -libkf5texteditor5:amd64
    -libkf5texteditor-bin

  26. Andreas Ferber says:

    Just a heads up: the latest framework update 5.88 breaks the breeze-dark icon theme due to a bug in the cmake setup that was introduced upstream two weeks ago. I’ve already reported it: https://bugs.kde.org/show_bug.cgi?id=445489

    To fix it for the Debian package until it gets fixed upstream you could add a local patch reverting the two commits mentioned in the bug report that caused the bug.

    • Thanks for the pointer, but something is still strange. The latest set of packages (1~np2) reverts the two commits, but the icons on my desktop now look very different. Need to investigate.

      • Andreas Ferber says:

        Yeah, I think the commit 1b92cfc450f6ab6b72ed9ef69c052e4624e5a040 (and maybe bc18bf8e28e1110d752f94412f2314c7b57f9fdb) needs to be reverted too. The guy making those changes doesn’t seem to have understood how icon theme inheritance works, in particular that if an icon doesn’t exist in the current theme in the requested size then it first looks for a different size of the icon in the same theme, and only if that still didn’t find anything is the parent theme checked. So by removing those “duplicates” he actually broke all icons where only certain sizes had dark-mode specific versions, and then made things even worse with the later attempt to fix it.

  27. Sedat says:

    After recent KF v5.88.0 changes/upgrades:

    $ LC_ALL=C date –utc
    Sun Nov 14 15:28:26 UTC 2021

    I am able to start as user via (in konsole):

    user$ sudo /usr/bin/systemsettings5
    user$ sudo /usr/bin/kinfocenter

  28. Sedat says:

    Upgraded all reported missing packages… still cannot start from K-Start via icon/symbol.
    Maybe restart KDE/Plasma/Wayland…

  29. Sedat says:

    Downgrade…

    dpkg -i /var/cache/apt/archives/qml-module-org-kde-kirigami2_5.86.0-1_amd64.deb /var/cache/apt/archives/libkf5kirigami2-5_5.86.0-1_amd64.deb

    …and I can run kinfocenter as user from terminal and k-start.

    One problem seems to be a typo:

    # git diff /usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/RefreshableScrollView.qml.5.86.0-1 /usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/RefreshableScrollView.qml.5.88.0-1~np1
    diff –git a/usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/RefreshableScrollView.qml.5.86.0-1 b/usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/RefreshableScrollView.qml.5.88.0-1~np1
    index c46b518..ab46a48 100644
    — a/usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/RefreshableScrollView.qml.5.86.0-1
    +++ b/usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/RefreshableScrollView.qml.5.88.0-1~np1
    @@ -173,7 +173,7 @@ P.ScrollView {
    }

    Binding {
    – target: root.contentItem
    + target: root.flickableItem
    property: “width”
    value: root.flickableItem.width
    when: root.horizontalScrollBarPolicy == Qt.ScrollBarAlwaysOff

    • Manfred Tremmel says:

      I can confirm this, all current updates installed, then downgraded both packages (in my case, I had qml-module-org-kde-kirigami2_5.87.0-1~np1_amd64.deb and libkf5kirigami2-5_5.87.0-1~np1_amd64.deb in cache), and problems are gone.

  30. Sedat says:

    Unfortunately, some other KF v5.88.0 packages depend on newer kirigami2.

    Problems seems to be qml-module-org-kde-kirigami2 package.
    I was able to use the older version together with the newer libkf5kirigami2-5 by manually copying files/dirs.

  31. Hi everyone
    I cannot answer to all comments here, but 5.88.0-1~np2 should fix all the problems. Sorry for the inconveniences.

    I have them running on my computer and kinfocenter and systemsettings5 runs without any problems.

  32. Sedat says:

    I upgraded to KF version 5.88.0-1~np2.
    Still cannot start kinfocenter.

  33. Luc says:

    starting from commandline I get same behaviour

    luc@wolder:~$ /usr/bin/systemsettings5
    file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/RefreshableScrollView.qml:175:13: QML Binding: Not restoring previous value because restoreMode has not been set.
    This behavior is deprecated.
    You have to import QtQml 2.15 after any QtQuick imports and set
    the restoreMode of the binding to fix this warning.
    In Qt = 6.0 the default is Binding.RestoreBindingOrValue.

    file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/RefreshableScrollView.qml:175:13: QML Binding: Not restoring previous value because restoreMode has not been set.
    This behavior is deprecated.
    You have to import QtQml 2.15 after any QtQuick imports and set
    the restoreMode of the binding to fix this warning.
    In Qt = 6.0 the default is Binding.RestoreBindingOrValue.

    file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/RefreshableScrollView.qml:175:13: QML Binding: Not restoring previous value because restoreMode has not been set.
    This behavior is deprecated.
    You have to import QtQml 2.15 after any QtQuick imports and set
    the restoreMode of the binding to fix this warning.
    In Qt = 6.0 the default is Binding.RestoreBindingOrValue.

    file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/RefreshableScrollView.qml:175:13: QML Binding: Not restoring previous value because restoreMode has not been set.
    This behavior is deprecated.
    You have to import QtQml 2.15 after any QtQuick imports and set
    the restoreMode of the binding to fix this warning.
    In Qt = 6.0 the default is Binding.RestoreBindingOrValue.

    QQmlEngine::setContextForObject(): Object already has a QQmlContext
    KCrash: crashing… crashRecursionCounter = 2
    KCrash: Application Name = systemsettings5 path = /usr/bin pid = 4339
    KCrash: Arguments: /usr/bin/systemsettings5
    KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi

  34. Luc says:

    GDB:

    [Detaching after fork from child process 4630]
    [Detaching after fork from child process 4631]
    [New Thread 0x7fffd7fff640 (LWP 4632)]
    QQmlEngine::setContextForObject(): Object already has a QQmlContext

    Thread 1 “systemsettings5” received signal SIGSEGV, Segmentation fault.
    0x00007ffff57bd7c2 in QV4::QQmlTypeWrapper::virtualInstanceOf(QV4::Object const*, QV4::Value const&) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
    (gdb)

  35. Sedat says:

    Rebooted my Debian/unstable AMD64 system and installed qml-module-org-kde-i18n-localedata:amd64. Nope with systemsettings5 and kinfocenter.

    Some local .config files causing troubles?

    BTW, my chromium bookmarks etc are all gone :-(.

  36. Sedat says:

    root# apt-get install –reinstall -t unstable qml-module-org-kde-qqc2desktopstyle=5.86.0-1 -y –allow-downgrades

    …seems to fix the issue here.

  37. Sedat says:

    I dunno much about kirigami and/or kcm qml* modules but there is a co-relation between

    root# dpkg -L qml-module-org-kde-qqc2desktopstyle | grep kirigami
    /usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kirigami
    /usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kirigami/org.kde.desktop.so

  38. Sedat says:

    I have rebuild qqc2-desktop-style package against new v5.88.0 B-D -dev packages, but kinfocenter still crashes.

  39. qml-module-org-kde-qqc2desktopstyle in version 5.88.0-1~np3 should fix the problem. There were missing dependencies on qml-module-org-kde-sonnet. That also explained why it worked on one of my system where the package was installed.

    • Thomas Florek says:

      Confirmed on my system.
      From history.log:

      Commandline: apt full-upgrade -V
      Install: qml-module-org-kde-sonnet:amd64 (5.88.0-1~np2, automatic)
      Upgrade: qml-module-org-kde-qqc2desktopstyle:amd64 (5.88.0-1~np2, 5.88.0-1~np3)

      Thanks a lot, Norbert

  40. Sedat says:

    OK, qml-module-org-kde-qqc2desktopstyle (5.88.0-1~np3) plus qml-module-org-kde-sonnet:amd64 (5.88.0-1~np2) fixes the problem here.

    My rebuild of qml-module-org-kde-qqc2desktopstyle + qml-module-org-kde-sonnet works fine, too.

  41. Benjamin says:

    HI,
    I am trying to install Kde 5.23 but I cant select it from the login screen, the only thing that shows up is Gnome.

    I had KDE 5.22 working fine, but after a system update it broke. I uninstalled Plasma then reinstalled with Debians repos, worked fine. As soon as I tried 5.23, same problem, no option to select it from the login screen.

    I am on Debian bullseye

    • Hard to debug from here. I have a virtual machine based on bullseye and SDDM as display manager and Plasma shows up. So I cannot help more than advise you to read the log files of the display manager and see if there is something there. Also, do you have all the plasma related packages installed.

      • Benjamin says:

        I installed minimal version of plasma. this is the command that I used to install

        sudo apt install kde-plasma-desktop plasma-nm

        after the install I updated the repositories, issued the update and upgrade commands, did a reboot, and when I logged in to plasma everything still fine. then it said I hade more udates so I installed them and that is when it broke. no more plasma.

        if I do the install plasma command, this is the errors I get.

        sudo apt install kde-plasma-desktop plasma-nm
        Reading package lists… Done
        Building dependency tree… Done
        Reading state information… Done
        plasma-nm is already the newest version (4:5.23.3-1~np1).
        Some packages could not be installed. This may mean that you have
        requested an impossible situation or if you are using the unstable
        distribution that some required packages have not yet been created
        or been moved out of Incoming.
        The following information may help to resolve the situation:

        The following packages have unmet dependencies:
        kde-plasma-desktop : Depends: plasma-workspace (>= 4:5.20.5) but it is not installable
        plasma-desktop : Depends: plasma-workspace (>= 4:5.23~) but it is not installable
        Recommends: kinfocenter (>= 4:5.23~) but it is not installable
        E: Unable to correct problems, you have held broken packages

        I am somewhat a newbie so were can I go to read the log files?

  42. Thomas Florek says:

    @benjamin, please launch and show the output:

    apt policy plasma-workspace
    apt policy kinfocenter
    less /etc/apt/sources.list.d/obs-npreining-kde.list
    apt install kde-plasma-desktop plasma-desktop

  43. Benjamin says:

    @Thomas

    apt policy plasma-workspace
    plasma-workspace:
    Installed: (none)
    Candidate: 4:5.23.3-1~np1
    Version table:
    4:5.23.3-1~np1 500
    500 https://download.opensuse.org/repositories/home:/npreining:/debian-kde:/plasma523/Debian_11 ./ Packages
    4:5.20.5-6 500
    500 http://deb.debian.org/debian bullseye/main amd64 Packages
    100 /var/lib/dpkg/status

    apt policy kinfocenter
    kinfocenter:
    Installed: (none)
    Candidate: 4:5.23.3-1~np1
    Version table:
    4:5.23.3-1~np1 500
    500 https://download.opensuse.org/repositories/home:/npreining:/debian-kde:/plasma523/Debian_11 ./ Packages
    100 /var/lib/dpkg/status
    4:5.20.5-1 500
    500 http://deb.debian.org/debian bullseye/main amd64 Packages

    I have my list named as: /etc/apt/sources.list.d/kde23.list

    # KDE Plasma 5.23

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

    sudo apt install kde-plasma-desktop plasma-desktop
    [sudo] password for benjamin:
    Reading package lists… Done
    Building dependency tree… Done
    Reading state information… Done
    Some packages could not be installed. This may mean that you have
    requested an impossible situation or if you are using the unstable
    distribution that some required packages have not yet been created
    or been moved out of Incoming.
    The following information may help to resolve the situation:

    The following packages have unmet dependencies:
    kde-plasma-desktop : Depends: plasma-workspace (>= 4:5.20.5) but it is not installable
    plasma-desktop : Depends: plasma-workspace (>= 4:5.23~) but it is not installable
    Recommends: kinfocenter (>= 4:5.23~) but it is not installable
    E: Unable to correct problems, you have held broken packages.

    • Thomas Florek says:

      I have a sid (unstable) Debian and you have installed a Debian stable. Our systems are not exactly comparable.
      Please report the results of
      apt install plasma-workspace
      apt install kinfocenter
      Could be unresolved dependencies, because of
      “plasma-workspace (>= 4:5.23~) but it is not installable”,
      “kinfocenter (>= 4:5.23~) but it is not installable”
      OTOH those packages are shown by the policy command.

      • Benjamin says:

        sudo apt install plasma-workspace
        [sudo] password for benjamin:
        Reading package lists… Done
        Building dependency tree… Done
        Reading state information… Done
        Some packages could not be installed. This may mean that you have
        requested an impossible situation or if you are using the unstable
        distribution that some required packages have not yet been created
        or been moved out of Incoming.
        The following information may help to resolve the situation:

        The following packages have unmet dependencies:
        plasma-workspace : Depends: libqalculate22 (>= 3.20.1) but it is not installable
        Recommends: kde-cli-tools (>= 4:5.23~) but it is not going to be installed
        Recommends: ksystemstats (>= 5.23~) but it is not going to be installed
        Recommends: libpam-kwallet5 (>= 5.14) but it is not going to be installed
        Recommends: powerdevil (>= 4:5.14) but it is not going to be installed
        E: Unable to correct problems, you have held broken packages.

        sudo apt install kinfocenter
        Reading package lists… Done
        Building dependency tree… Done
        Reading state information… Done
        Some packages could not be installed. This may mean that you have
        requested an impossible situation or if you are using the unstable
        distribution that some required packages have not yet been created
        or been moved out of Incoming.
        The following information may help to resolve the situation:

        The following packages have unmet dependencies:
        plasma-workspace : Depends: libqalculate22 (>= 3.20.1) but it is not installable
        Recommends: kde-cli-tools (>= 4:5.23~) but it is not going to be installed
        Recommends: ksystemstats (>= 5.23~) but it is not going to be installed
        Recommends: libpam-kwallet5 (>= 5.14) but it is not going to be installed
        Recommends: powerdevil (>= 4:5.14) but it is not going to be installed
        E: Unable to correct problems, you have held broken packages.

  44. m says:

    I am trying to use these packages with bullseye, but I cannot install plasma-workspace because it depends on libqalculate22. This was also mentioned in other comments, but I do not understand the solutions mentioned there. This package is not available at all in bullseye and also not after adding the repositories from here:

    See also https://packages.debian.org/search?keywords=libqalculate22

  45. Thomas Florek says:

    Please try (https://forum.siduction.org/index.php?topic=8393.msg67539#msg67539)
    apt full-upgrade libqalculate22+

  46. Benjamin says:

    was anybody else successful in updating to plasma 5.23 on bullseye or is it just my computer that is broke?

    • No, in fact it is currently broken because the build of libqalculate was deactivated. I have kicked of a rebuild and the OBS servers are crunching at it. Hopefully in short time (few hours) the package should be available, and with that update should be possible.

  47. Benjamin says:

    Yea!!! its working!!! thanks.

  48. X_Server says:

    Hello! After updating the KDE Plasma packages to version 5.23.3, I ran into the problem again – MTP does not work in Dolphin. I have libmtp packages installed, KIO is also installed, but the error still pops up: “File or folder udi =/org/kde/solid/udev/sys/devices/pci0000: 00/0000:00:14.0/usb1/1-2 does not exist “. That being said, everything works fine on Arch Linux and OpenSUSE. Debian is installed via netinstall, Plasma-Desktop package is manually installed. Maybe I did something wrong?

    I am attaching a screenshot (in Russian, but I translated the error in the message): https://ibb.co/kDDkwg4

    I also noticed that for some unknown reason, KDE Plasma on Debian is much slower than Arch and OpenSUSE. Could you tell me why this is so?

    Thanks in advance! =)

    • Not sure what this might be, maybe some permissions are not correct? Or you are not member of the correct groups? I really don’t know. I just plugged in a MTP device and it had a UDI very similar to yours, and worked without a problem.

      Concerning the “slow”, that is even harder to reason about: What is slower? Do you have hardware acceleration turned on? Is the compositor turned on? (See above comments) … There shouldn’t be any noticable speed difference when the hardware is properly set up.

      • X_Server says:

        I have no problem with hardware acceleration. Rendering is included in OpenGL 3.1, but everything is the same in 2.0, and the operating system is installed on an SSD. So, for example, Dolphin starts up in almost 1.5-2 seconds, while in OpenSUSE and Arch it starts almost instantly, and KDE Plasma runs more smoothly there than in Debian (and this is in an X11 session). Perhaps I’m wrong, but it seems to me that Debian simply does not cache the launch of the most frequently used programs and reloads the libraries every time (again, perhaps I do not understand something and know little about it)

        But I don’t know about MTP. USB devices such as thumb drives are working properly. KDE Connect, like Bluetooth, works just as well. There was a similar error with MTP back in version 5.22, and it was fixed by Dolphin update, but this time I even ran dpkg-reconfigure dolphin (also kio), but it did not help

  49. Thom says:

    Hi Norbert!
    Thanks for you great work!

    It looks like this issue https://bugs.kde.org/show_bug.cgi?id=445518 is present in the breeze-icon-theme 4:5.88.0-1 package from the Debian repository.

    Replacing only one breeze-icon-theme package with version 4:5.88.0-1~np2 from your repository solves this problem.

  50. Shmerl says:

    Btw, regarding ksysguard in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996737

    Unfortunately Plasma System monitor isn’t a good replacement yet due to maintainers not allowing selecting arbitrary sensors for CPU and GPU in it.

    See: https://bugs.kde.org/show_bug.cgi?id=438318

    Can you please help restore ksysguard in Debian repos? Until KDE Plasma System Monitor developers will change their approach, ksysguard is the only sensible option if you need flexible sensors monitoring.

    Thanks!

    • Sorry, not going to happen until upstream authors provide updated packages of ksysguard that works with curretn libksysguard. There was some movement around 5.21 but I haven’t seen any further updates, so it might not happen at all. Maybe you could help them getting ksysguard working with current libksysguard?

      • Shmerl says:

        Alright. But it might more productive for me to look into how to patch Plasma system monitor to prevent that artificial sensor filtering. That would be especially useful if upstream developers will decide not to cooperate and keep filtering things going forward.

  1. 2021/10/22

    […] KDE/Plasma 5.23 “25th Anniversary Edition” for Debian | There and back again […]

  2. 2021/10/22

    […] Más información: There and Back Again […]

  3. 2021/10/23

    […] Más información: There and Back Again […]

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>