KDE Connect SMS crashes on start

[c58638977]

I have a very similar to that reported here in a fresh install of Kubuntu 25.04:

Ubuntu 24.10: kdeconnect-sms crashes on start

Hello! I’ve been using KDE Connect and for years on Ubuntu without any bigger problems. A few weeks ago, I upgraded to Ubuntu 24.10. Since then, kdeconnect-sms does not work anymore, everything else still seems to work. What does “not work anymore” mean? When I click on the Icon, nothing happens. When I run it directly from the command line, I get this: ~ kdeconnect-sms qt.qml.typeresolution.cycle: Cyclic dependency detected between "qrc:/qt/qml/org/kde/desktop/private/TextFieldContextMenu.qm…

However, the fix reported there was to install the missing dependency qml6-module-org-kde-kirigamiaddons-components. I already have this installed—the packaging issue seems to have been fixed—but KDE Connect SMS still crashes when run:

> kdeconnect-sms
QThreadStorage: entry 8 destroyed before end of thread 0x5cbdd5f47f30
QThreadStorage: entry 3 destroyed before end of thread 0x5cbdd5f47f30
QThreadStorage: entry 2 destroyed before end of thread 0x5cbdd5f47f30

Exit code is 0.

[WaggleWorx]

I’m also experiencing this on Kubuntu 25.04

I can reproduce this in terminal with kdeconnect-sms and it produces the following output:

QThreadStorage: entry 8 destroyed before end of thread 0x5deb16503f30
QThreadStorage: entry 3 destroyed before end of thread 0x5deb16503f30
QThreadStorage: entry 2 destroyed before end of thread 0x5deb16503f30

I tried digging into QT logging, but wasn’t able to make any useful progress.

[phm]

Hi, same question here about kdeconnect-sms terminating immediately on launch without apparent errors. I tried running with debug logging:

export QT_FORCE_STDERR_LOGGING=1
export QT_LOGGING_RULES="*.debug=true"
kdeconnect-sms

The result shows nothing suspicious at all, except for:

QThreadStorage: entry 8 destroyed before end of thread 0x632f1627bf30
QThreadStorage: entry 3 destroyed before end of thread 0x632f1627bf30
QThreadStorage: entry 2 destroyed before end of thread 0x632f1627bf30

But other than that, no indication why kdeconnect-sms terminates, at least that I can see.

I can browse the files on the mobile phone, and other kdeconnect features seem to work just fine.

Since there’s no crash, no errors in the log, it makes little sense to raise a ticket to simply say “not working” without useful evidence.

What else can I do to gather evidence of a problem?

Thanks.

[phm]

Adding an observation that SMS messages arriving on the mobile have appeared as notifications in KDE containing the full message text. It appears that kdeconnect is able to see SMS message content, but kdeconnect-sms still fails to launch.