Version-Release number of selected component: kdelibs-4.11.4-1.fc20 Additional info: reporter: libreport-2.1.10 backtrace_rating: 3 cmdline: kded4 crash_function: _IO_vfprintf_internal executable: /usr/bin/kded4 kernel: 3.12.6-300.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 _IO_vfprintf_internal at vfprintf.c:1635 #1 buffered_vfprintf at vfprintf.c:2328 #2 _IO_vfprintf_internal at vfprintf.c:1289 #3 ___fprintf_chk at fprintf_chk.c:35 #4 fprintf at /usr/include/bits/stdio2.h:98 #5 startProcessInternal at /usr/src/debug/kdelibs-4.11.4/kdeui/util/kcrash.cpp:535 #6 KCrash::startProcess at /usr/src/debug/kdelibs-4.11.4/kdeui/util/kcrash.cpp:524 #7 KCrash::defaultCrashHandler at /usr/src/debug/kdelibs-4.11.4/kdeui/util/kcrash.cpp:311 #9 memmove at ../sysdeps/x86_64/multiarch/memcpy-ssse3.S:2975 #11 QListData::remove at tools/qlist.cpp:343 Potential duplicate: bug 889869
Created attachment 845824 [details] File: backtrace
Created attachment 845825 [details] File: cgroup
Created attachment 845826 [details] File: core_backtrace
Created attachment 845827 [details] File: dso_list
Created attachment 845828 [details] File: environ
Created attachment 845829 [details] File: exploitable
Created attachment 845830 [details] File: limits
Created attachment 845831 [details] File: maps
Created attachment 845832 [details] File: open_fds
Created attachment 845833 [details] File: proc_pid_status
Created attachment 845834 [details] File: var_log_messages
Another user experienced a similar problem: This happened after resuming from a suspend to disk, due laptop battery low. reporter: libreport-2.2.0 backtrace_rating: 3 cmdline: kded4 crash_function: _IO_vfprintf_internal executable: /usr/bin/kded4 kernel: 3.13.6-200.fc20.x86_64 package: kdelibs-4.12.3-1.fc20 reason: kded4 killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: Not sure what happened. Laptop (Thinkpad W510) lid was closed, power level about 35%, laptop had gone to sleep. Plugged in a wired network and opened the lid, ABRT popped up. Strange things I noticed: can't adjust screen brighness, bluetooth is on. reporter: libreport-2.2.3 backtrace_rating: 3 cmdline: kded4 crash_function: _IO_vfprintf_internal executable: /usr/bin/kded4 kernel: 3.16.2-201.fc20.x86_64 package: kdelibs-4.13.3-1.fc20 reason: kded4 killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
From the original backtrace, all I can tell is that it's deep in glib eventloop processing when the crash occurs. Not much to go on :-/
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.