Already discussed in here, but looks like a bug: https://discuss.kde.org/t/kdeconnect-sms-crashes-at-start/39468/4 SUMMARY STEPS TO REPRODUCE 1. launch kdeconnect-sms from the CLI OBSERVED RESULT QThreadStorage: Thread 0x5847fc4610f0 exited after QThreadStorage 8 destroyed QThreadStorage: Thread 0x5847fc4610f0 exited after QThreadStorage 3 destroyed QThreadStorage: Thread 0x5847fc4610f0 exited after QThreadStorage 2 destroyed Log shows: – Boot 745a6dbf1f964fef8b50a6314f79c5ca – sep 12 09:22:12 gda-tux systemd[1560]: Starting app-org.kde.kdeconnect.daemon@autostart.service - KDE Connect… sep 12 09:22:12 gda-tux systemd[1560]: Started app-org.kde.kdeconnect.daemon@autostart.service - KDE Connect. sep 12 09:22:12 gda-tux kdeconnectd[2043]: 2025-09-12T09:22:12 default: Error sending UDP packet: QAbstractSocket::NetworkError sep 12 09:22:12 gda-tux kdeconnectd[2043]: 2025-09-12T09:22:12 kdeconnect.core: Failed to open any MDNS client sockets sep 12 09:22:12 gda-tux kdeconnectd[2043]: 2025-09-12T09:22:12 kdeconnect.core: Failed to open any MDNS server sockets sep 12 09:22:13 gda-tux kdeconnectd[2043]: 2025-09-12T09:22:13 kdeconnect.core: Failed to send mDNS query: Cannot assign requested address sep 12 09:22:31 gda-tux kdeconnectd[2043]: 2025-09-12T09:22:31 kdeconnect.core: “Pixel 9 Pro XL” uses a different protocol version 8 expected 7 sep 12 09:23:01 gda-tux kdeconnectd[2043]: 2025-09-12T09:23:01 default: Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) sep 12 09:23:01 gda-tux kdeconnectd[2043]: 2025-09-12T09:23:01 default: discarding unsupported packet “kdeconnect.battery” for “Pixel 9 Pro XL” sep 12 09:23:01 gda-tux kdeconnectd[2043]: 2025-09-12T09:23:01 default: Clearing existing entries 0 EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION