Description of problem: I think it happened while I had qt-creator open. It can be reproduced by running the commandline. It gives me this error: [...] <<--- Repeated warnings about not being able to filter events like below... (Parent is QGuiApplication(0x7fffc91ceca0), parent's thread is QThread(0x1884570), current thread is QThread(0x188fcc0) QObject::installEventFilter(): Cannot filter events for objects in a different thread. QObject: Cannot create children for a parent that is in a different thread. (Parent is QGuiApplication(0x7fffc91ceca0), parent's thread is QThread(0x1884570), current thread is QThread(0x188fcc0) QObject: Cannot create children for a parent that is in a different thread. (Parent is QGuiApplication(0x7fffc91ceca0), pQWidget: Carent's thread is annot create a QWidgetQThread w(0x1884570), current thread is QThread(ith0x188fcc0) out QApplicQObject::installEventFiltationer(): Cannot filter events for objec ttts in a different thread. Aborted (core dumped) Version-Release number of selected component: qt5-qtdeclarative-devel-5.3.1-1.fc20 Additional info: reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /usr/lib64/qt5/bin/qmlplugindump -relocatable org.kde.plasma.components 2.0 /usr/lib64/qt5/qml crash_function: qt_message_fatal executable: /usr/lib64/qt5/bin/qmlplugindump kernel: 3.16.3-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (9 frames) #2 qt_message_fatal at global/qlogging.cpp:1364 #3 QMessageLogger::fatal at global/qlogging.cpp:669 #4 QWidgetPrivate::init at kernel/qwidget.cpp:1105 #5 QMenu::QMenu at widgets/qmenu.cpp:1339 #6 QMenuProxy::QMenuProxy at /usr/src/debug/plasma-framework-5.2.0/src/declarativeimports/plasmacomponents/qmenu.cpp:31 #7 QQmlElement at /usr/include/qt5/QtQml/qqmlprivate.h:101 #8 QQmlPrivate::createInto<QMenuProxy> at /usr/include/qt5/QtQml/qqmlprivate.h:110 #9 QQmlType::create() const at /lib64/libQt5Qml.so.5 #10 collectReachableMetaObjects(QQmlEngine*, QSet<QMetaObject const*>&, QSet<QMetaObject const*>&, QList<QQmlType*> const&)
Created attachment 942147 [details] File: backtrace
Created attachment 942148 [details] File: cgroup
Created attachment 942149 [details] File: core_backtrace
Created attachment 942150 [details] File: dso_list
Created attachment 942151 [details] File: environ
Created attachment 942152 [details] File: limits
Created attachment 942153 [details] File: maps
Created attachment 942154 [details] File: open_fds
Created attachment 942155 [details] File: proc_pid_status
Created attachment 942156 [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.