https://bugs.kde.org/show_bug.cgi?id=486572
--- Comment #4 from filip.kend...@gmail.com --- (In reply to Nate Graham from comment #3) > I can't reproduce the issue as depicted, and unfortunately the backtrace is > useless without those debug symbols. > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl > may help with getting a better backtrace. Can you try that? Thanks! I can't reproduce the issue today. I guess either something got messed up while I was messing with https://bugs.kde.org/show_bug.cgi?id=486568 and it was resolved after the reboot (although I did reboot couple of times yesterday while trying to install debug symbols and could always repro the issue) or the latest system update resolved the issue. Either way, I think we can close this as NOT A BUG since neither can repro it. As for installing the debug symbols, I just can't do it. - Exported DEBUGINFOD_URLS="https://debuginfod.archlinux.org"; as an environment variable per the Archlinux guide - Installed debuginfod package - Used the "Install Debug Symbols" though Dr Konqi - I'm not sure if it crashes, but I just run out of my grand 8GB of RAM and system freezes. I uploaded SS for this. - Tried using the gdb using the link you provided and it worked for the kcalc example, but when I tried to report it on a real crash (Draging the file in Dolphin over the location bar - that's already reported). Dolphin freezes like it's mentioned in the guide, but I can't use gdb anymore and again run out of RAM -- You are receiving this mail because: You are watching all bug changes.
