https://bugs.kde.org/show_bug.cgi?id=502446
Bug ID: 502446
Summary: DrKonqui enters UI loop due to gdb/debuginfo failure.
Classification: Applications
Product: drkonqi
Version: 5.27.11
Platform: Ubuntu
OS: Linux
Status: REPORTED
Severity: major
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: tim-...@baverstock.org.uk
Target Milestone: ---
SUMMARY
Trying to install Prusa Slicer's flatpak by clicking the flatpak file -
discover hangs and then crashes, but DrKonqui enters a UI loop repeatedly
failing to retrieve crash information.
STEPS TO REPRODUCE
1. Try to install Prusa Slicer from
https://www.prusa3d.com/page/prusaslicer_424/
2. Click on the downloaded file to install it. For me, Discover hangs trying to
download the images and eventually crashes, bringing up DrKonqui.
3. Reach 'Fetching the Backtrace (Automatic Crash Inform...' screen.
4. Try to retrieve the stacktrace.
OBSERVED RESULT
It repeatedly shows 'The crash information could not be generated' with 'You
could try to regenerate the backtrace by clicking refresh'.
Clicking refresh flashes very briefly:
This GDB supports auto-downloading debuginfo from the following URL
https://debuginfod.ubuntu.com
Enable debuginfod for this session? (y or [N]) [answered N; input not from
terminal]
Debuginfod has been disabled
To make this setting permanent, add 'set debuginfod enabled off' to .gdbinit
and then blanks to show 'The crash information could not be generated' again
and leaving the 'Next' button disabled.
EXPECTED RESULT
1. Such a message should not flash up and vanish like that: I was able to
capture it with a video on my phone but that shouldn't be necessary: there
should be a log window showing the commands it's running and their output -
even if that output is perhaps folded.
2. I tried adding 'set debuginfod enabled on' to .gdbinit, but that had no
effect.
SOFTWARE/OS VERSIONS
Operating System: Kubuntu 24.04
KDE Plasma Version: 5.27.12
KDE Frameworks Version: 5.115.0
Qt Version: 5.15.13
Kernel Version: 6.8.0-54-generic (64-bit)
Graphics Platform: offscreen
Processors: 8 × Intel® Core™ i7-3610QM CPU @ 2.30GHz
Memory: 15.5 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 4000
ADDITIONAL INFORMATION
I managed to install Prusa from the command-line. I'm guessing the original bug
was in Discover, but it seems I can't report that unless this is fixed! Aaand
having just updated and/or installed, I can't reproduce the issue in Discover.
--
You are receiving this mail because:
You are watching all bug changes.
