https://bugs.kde.org/show_bug.cgi?id=411349
--- Comment #20 from Emanuele Spirito <emaster...@gmail.com> --- > The most important information though is to find a reliable way to reproduce > the symptoms that a developer could reproduce then. > Until we don’t a way to reproduce or pinpoint the origin of the issue, we > are clueless. I know, I was trying to explain in the most complete way the issue so maybe any expert reading could find a clue to the solution I cannot see. > The recommended path to give actionable intel here, would be a trace using > gdb or https://github.com/KDAB/hotspot. Those technics require debugging > symbols. It might be out of your skill. I had a look to that link but I think you are right, this is quite hard for me. > It still helps to update bugs to inform devs which bugs are still > effectively hurting users and which ones are more common. > So thanks for the effort anyway. You are welcome, I'll stay tuned so if I can find the way to reproduce the bug I'll tell you. -- You are receiving this mail because: You are watching all bug changes.
