Bug#1142423: koko crashes when opening images after kf6-kirigami upgrade to 6.26

Marco Mattiolo <[email protected]> Sun, 19 Jul 2026 18:11:57 +0200
Newsgroups gmane.linux.debian.devel.qt-kde
Message-ID <DU2P195MB2372737A2058412ECD65D5E3E6C42__18046.665661835$1784477727$gmane$org@DU2P195MB2372.EURP195.PROD.OUTLOOK.COM>
Package: libkirigami6
Version: 6.26.0-2
Affects: koko

Hi,
after KF6 upgrade 6.23->6.26, koko started crashing upon opening image 
(tapping on the preview to open photo fullscreen) with following (the 
DrawerHandle.qml line is there before the crash)

$ koko
qrc:/qt/qml/org/kde/kirigami/templates/private/DrawerHandle.qml:117:5: 
TypeError: Cannot read property 'width' of null
qt.core.qobject.connect: QObject::connect(QObject, QQmlDMObjectData): 
invalid nullptr parameter
QQmlComponent: Cannot create a component in an invalid context
QQmlComponent: Cannot create a component in an invalid context
QQmlComponent: Cannot create a component in an invalid context
QQmlComponent: Cannot create a component in an invalid context
QQmlComponent: Cannot create a component in an invalid context
QQmlComponent: Cannot create a component in an invalid context
QQmlComponent: Cannot create a component in an invalid context
QQmlComponent: Cannot create a component in an invalid context
QQmlComponent: Cannot create a component in an invalid context
QQmlComponent: Cannot create a component in an invalid context
QQmlComponent: Cannot create a component in an invalid context
QQmlComponent: Cannot create a component in an invalid context
QQmlComponent: Cannot create a component in an invalid context
QQmlComponent: Cannot create a component in an invalid context
QQmlComponent: Cannot create a component in an invalid context
QQmlComponent: Cannot create a component in an invalid context
QQmlComponent: Cannot create a component in an invalid context
QQmlComponent: Cannot create a component in an invalid context
QQmlComponent: Cannot create a component in an invalid context
KCrash: Application 'koko' crashing... crashRecursionCounter = 2
Segmentation fault         (core dumped) koko

On another system I performed a segmented upgrade and found the 
following to be the culprit

Install: libkirigamiformsprivatetemplates6:arm64 (6.26.0-2, automatic), 
libkirigamicontrols6:arm64 (6.26.0-2, automatic), 
libkirigamiforms6:arm64 (6.26.0-2, automatic), 
libkirigamiformsprivateflat6:arm64 (6.26.0-2, automatic), 
libkirigamiformsprivatecards6:arm64 (6.26.0-2, automatic)
Upgrade: libkirigamidelegates6:arm64 (6.23.1-3, 6.26.0-2), 
libkirigamitemplates6:arm64 (6.23.1-3, 6.26.0-2), 
libkirigamilayouts6:arm64 (6.23.1-3, 6.26.0-2), 
libkirigamiprivate6:arm64 (6.23.1-3, 6.26.0-2), libkirigami6:arm64 
(6.23.1-3, 6.26.0-2), libkirigamidialogs6:arm64 (6.23.1-3, 6.26.0-2), 
libkirigamiprimitives6:arm64 (6.23.1-3, 6.26.0-2), 
libkirigamiplatform6:arm64 (6.23.1-3, 6.26.0-2), 
libkirigamilayoutsprivate6:arm64 (6.23.1-3, 6.26.0-2), 
libkirigamipolyfill6:arm64 (6.23.1-3, 6.26.0-2), 
qml6-module-org-kde-desktop:arm64 (6.23.0-2+b1, 6.26.0-1), 
qml6-module-org-kde-ksvg:arm64 (6.23.0-2, 6.26.0-1), 
qml6-module-org-kde-kirigami:arm64 (6.23.1-3, 6.26.0-2), 
libkirigami-data:arm64 (6.23.1-3, 6.26.0-2)

I've also tried re-building koko_26.04.0 on an up-to-date testing 
system, but it still crashes, then it doesn't seem to be a matter of 
koko needing a rebuild after KF6 upgrade.
Tried the same on pmOS, but it doesn't crash, even though they're on 
KF6.28, then this seems to be a Debian-specific issue

Kind regards
Marco