Created attachment 163903 [details] Debug symbol silent installation failure. SUMMARY When performing a live update, certain files necessary to parse a backtrace might be removed, making backtrace parsing impossible. Because the reason for the result is not communicated to the user, this appears erroneous, degrading confidence in the bug reporting system. Additionally, because certain bugs solely present themselves during updates, this can be especially frustrating because that's the sole opportunity to report them. For instance, as https://bugsfiles.kde.org/attachment.cgi?id=162707 demonstrates, when debug symbols are not installed, this creates a strange situation whereby a reboot would be necessary to put the correct files in the correct locations for them to be usable by DrKonqi, yet the package is displayed to the user as installed. To my knowledge, updating the system whilst it is booted, by using the CLI or a pkcon-powered GUI package manager like Discover, is the standard method of updating. This is as opposed to automatic updates on boot, which plasma-systemsettings and plasma-discover in a certain harmonious configuration provide. STEPS TO REPRODUCE 1. Update the system. 1. Notice an automatic crash report notification window from DrKonqi. OBSERVED RESULT Unable to parse backtrace due to absent debug symbols. EXPECTED RESULT Should explain why and how to create a usable backtrace (reboot?) and warn against filing issues caused by updates unless certain they are useful (and better yet, automatically factor this decision into the star system). SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20231203 KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.112.0 Qt Version: 5.15.11 Kernel Version: 6.6.3-1-default (64-bit) Graphics Platform: X11 Processors: 12 × AMD Ryzen 5 7600X 6-Core Processor Memory: 30.5 GiB of RAM Graphics Processor: AMD Radeon RX 5700 Manufacturer: ASRock Product Name: X670E Taichi ADDITIONAL INFORMATION https://bugs.kde.org/show_bug.cgi?id=270002#c15
A possibly relevant merge request was started @ https://invent.kde.org/plasma/drkonqi/-/merge_requests/261
Git commit 34cc1171c26d72dc423cbe0f10d03ac541b3d1e6 by Harald Sitter. Committed on 27/08/2024 at 11:24. Pushed by sitter into branch 'master'. backtracegenerator: cache raw debugger output and give the user access to it this now means we capture both stdout and stderr. shouldn't be a huge problem because we ultimately run the output through the gdb parser anyway and that filters out most of the noise. plus, we mostly care about the traces in sentry anyway and those are generated by the preamble and clean. there are two ways to get the data - the inlinemessage now sports a details link that opens a txt file - via the developer view, which no longer shows a useless error there area also now verbosity lines to mark the beginning and the end of the debugging session Related: bug 477586, bug 474116, bug 491820 M +53 -2 src/backtracegenerator.cpp M +7 -0 src/backtracegenerator.h M +2 -3 src/qml/DeveloperPage.qml M +16 -1 src/qml/main.qml https://invent.kde.org/plasma/drkonqi/-/commit/34cc1171c26d72dc423cbe0f10d03ac541b3d1e6