Version-Release number of selected component: kdelibs-4.12.3-1.fc20 Additional info: reporter: libreport-2.2.0 backtrace_rating: 4 cmdline: /usr/bin/kded4 --nocrashhandler crash_function: KCrash::defaultCrashHandler executable: /usr/bin/kded4 kernel: 3.13.7-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #1 KCrash::defaultCrashHandler at /usr/src/debug/kdelibs-4.12.3/kdeui/util/kcrash.cpp:346 #3 Solid::Backends::UPower::Battery::slotChanged at /usr/src/debug/kdelibs-4.12.3/solid/solid/backends/upower/upowerbattery.cpp:149 #4 QMetaObject::activate at kernel/qobject.cpp:3547 #6 QDBusInterfacePrivate::metacall at qdbusinterface.cpp:278 #7 QDBusConnectionPrivate::deliverCall at qdbusintegrator.cpp:951 #8 QObject::event at kernel/qobject.cpp:1194 #9 QApplicationPrivate::notify_helper at kernel/qapplication.cpp:4562 #10 QApplication::notify at kernel/qapplication.cpp:4348 #11 KApplication::notify at /usr/src/debug/kdelibs-4.12.3/kdeui/kernel/kapplication.cpp:311 #12 QCoreApplication::notifyInternal at kernel/qcoreapplication.cpp:949 Potential duplicate: bug 801275
Created attachment 880254 [details] File: backtrace
Created attachment 880255 [details] File: cgroup
Created attachment 880256 [details] File: core_backtrace
Created attachment 880257 [details] File: dso_list
Created attachment 880258 [details] File: environ
Created attachment 880259 [details] File: limits
Created attachment 880260 [details] File: maps
Created attachment 880261 [details] File: open_fds
Created attachment 880262 [details] File: proc_pid_status
Created attachment 880263 [details] File: var_log_messages
Another user experienced a similar problem: Recover from sleep reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: /usr/bin/kded4 --nocrashhandler crash_function: KCrash::defaultCrashHandler executable: /usr/bin/kded4 kernel: 3.14.8-200.fc20.x86_64 package: kdelibs-4.12.5-2.fc20 reason: kded4 killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
*** Bug 1103186 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 '20'. 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 20 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.