Hide Forgot
Version-Release number of selected component: kdeconnectd-1.0.1-2.fc26 Additional info: reporter: libreport-2.8.0 backtrace_rating: 4 cmdline: /usr/libexec/kdeconnectd crash_function: QObject::disconnect executable: /usr/libexec/kdeconnectd global_pid: 2088 kernel: 4.9.0-0.rc0.git4.1.fc26.x86_64 pkg_fingerprint: 812A 6B4B 64DA B85D pkg_vendor: Fedora Project runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (4 frames) #0 QObject::disconnect at kernel/qobject.cpp:2956 #2 QDBusConnectionPrivate::closeConnection at qdbusintegrator.cpp:1133 #3 QDBusConnectionManager::run at qdbusconnection.cpp:206 #4 QThreadPrivate::start at thread/qthread_unix.cpp:344 Potential duplicate: bug 1352190
Created attachment 1210715 [details] File: backtrace
Created attachment 1210716 [details] File: cgroup
Created attachment 1210717 [details] File: core_backtrace
Created attachment 1210718 [details] File: dso_list
Created attachment 1210719 [details] File: environ
Created attachment 1210720 [details] File: exploitable
Created attachment 1210721 [details] File: limits
Created attachment 1210722 [details] File: maps
Created attachment 1210723 [details] File: mountinfo
Created attachment 1210724 [details] File: namespaces
Created attachment 1210725 [details] File: open_fds
Created attachment 1210726 [details] File: proc_pid_status
Created attachment 1210727 [details] File: var_log_messages
This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle. Changing version to '26'.
Similar problem has been detected: Update from fedora 25 to 26 reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/libexec/kdeconnectd crash_function: QObject::disconnect executable: /usr/libexec/kdeconnectd journald_cursor: s=23a43169d18a45bf81b3cad95c4a6ef8;i=1fbbd8;b=b32cbb13d4f34efe9d17a046f7bd6522;m=4af893a;t=54f57edfb423c;x=f258a765a41d4a58 kernel: 4.11.0-1.fc26.x86_64 package: kdeconnectd-1.0.3-2.fc26 reason: kdeconnectd killed by signal 11 rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: I was in wayland session, but don't know what caused the crash reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/libexec/kdeconnectd crash_function: QObject::disconnect executable: /usr/libexec/kdeconnectd journald_cursor: s=eaa04589e6304d3480759ba488468e82;i=35ba;b=27f0a4a692cf4d68bcc575433665621b;m=e91e2465;t=551e69598ec64;x=e56fc2d5c681a4e7 kernel: 4.11.0-2.fc26.x86_64 package: kdeconnectd-1.0.3-2.fc26 reason: kdeconnectd killed by signal 11 rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: This crash occurs every time I log out of KDE Plasma (but not if I just reboot or power off). reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/libexec/kdeconnectd crash_function: QObject::disconnect executable: /usr/libexec/kdeconnectd journald_cursor: s=22003801544d48fabb755644e73832e6;i=4272;b=c4176feefc96422695b6f4ff3a8fdb6d;m=17cf213a;t=5527ef8fb6da4;x=b8a3e2d387a81a54 kernel: 4.11.6-300.fc26.x86_64 package: kdeconnectd-1.0.3-2.fc26 reason: kdeconnectd killed by signal 11 rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1471726 has been marked as a duplicate of this bug. ***
Similar problem has been detected: The problem is happening since i upgraded from fedora 25 to 26. At this time GNOME got upgraded to 3.24. So i think it is having compatibility issues. Everytime i launch kdeconnect, it crashes and it can be reproduced everytime. reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/libexec/kdeconnectd crash_function: QObject::disconnect executable: /usr/libexec/kdeconnectd journald_cursor: s=eb9b006f15fe432981b9bd9591a98ec4;i=37583;b=b05d3f2eca8f4c1aa54f8736053cde7d;m=a57ab84;t=5545ed0cdba72;x=9d30fbd2800635e kernel: 4.11.9-300.fc26.x86_64 package: kdeconnectd-1.0.3-2.fc26 reason: kdeconnectd killed by signal 11 rootdir: / runlevel: N 5 type: CCpp uid: 1000
Running the command 'pkill -SIGQUIT kdeconnectd' on KDE logout stops the crashes.
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.