Description of problem: Just working along and suddenly got an alert that plasmashell had crashed. I wasn't doing anything unusual that I can recall. Version-Release number of selected component: plasma-workspace-5.5.3-4.fc23 Additional info: reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/bin/plasmashell --shut-up crash_function: KCrash::defaultCrashHandler executable: /usr/bin/plasmashell global_pid: 1885 kernel: 4.3.3-300.fc23.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #1 KCrash::defaultCrashHandler at ../../src/kcrash.cpp:431 #3 __memmove_avx_unaligned at ../sysdeps/x86_64/multiarch/memcpy-avx-unaligned.S:244 #4 memmove at /usr/include/bits/string3.h:59 #5 drisw_update_tex_buffer at drisw.c:356 #6 dri_set_tex_buffer2 at dri_drawable.c:245 #7 Plasma::WindowThumbnail::bindGLXTexture at ../../../../src/declarativeimports/core/windowthumbnail.cpp:447 #8 Plasma::WindowThumbnail::windowToTextureGLX at ../../../../src/declarativeimports/core/windowthumbnail.cpp:282 #9 Plasma::WindowThumbnail::windowToTexture at ../../../../src/declarativeimports/core/windowthumbnail.cpp:394 #10 Plasma::WindowThumbnail::updatePaintNode at ../../../../src/declarativeimports/core/windowthumbnail.cpp:199 #11 QQuickWindowPrivate::updateDirtyNode at /usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/quick/items/qquickwindow.cpp:2984
Created attachment 1115997 [details] File: backtrace
Created attachment 1115998 [details] File: cgroup
Created attachment 1115999 [details] File: core_backtrace
Created attachment 1116000 [details] File: dso_list
Created attachment 1116001 [details] File: environ
Created attachment 1116002 [details] File: limits
Created attachment 1116003 [details] File: maps
Created attachment 1116004 [details] File: mountinfo
Created attachment 1116005 [details] File: namespaces
Created attachment 1116006 [details] File: open_fds
Created attachment 1116007 [details] File: proc_pid_status
Created attachment 1116008 [details] File: var_log_messages
Another user experienced a similar problem: It is happening randomly and repeatedly, with no concrete foregoing actions. reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/bin/plasmashell -s --crashes 1 crash_function: KCrash::defaultCrashHandler executable: /usr/bin/plasmashell global_pid: 2652 kernel: 4.3.3-303.fc23.x86_64 package: plasma-workspace-5.5.4-1.fc23 reason: plasmashell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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 '23'. 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 23 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 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.