https://bugs.kde.org/show_bug.cgi?id=497495
--- Comment #2 from lupe <lupefic...@gmail.com> --- Hi unfortunately when I tried to automatically report the bug from the program itself directly, after the crash, I got a prompt informing me that "it has been impossible to collect a proper back trace" , and so I reported it manually. That said, I couldn't reproduce it anymore Le vendredi 27 décembre 2024, John Kizer <bugzilla_nore...@kde.org> a écrit : > https://bugs.kde.org/show_bug.cgi?id=497495 > > John Kizer <john.ki...@proton.me> changed: > > What |Removed |Added > ------------------------------------------------------------ > ---------------- > Status|REPORTED |NEEDSINFO > CC| |john.ki...@proton.me > Resolution|--- |BACKTRACE > > --- Comment #1 from John Kizer <john.ki...@proton.me> --- > If something crashed, we need a backtrace of it so we can figure out what's > going on. Can you please attach a backtrace of the crash using the > coredumpctl > command-line program, as detailed in > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_ > useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl > ? > > Thanks! > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
