https://bugs.kde.org/show_bug.cgi?id=359542
--- Comment #30 from OlafLostViking <olaf.the.lost.vik...@gmail.com> --- Hi Sebas, first thank you very much for the work. I really don't want you to get this wrong and I fully understand that you are scanning through a lot of bug reports and it takes time to understand each of them. (Especially considering my bad English from time to time ;-) ) But I (personally) think that closing the bug because of too many details is not the best solution. If I would have written "Yes, doesn't work with 5.8.2." and that's it, would that have been better? So I tried around a long time to find a way to provoke this bug and attached the logfile. To make it easier for you to see what was happening in the log that lead to the crash I described what I did. If you are not interested in that, wouldn't it work to just ignore it and jump to the marked "2nd pause", where the crash happened - as written at the beginning? There are no problems with specific apps, as the broken images happen on multiple ones and only after kscreen "did things" ;-). So this wasn't a "Please fix the app." but a "Look, Kscreen(??) does something that leads to problems at many other places." The same goes with Plasma which takes the information vom libkscreen, I guess. Of course, nobody wants you to take care of that! It was just mentioned so that you could guess what kscreen is doing wrong at that point in time. So in the end I do not know what else I could write in a new bug report but "Crashes when (un-)docking." and attaching the very same log as above (there was no kscreen.log at the beginning which is why I started with kscreen-console and xrandr logs). I tried it on bug #371417 - I hope it helps. -- You are receiving this mail because: You are watching all bug changes.