https://bugs.kde.org/show_bug.cgi?id=504236
--- Comment #8 from John Kizer <john.ki...@proton.me> --- Hmm - I don't know if there are specific, unique things that need to done on Arch Linux to get a backtrace fully populated, beyond what's listed out on the Community Wiki link that I shared earlier. I'm also still 99% sure that this is an instance of that bug 503703 popping up - so would it work to say: * If you're able to snag a fully populated backtrace from your device, add it as a comment here * If not, then when Kirigami 6.14.1 - the point release that contains the fix for that bug - is packaged and updated for Arch Linux (likely not too long from now), can you check if this crash still occurs? Thanks! -- You are receiving this mail because: You are watching all bug changes.
