Version-Release number of selected component: kf5-kinit-5.20.0-1.fc23 Additional info: reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: 'http.so [kdeinit5] https local:/run/user/1000/klauncherXM1506.1.slave-socket local:/run/user/1000/konversationHf1209.4.slave-socket' crash_function: QObject::disconnect executable: /usr/bin/kdeinit5 global_pid: 16272 kernel: 4.4.6-300.fc23.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (4 frames) #0 QObject::disconnect at kernel/qobject.cpp:2949 #2 QDBusConnectionPrivate::closeConnection at qdbusintegrator.cpp:1111 #3 QDBusConnectionManager::run at qdbusconnection.cpp:191 #4 QThreadPrivate::start at thread/qthread_unix.cpp:340
Created attachment 1139944 [details] File: backtrace
Created attachment 1139945 [details] File: cgroup
Created attachment 1139946 [details] File: core_backtrace
Created attachment 1139947 [details] File: dso_list
Created attachment 1139948 [details] File: environ
Created attachment 1139949 [details] File: limits
Created attachment 1139950 [details] File: maps
Created attachment 1139951 [details] File: mountinfo
Created attachment 1139952 [details] File: namespaces
Created attachment 1139953 [details] File: open_fds
Created attachment 1139954 [details] File: proc_pid_status
Created attachment 1139955 [details] File: var_log_messages
I've also seen this crash (100% reproducible) since updating to Qt 5.6 with my PyQt application. I've now reported it upstream: https://bugreports.qt.io/browse/QTBUG-52988
*** Bug 1336501 has been marked as a duplicate of this bug. ***
*** Bug 1337512 has been marked as a duplicate of this bug. ***
Similar problem has been detected: i dont know. ever since I got the new kernel there have been system crashes (not dibilitating) and random other crashes like this, but most arnt reportable. reporter: libreport-2.6.4 backtrace_rating: 3 cmdline: 'http.so [kdeinit5] http local:/run/user/1000/klauncherXM1383.1.slave-socket local:/run/user/1000/plasmashellDS1433.3.slave-socket' crash_function: QObject::disconnect executable: /usr/bin/kdeinit5 global_pid: 6436 kernel: 4.4.9-300.fc23.x86_64 package: kf5-kinit-5.22.0-2.fc23 reason: kdeinit5 killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
*** Bug 1342838 has been marked as a duplicate of this bug. ***
This problem happens on Fedora 24 too. Please update the version.
Similar problem has been detected: it happens at startup reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: 'http.so [kdeinit5] http local:/run/user/1000/klauncherTJ1222.1.slave-socket local:/run/user/1000/kioclientXM1943.2.slave-socket' crash_function: QObject::disconnect executable: /usr/bin/kdeinit5 global_pid: 1946 kernel: 4.7.10-100.fc23.x86_64+debug package: kf5-kinit-5.26.0-1.fc23 reason: kdeinit5 killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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 '23'. 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 23 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.
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 '24'. 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 24 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 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.