Red Hat Bugzilla – Bug 1271396
segfault in kwin when using "Plastik" decoration
Last modified: 2016-07-19 14:12:53 EDT
Description of problem:
I'm in the process of testing a migration of several workstations from Fedora 20 to 22, all using KDE. On one test workstation I get lot's of segfaults from kwin.
Version-Release number of selected component (if applicable):
How reproducible: Always
Steps to Reproduce:
1. open a new kate process
2. Menu File, Open...
kwin segfaults before the open dialog is shown
open dialog shown, no segfault.
Using kate has proven to be the most reliable way to trigger it. But it happens with many other programs too, e.g. Firefox, Konqueror,... It usually happens when a new window or dialog should be shown.
I first thought this had something to do with desktop effects and the graphics driver, so I reduced the effects as much as I could. I also tried a Nvidia graphics card with Nouveau and an Intel one. Both did not fix or reduce the segfaults.
The user experiencing this had KDE 4 configured. Upgrading was done with fedup.
Created attachment 1082620 [details]
backtrace of kwin_x11 after the segfault
Seems to be related to kwin decoration, what decoration are you using?
Thanks for your quick reply.
I'm using the "Plastik" decoration.
When I switch to "org.kde.breeze", log out, log in again I can't reproduce the problem anymore (at least not so quick, haven't tried for a longer time yet). Switching back to Plastik, log out, log in and the segfaults are back.
So the problem seems indeed to be related to the windows decoration.
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
Thank you for reporting this bug and we are sorry it could not be fixed.