https://bugs.kde.org/show_bug.cgi?id=511874
--- Comment #7 from Roke Julian Lockhart Beedell <[email protected]> --- (In reply to TraceyC from comment #6) > Thanks for the bug report! Unfortunately it reports multiple distinct > issues, which will make it not actionable. See > https://community.kde.org/Get_Involved/ > Issue_Reporting#Multiple_issues_in_a_single_Bugzilla_ticket for more > explanation. > > Can I ask you to submit a new bug report for each specific issue that isn't > the crash? Thanks again! 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. > 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. -- You are receiving this mail because: You are watching all bug changes.
