Bug 508327

Summary:	"Debuginfod has been disabled" (again) on KDE Neon
Product:	[KDE Neon] neon	Reporter:	Malte S. Stretz <mss>
Component:	Packages Unstable Edition	Assignee:	Neon Bugs <neon-bugs>
Status:	RESOLVED WORKSFORME
Severity:	minor	CC:	carlosd.kde, jr, neon-bugs
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Neon
OS:	Linux
See Also:	https://bugs.kde.org/show_bug.cgi?id=484974
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	Screenshot

Description Malte S. Stretz 2025-08-16 10:12:52 UTC

Created attachment 184133 [details]
Screenshot

SUMMARY

Looks like the bug 484974 wasn't fixed properly.

STEPS TO REPRODUCE

1. Start KDE Neon Unstable Edition
2. Make something crash (I reproduced bug 486076)
3. In the Crash Handler (DrKonqi I guess) it will not download symbols via debuginfod even though the option to do so was enabled. 

OBSERVED RESULT

> Application: kded6 (kded6), signal: Segmentation fault
>
>
> This GDB supports auto-downloading debuginfo from the following URLs:
>   <https://debuginfod.neon.kde.org/>
>   <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.

EXPECTED RESULT

Debug symbols pulled via debuginfod

SOFTWARE/OS VERSIONS
Operating System: KDE neon Unstable Edition
KDE Plasma Version: 6.4.80
KDE Frameworks Version: 6.18.0
Qt Version: 6.9.1
Kernel Version: 6.14.0-27-generic (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i5-6300U CPU @ 2.40GHz
Memory: 24 GiB of RAM (23,4 GiB usable)
Graphics Processor: Intel® HD Graphics 520
Manufacturer: LENOVO
Product Name: 20JNS29X0R
System Version: ThinkPad T470 W10DG

ADDITIONAL INFORMATION

Comment 1 Carlos De Maine 2025-08-17 00:44:49 UTC

nothing has changed from the neon side.  upstream the the -DWITH_GDB12 flag has been removed so is now no-op.
necessary envvar is set correctly
`carlos@carlos-slimbook-unstable:~$ echo $DEBUGINFOD_URLS 
https://debuginfod.neon.kde.org/ https://debuginfod.ubuntu.com/`

can you please run drkonqi-coredump-gui  from konsole, click on a  crash and then press the "Run Interactive Debugger" button  ?
report back whether this runs as expected

Comment 2 Malte S. Stretz 2025-08-22 12:57:48 UTC

(In reply to Carlos De Maine from comment #1)
> nothing has changed from the neon side.  upstream the the -DWITH_GDB12 flag
> has been removed so is now no-op.

So it might be broken upstream/in Dr- Konqi?

> necessary envvar is set correctly
> `carlos@carlos-slimbook-unstable:~$ echo $DEBUGINFOD_URLS 
> https://debuginfod.neon.kde.org/ https://debuginfod.ubuntu.com/`

I can confirm that.

> can you please run drkonqi-coredump-gui  from konsole, click on a  crash and
> then press the "Run Interactive Debugger" button  ?
> report back whether this runs as expected

It doesn't really, at least it doesn't automatically download the debug info: As before it asks for confirmation (the "Enable debuginfod for this session? (y or [n])" prompt above) but since now it has a terminal it is waiting for my input. I don't know if this is expected in this interactive mode but in batch mode that prompt should be answered automatically. That was fixed in bug 454063 via the -DWITH_GDB12 flag.

I dist-upgraded to the latest Neon Developer edition before testing.

Comment 3 Malte S. Stretz 2025-08-22 13:06:31 UTC

Hmmm... looks like this was fixed in the meantime. I triggered a crash again (via `kcalc & sleep 1 && killall -SEGV kcalc) and now the debug symbols are downloaded automatically as they should. At east it doesn't show that gdb output anymore but the info dialog just closes after a while.

The `drkonqi-coredump-gui` still shows incomplete backtraces but when I enter the interactive debugger an confirm the download it shows the full symbols quickly (ie. the debuginfod data must have been loaded from the cache).