Description of problem: I guess this crash is related to bug #1228577 Version-Release number of selected component: plasma-workspace-5.3.1-2.fc23 Additional info: reporter: libreport-2.5.1.34.g4907 backtrace_rating: 4 cmdline: /bin/plasmashell --shut-up crash_function: qt_message_fatal executable: /usr/bin/plasmashell global_pid: 4355 kernel: 4.1.0-0.rc6.git1.1.fc23.x86_64 runlevel: 3 5 type: CCpp uid: 18601 Truncated backtrace: Thread no. 1 (10 frames) #5 qt_message_fatal at global/qlogging.cpp:1422 #6 QMessageLogger::fatal at global/qlogging.cpp:643 #7 QObjectPrivate::QObjectPrivate at kernel/qobject.cpp:198 #8 QScriptEnginePrivate::QScriptEnginePrivate at /usr/src/debug/qtscript-opensource-src-5.4.1/src/script/api/qscriptengine.cpp:976 #9 QScriptEngine::QScriptEngine at /usr/src/debug/qtscript-opensource-src-5.4.1/src/script/api/qscriptengine.cpp:2059 #10 WorkspaceScripting::ScriptEngine::ScriptEngine at ../../shell/scripting/scriptengine.cpp:63 #11 ShellCorona::loadDefaultLayout at ../../shell/shellcorona.cpp:528 #12 ShellCorona::load at ../../shell/shellcorona.cpp:306 #13 ShellCorona::<lambda(KScreen::ConfigOperation*)>::operator() at ../../shell/shellcorona.cpp:268 #14 QtPrivate::FunctorCall<QtPrivate::IndexesList<0>, QtPrivate::List<KScreen::ConfigOperation*>, void, ShellCorona::setShell(const QString&)::<lambda(KScreen::ConfigOperation*)> >::call at /usr/include/qt5/QtCore/qobjectdefs_impl.h:494
Created attachment 1035124 [details] File: backtrace
Created attachment 1035125 [details] File: cgroup
Created attachment 1035126 [details] File: core_backtrace
Created attachment 1035127 [details] File: dso_list
Created attachment 1035128 [details] File: environ
Created attachment 1035129 [details] File: limits
Created attachment 1035130 [details] File: maps
Created attachment 1035131 [details] File: mountinfo
Created attachment 1035132 [details] File: namespaces
Created attachment 1035133 [details] File: open_fds
Created attachment 1035134 [details] File: proc_pid_status
Created attachment 1035135 [details] File: var_log_messages
yes, likely a dup *** This bug has been marked as a duplicate of bug 1228577 ***