Bug 494947

Summary: The crash reporter doesn't working
Product: [Plasma] plasmashell Reporter: Mozo <nstefanovmo>
Component: generalAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED UPSTREAM    
Severity: crash CC: kde, kdedev
Priority: NOR    
Version First Reported In: 6.2.1   
Target Milestone: 1.0   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: view detailed output log

Description Mozo 2024-10-17 17:41:00 UTC 
Created attachment 174956 [details]
view detailed output log

SUMMARY
From some time the crash reporter doesn't working. It offers to download the debug symbols and can't continue:
https://i.imgur.com/QFcGXeX.png
It stays here forever and no matter how many times you press on Retry, it doesn't work. Here's the log from the "view detailed output" link:
https://pastebin.com/gJHeJmr1
I'll attach it here as well.

STEPS TO REPRODUCE
1. Wait something to crash.
2. Use Automated reports.
3. 

OBSERVED RESULT
The process hangs and never finish.

EXPECTED RESULT
Automatic report.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 6.2.1
KDE Frameworks Version: 6.7.0
Qt Version: 6.8.0
Kernel Version: 6.11.3-arch1-1 (64-bit)
Graphics Platform: X11
Processors: 32 × Intel® Core™ i9-14900KF
Memory: 62.6 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 4090/PCIe/SSE2
Manufacturer: ASUS
Comment 1 TraceyC 2024-11-13 19:58:33 UTC 
Looks like gdb crashed


Downloading separate debug info for /usr/lib/qt6/plugins/kf6/krunner/krunner_systemsettings.so...
Downloading separate debug info for /usr/lib/libnss_systemd.so.2...
Downloading separate debug info for system-supplied DSO at 0x7abaa0121000...
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
Core was generated by `/usr/bin/plasmashell --no-respawn'.
Program terminated with signal SIGSEGV, Segmentation fault.
Downloading source file /usr/src/debug/glibc/glibc/nptl/pthread_kill.c...
#0  __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=11, no_tid=no_tid@entry=0) at pthread_kill.c:44
44	      return INTERNAL_SYSCALL_ERROR_P (ret) ? INTERNAL_SYSCALL_ERRNO (ret) : 0;
[Current thread is 1 (Thread 0x7ab9da0006c0 (LWP 3668))]
*** bit out of range 0 - FD_SETSIZE on fd_set ***: terminated


Fatal signal: Aborted
----- Backtrace -----
0x56ad92c0c2f0 ???
0x56ad92d46902 ???
0x7a224004c1cf ???
0x7a22400a53f4 ???
0x7a224004c11f ???
0x7a22400334c2 ???
0x7a2240034353 ???
0x7a2240134798 ???
0x7a2240134264 ???
0x56ad9312d9c5 ???
0x56ad9312de6f ???
0x56ad92c5290c ???
0x56ad92c4230b ???
0x56ad92e85809 ???
0x56ad92e858b7 ???
0x56ad92e87e54 ???
0x56ad92e88b8f ???
0x56ad92af6eef ???
0x7a2240034e07 ???
0x7a2240034ecb ???
0x56ad92b0adf4 ???
0xffffffffffffffff ???
---------------------
A fatal error internal to GDB has been detected, further
debugging is not possible.  GDB will now terminate.

This is a bug, please report it.  For instructions, see:
<https://www.gnu.org/software/gdb/bugs/>.

Debugging ended with exit code '6' and exit status 'CrashExit'
Comment 2 TraceyC 2024-11-13 20:02:03 UTC 
According to the attached backtrace, GDB itself crashed. Please use the information provided by the backtrace to report this to the GNU project.

This is a bug, please report it.  For instructions, see:
<https://www.gnu.org/software/gdb/bugs/>

Thanks!