https://bugs.kde.org/show_bug.cgi?id=508868
TraceyC <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |BACKTRACE Status|REPORTED |NEEDSINFO --- Comment #8 from TraceyC <[email protected]> --- (In reply to Jens from comment #7) > Please advise on how to install the needed backtrace packages specifically > for this bug on KDE Neon. I have read the generic instructions but they > don't work for me - drkonqi never finishes and consumes >1.5GB of /tmp space First, you'll need to find a way to make more space in /tmp before you'll be successful in getting a backtrace. 5G should be plenty I recommend reaching out to your distro for support doing this. After you've done that, take another look at the link from my previous reply https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl There's a section on "Install debugging packages", with a section for Neon. > KDE neon > Neon has the debug symbols in its regular repository. If you need help installing the debug packages, please reach out on the Neon forums. After you have the debug symbols, it's time to get the backtrace. You may not need to create the crash again. If there's an existing coredump, you can get a backtrace of that, using the information on the page linked above. Thanks. -- You are receiving this mail because: You are watching all bug changes.
