SUMMARY As soon as /usr/lib/kdeconnectd finds and connects to my phone, it segfaults immediately. STEPS TO REPRODUCE 1. Open KDE-Connect Android app 2. press refresh on KDE-Connect config menu 3. watch crash notification pop up OBSERVED RESULT KDE-Connect crashes EXPECTED RESULT Connects to phone SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.14.4 (available in About System) KDE Plasma Version: 5.14.4 KDE Frameworks Version: 5.52.0 Qt Version: 5.11.2 ADDITIONAL INFORMATION /usr/lib/kdeconnectd output from terminal: kdeconnect.core: KdeConnect daemon starting kdeconnect.core: Warning: KDE Connect private key file has too open permissions "/home/christian/.config/kdeconnect/privateKey.pem" kdeconnect.core: onStart kdeconnect.core: KdeConnect daemon started kdeconnect.core: Broadcasting identity packet kdeconnect.core: Starting client ssl (but I'm the server TCP socket) kdeconnect.core: Socket succesfully stablished an SSL connection kdeconnect.core: It is a known device "Samsung SM-G960U" kdeconnect.plugin.sftp: add to dolphin kdeconnect.plugin.sftp: Created device: "Samsung SM-G960U" Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) kdeconnect.plugin.mpris: MPRIS service "org.mpris.MediaPlayer2.plasma-browser-integration" just came online kdeconnect.plugin.mpris: Mpris addPlayer "org.mpris.MediaPlayer2.plasma-browser-integration" -> "Firefox Web Browser" KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = kdeconnectd path = /usr/lib pid = 29664 KCrash: Arguments: /usr/lib/kdeconnectd KCrash: Attempting to start /usr/lib/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5__0 QSocketNotifier: Invalid socket 8 and type 'Read', disabling... QSocketNotifier: Invalid socket 13 and type 'Read', disabling... QSocketNotifier: Invalid socket 9 and type 'Read', disabling... [1] + 29664 suspended (signal) /usr/lib/kdeconnectd
Hello! Thank you for reporting the issue. Could you please provide a backtrace for the crash? https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#How_to_create_useful_crash_reports
updating to NEEDSINFO till the backtrace is provided
Created attachment 116846 [details] Backtrace on crash described I believe this is the relevant backtrace, let me know if any further info is needed. Sorry for any delays in my response.
Could you please install debug symbols for kdeconnect and re-capture the backtrace?
Alright, I compiled it with the debug flag set, however I no longer am observing the crash under the conditions previously described. Consider my problem fixed for the time being.
Created attachment 116887 [details] Backtrace of crash, with debug symbols Immediately after replying the crash occurred, backtrace attached.
Could you please say what apps have active notifications on your phone when the crash happens?
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
Possibly a duplicate of bug #400010.
*** This bug has been marked as a duplicate of bug 400010 ***