Version-Release number of selected component: kactivitymanagerd-5.8.1-1.fc25 Additional info: reporter: libreport-2.8.0 backtrace_rating: 4 cmdline: /usr/bin/kactivitymanagerd start-daemon crash_function: QObject::disconnect executable: /usr/bin/kactivitymanagerd global_pid: 2479 kernel: 4.8.8-300.fc25.x86_64 pkg_fingerprint: 4089 D8F2 FDB1 9C98 pkg_vendor: Fedora Project runlevel: unknown 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
Created attachment 1229315 [details] File: backtrace
Created attachment 1229316 [details] File: cgroup
Created attachment 1229317 [details] File: core_backtrace
Created attachment 1229318 [details] File: dso_list
Created attachment 1229319 [details] File: environ
Created attachment 1229320 [details] File: limits
Created attachment 1229321 [details] File: maps
Created attachment 1229322 [details] File: mountinfo
Created attachment 1229323 [details] File: namespaces
Created attachment 1229324 [details] File: open_fds
Created attachment 1229325 [details] File: proc_pid_status
Created attachment 1229326 [details] File: var_log_messages
Created attachment 1229327 [details] File: exploitable
Similar problem has been detected: I did not do anything. This error occurred on boot and appeared after I logged in. reporter: libreport-2.8.0 backtrace_rating: 4 cmdline: /usr/bin/kactivitymanagerd start-daemon crash_function: QObject::disconnect executable: /usr/bin/kactivitymanagerd global_pid: 1524 kernel: 4.10.15-200.fc25.i686+PAE package: kactivitymanagerd-5.9.5-1.fc25 pkg_fingerprint: 4089 D8F2 FDB1 9C98 pkg_vendor: Fedora Project reason: kactivitymanagerd killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Logged out of desktop after dnf update replaced glib. reporter: libreport-2.8.0 backtrace_rating: 3 cmdline: /usr/bin/kactivitymanagerd crash_function: QObject::disconnect executable: /usr/bin/kactivitymanagerd global_pid: 1495 kernel: 4.11.3-202.fc25.x86_64 package: kactivitymanagerd-5.9.5-1.fc25 pkg_fingerprint: 4089 D8F2 FDB1 9C98 pkg_vendor: Fedora Project reason: kactivitymanagerd killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Reproducible here, too. After nearly every login I get such a report.
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. 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 '25'. 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 25 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 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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.