Description of problem: I needed to disable USB3 to get my scanner working, so I shutdown KDE via the menu and did a cold start. After disabling USB in the UEFI BIOS (it hides the USB3 controller according to the accompanying text so it shows up as a USB2 controller) I restarted the laptop (Lenovo T440). After a normal startup (not touching the keyboard except for entering the disk decryption password) I was presented with the user screen from GDM. After that I logged in my user and the KDE interface shows me the splash screen, but not the top menu bar thingie and after the crash (presumably GDM) restarts KDE and abrt show me the crash. As to what exactly caused it I have no idea. Version-Release number of selected component: kdelibs-4.12.5-2.fc20 Additional info: reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: 'kdeinit4: krunner [kdeinit]' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' crash_function: _xend executable: /usr/bin/kdeinit4 kernel: 3.14.7-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 _xend at ../nptl/sysdeps/unix/sysv/linux/x86/elision-unlock.c:33 #1 __lll_unlock_elision at ../nptl/sysdeps/unix/sysv/linux/x86/elision-unlock.c:29 #2 unlock at /usr/src/debug/kdelibs-4.12.5/kdecore/util/kshareddatacache.cpp:1245 #3 ~CacheLocker at /usr/src/debug/kdelibs-4.12.5/kdecore/util/kshareddatacache.cpp:1317 #4 KSharedDataCache::insert at /usr/src/debug/kdelibs-4.12.5/kdecore/util/kshareddatacache.cpp:1595 #5 KIconLoaderPrivate::insertCachedPixmapWithPath at /usr/src/debug/kdelibs-4.12.5/kdeui/icons/kiconloader.cpp:827 #6 KIconLoader::loadIcon at /usr/src/debug/kdelibs-4.12.5/kdeui/icons/kiconloader.cpp:1205 #7 KIconEngine::pixmap at /usr/src/debug/kdelibs-4.12.5/kdeui/icons/kiconengine.cpp:104 #8 QIcon::pixmap at image/qicon.cpp:684 #9 QWidgetPrivate::setWindowIcon_sys at kernel/qwidget_x11.cpp:1490
Created attachment 912199 [details] File: backtrace
Created attachment 912200 [details] File: cgroup
Created attachment 912201 [details] File: core_backtrace
Created attachment 912202 [details] File: dso_list
Created attachment 912203 [details] File: environ
Created attachment 912204 [details] File: exploitable
Created attachment 912205 [details] File: limits
Created attachment 912206 [details] File: maps
Created attachment 912207 [details] File: open_fds
Created attachment 912208 [details] File: proc_pid_status
Created attachment 912209 [details] File: var_log_messages
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.