https://bugs.kde.org/show_bug.cgi?id=511874
--- Comment #8 from TraceyC <[email protected]> --- (In reply to Roke Julian Lockhart Beedell from comment #7) > Thanks, too. However, I was only really reporting the crash, unless you > think that the other information is actionable, considering that I don't see > a way to reproduce it. I'm a little wary to file bugs that'll likely be > closed as WAITINGFORINFO, since I presume it's not a great use of your time. Thank you for being considerate. If you can find a way to reliably reproduce the theming issue with Dr Konqi, it would be worth reporting. Without a way to reproduce, I'm afraid you're right, we wouldn't be able to do much. > > The crash has the same backtrace as bug 507936, and doesn't need to be > > reported again. > > Got any ideas on how to tell what it is before I report? Abrt tells me when > a trace matches something I've already reported, but Konqi doesn't. Unless I > just don't report ANRs for PlasmaShell, I'm not sure how to tell whether > one's a Mesa bug or not. I can't really read traces. Unfortunately, the only way to tell if a crash is the same as another is to read the backtrace. In the case of this and the other report, the backtraces are identical, if you were interested in seeing how we compare. They are an excellent example to learn from. We also have a howto on reading the backtraces, if you're interested https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging/Identifying_duplicates#Identifying_duplicates_(crashes)_:_C++_Backtraces -- You are receiving this mail because: You are watching all bug changes.
