https://bugs.kde.org/show_bug.cgi?id=363224
--- Comment #40 from A. Wilcox (awilfox) <awil...@adelielinux.org> --- (In reply to Martin Gräßlin from comment #37) > The problem is: we developers are not able to reproduce the issue. If we try > the steps outlined in this bug and its many duplicates it just doesn't > crash. There is an important part of the puzzle still missing. Something is > different for our users and for us trying to investigate. > > We need your support to figure out what it is. Once we find the key it will > be easy to fix. That is the proper way forward. Ranting won't fix the issue > but just demotivates those working on it. Please remember that I and most > KDE developers are volunteers working in their free time on it. I want to help! What can I provide? (In reply to marc from comment #38) > - it appears only with Intel on-chip card [HD graphics] Maybe you miss my comment #34: > OpenGL renderer string: Gallium 0.4 on AMD PITCAIRN 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Curacao PRO [Radeon R7 370 / R9 270/370 OEM] I am using a R9 270 and amdgpu.ko. I have not used composition for months until a few weeks ago to see if Mesa 13.0 finally fixes my OpenGL woes. It seems to have fixed most of them, but then I get this error. So I report it. I wish to be of more assistance, but I do not know what to provide. I continue to use my WINE-based task scheduler, and have pressed F10 hundreds of times since the crash, and don't have it any more. It is indeed very random. I can say I am using the beautiful plastiK window decorations with Breeze widget styles. I know that plastiK has been source of bugs in the past. But still, it is the only decoration that I truly enjoy, so I continue to use it. Maybe that is a difference? -- You are receiving this mail because: You are watching all bug changes.
