Consistent Crash With KDE Wallet

I keep getting a consistent crash with KDE Plasma Wallet within 30 to 45 seconds of loading the DE. The crash report utility also has an issue and prompts me to retry or close the window. I saved the following a file named “drkonqi.CHk.AvV.txt” …


> Starting debugger gdb --nw --nx --batch --command=/tmp/drkonqi.djxCrB --command=/tmp/drkonqi.LbgMQW --core=/tmp/drkonqi-core.QrvBKA/core /usr/bin/ksecretd
> 
> This GDB supports auto-downloading debuginfo from the following URLs:
>   <https://debuginfod.opensuse.org/>
> 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.
> 
> warning: Can't open file /usr/lib64/ld-linux-x86-64.so.2 (deleted) during file-backed mapping note processing
> 
> warning: Can't open file /usr/lib64/gconv/gconv-modules.cache (deleted) during file-backed mapping note processing
> 
> warning: Can't open file /usr/lib64/libc.so.6 (deleted) during file-backed mapping note processing
> 
> warning: Can't open file /usr/lib64/libltdl.so.7.3.2 (deleted) during file-backed mapping note processing
> 
> warning: Can't open file /usr/lib64/libgraphite2.so.3.2.1 (deleted) during file-backed mapping note processing
> 
> warning: Can't open file /usr/lib64/libgomp.so.1.0.0 (deleted) during file-backed mapping note processing
> 
> warning: Can't open file /usr/lib64/libstdc++.so.6.0.34 (deleted) during file-backed mapping note processing
> 
> warning: Can't open file /usr/lib/locale/en_US.utf8/LC_CTYPE (deleted) during file-backed mapping note processing
> 
> warning: Can't open file /usr/lib64/libmvec.so.1 (deleted) during file-backed mapping note processing
> 
> warning: Can't open file /usr/lib64/libtinfo.so.6.5 (deleted) during file-backed mapping note processing
> 
> warning: Can't open file /usr/lib64/libblkid.so.1.1.0 (deleted) during file-backed mapping note processing
> 
> warning: Can't open file /usr/lib64/libnss_compat.so.2 (deleted) during file-backed mapping note processing
> 
> warning: Can't open file /usr/lib64/libgallium-25.1.3.so (deleted) during file-backed mapping note processing
> 
> warning: Can't open file /usr/lib64/libGLX_mesa.so.0.0.0 (deleted) during file-backed mapping note processing
> 
> warning: Can't open file /usr/lib64/libssh.so.4.10.1 (deleted) during file-backed mapping note processing
> 
> warning: Can't open file /usr/lib64/libKirigamiPlatform.so.6.15.0 (deleted) during file-backed mapping note processing
> 
> warning: Can't open file /usr/lib64/qt6/plugins/styles/breeze6.so (deleted) during file-backed mapping note processing
> 
> warning: Can't open file /usr/lib64/libcurl.so.4.8.0 (deleted) during file-backed mapping note processing
> 
> warning: Can't open file /usr/lib64/libmount.so.1.1.0 (deleted) during file-backed mapping note processing
> 
> warning: Can't open file /usr/lib64/libuuid.so.1.3.0 (deleted) during file-backed mapping note processing
> 
> warning: Can't open file /usr/lib64/libm.so.6 (deleted) during file-backed mapping note processing
> 
> warning: Can't open file /usr/lib64/libresolv.so.2 (deleted) during file-backed mapping note processing
> 
> warning: Can't open file /usr/lib64/qt6/plugins/platformthemes/KDEPlasmaPlatformTheme6.so (deleted) during file-backed mapping note processing
> [New LWP 2217]
> [New LWP 2228]
> [New LWP 2236]
> [New LWP 2227]
> [New LWP 2237]
> [New LWP 2239]
> [New LWP 2229]
> [New LWP 2233]
> [New LWP 2238]
> [New LWP 2232]
> 
> warning: .dynamic section for "/lib64/libmount.so.1" is not at the expected address (wrong library or version mismatch?)
> 
> warning: .dynamic section for "/lib64/libblkid.so.1" is not at the expected address (wrong library or version mismatch?)
> 
> warning: .dynamic section for "/lib64/libcurl.so.4" is not at the expected address (wrong library or version mismatch?)
> 
> warning: Could not load shared library symbols for /lib64/libgallium-25.1.3.so.
> Do you need "set solib-search-path" or "set sysroot"?
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib64/libthread_db.so.1".
> Core was generated by `/usr/bin/ksecretd'.
> Program terminated with signal SIGSEGV, Segmentation fault.
> #0  0x00007f22bca9b37c in create_thread () from /lib64/libc.so.6
> [Current thread is 1 (Thread 0x7f22bbe29380 (LWP 2217))]
> python sentry-sdk not installed :(
> Traceback (most recent call last):
>   File "/usr/share/drkonqi/gdb/python/gdb_preamble/preamble.py", line 812, in print_preamble
>     print_preamble_internal()
>     ~~~~~~~~~~~~~~~~~~~~~~~^^
>   File "/usr/share/drkonqi/gdb/python/gdb_preamble/preamble.py", line 783, in print_preamble_internal
>     resolve_modules()
>     ~~~~~~~~~~~~~~~^^
>   File "/usr/share/drkonqi/gdb/python/gdb_preamble/preamble.py", line 778, in resolve_modules
>     image = CoreImage(line)
>   File "/usr/share/drkonqi/gdb/python/gdb_preamble/preamble.py", line 742, in __init__
>     raise DeletedMappingException(f'Unexpectedly stumbled over a deleted mapping: {eu_unstrip_line}')
> DeletedMappingException: Unexpectedly stumbled over a deleted mapping: 0x7f22a9600000+0x297e000 - . - /usr/lib64/libgallium-25.1.3.so (deleted)
> Unexpectedly stumbled over a deleted mapping: 0x7f22a9600000+0x297e000 - . - /usr/lib64/libgallium-25.1.3.so (deleted)
> Debugging ended with exit code '1' and exit status 'NormalExit'

Any ideas?

Please post:
zypper lr -d

LANG=C zypper se -si | grep -Ei 'system_p|system p|system-p|systemp'

LANG=C zypper se -si mesa

And please for posting computer code do not use the Blockquote butten ", but the Preformatted text button </>.

Nevermind. I had installed Tumbleweed from my Ventoy USB SSD it apparently was the culprit all along as I downloaded Fedora and the Fedora USB tool. Neither the live session or the bare metal install is giving me issues.

So, you’re stating that you used Ventoy? If yes, it is NOT recommended to use Ventoy … or maybe your “the culprit” phrase is referring to Ventoy (?)

https://en.opensuse.org/Create_installation_USB_stick#Ventoy

I use Ventoy for just about everything for the last few years, and the only issues it gave me with installing any distro of Linux is certain boot/installation issues that are consistent with other multiboot creation tools (e.g. Manjaro) and the Ventoy repository entry. Nothing that can’t be overcome easily enough. But this is the first time where I experienced apparent file corruption that broke KDE Wallet to the point where it just segfaulted within 90 seconds of loading Plasma, and the reporting tool also had issues. I have a spare 500GB SATA drive in the target machine with nothing on it. I’ll try reinstalling Tumbleweed from my Ventoy SSD again to see if it happens again provided I’m not forced to work on the 4th … :frowning:

1 Like

Turns out the ISO I had downloaded two weeks ago was bad. Downloaded the latest Snapshot and reinstalled with Ventoy. No issues with KDE Wallet …