afaik, if you never ran an app through gdb there are no downloaded debug symbols so backtraces are always failing. It would be great to have an option in drkonqui / krash to after a crash run the app from gdb to actually get the debug symbols. After that backtraces work again.
I am not sure what you mean? Are your backtraces failing?
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
Yes I never have any backtraces in DRKonqui. Now again, even though I ran dolphin a lot through GDB as its constantly crashing. So not sure what the solution is, but the bug submission dialog is in general completely confusing (if you dont send attitional data or know what you did you dont get a backtrace???) and I saw its changed in Plasma 6 So some feature to run the app again and get backtraces, in drconqui, would be very needed
What distro? What version of Plasma? What version of frameworks? What version of Qt? ...
sorry Specified App: gdbm-libs-1.23-4.fc39.x86_64 wireless-regdb-2023.05.03-2.fc39.noarch gdb-headless-14.1-1.fc39.x86_64 gdb-14.1-1.fc39.x86_64 --- Software --- OS: Fedora Linux 39.20231214.0 (Kinoite) KDE Plasma: 5.27.9 KDE Frameworks: 5.111.0 Qt: 5.15.11 Kernel: 6.6.6-200.fc39.x86_64 Compositor: wayland --- Hardware --- CPU: AMD Ryzen 5 PRO 3500U w/ Radeon Vega Mobile Gfx RAM: 21.4 GB GPU: AMD Radeon Vega 8 Graphics Video memory: 2048MB Audio: Pipewire
Do you get any error in drkonqi?
Pretty much "no backtrace possible" for Dolphin
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 474116, bug 478110, 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