Created attachment 1011522 [details] backtrace from segmentation fault Description of problem: KDE 5 Plasma Shell sengmentation fault after I refreshed a page in the Chrome Web Browser Version-Release number of selected component (if applicable): 5.8.01 How reproducible: did not try to reproduce Steps to Reproduce: 1. 2. 3. Actual results: plasma-shel segmentation fault Expected results: browser page would refresh Additional info: I have dual-monitors enabled. I have not tried reproducing this on a single monitor configuration backtrace attached
Created attachment 1011535 [details] back trace from another crash
Created attachment 1011583 [details] one more backtrace
The third attached backtrace was collected when I was running in a single monitor (laptop display) configuration so multiple monitors is not the cause of the problem, however crashes were occurring more frequently with multiple monitors enabled.
KDE upstream bug report: https://bugs.kde.org/show_bug.cgi?id=342763 To be honest this looks like a Qt bug to me, VDMModelDelegateDataType is part of the low-level implementation detail of QML ListView.
debuginfo-install plasmashell will help get a better backtrace next time per upstream comment: "Hmm not much to do unfortunately ... the backtrace is quite non-descript and also doesn't have line numbers... I need a better BT"
Two plasma-workspace segmentation faults today. Although this is the same behavior as described above, not sure if the root cause is the same. I was playing with panels: I had just created an empty panel, deleted it, created a default panel and deleted it--then the first crash occurred. I have two monitors. My panel creations/deletions were done on the primary monitor. The problem reporting tool told me I have version 5.5.1.1.fc22.x86_64 of plasma-workspace, and that the plasma shell was killed by SIGSEGV. I clicked on the problem reporting tool's REPORT button, but nothing appeared to happen.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.