krunner and discover not working after upgrade

Started by finotti, Yesterday at 16:32:30

Previous topic - Next topic

finotti

Probably related to the libqt6 and qml6 transition, but Krunner and discover stopped working on my laptop after a full-upgrade just a few minutes ago.

Here is what i get in the command line:

$ plasma-discover

org.kde.plasma.libdiscover: OdrsReviewsBackend: Fetch ratings: true

(process:8764): dconf-WARNING **: 10:22:38.032: unable to open file '/etc/dconf/db/local': /etc/dconf/db/local: invalid gvdb header; expect degraded performance
adding empty sources model QStandardItemModel(0x55ace9d3eda0)
qrc:/qt/qml/org/kde/discover/qml/DiscoverWindow.qml:127:5: QML Shortcut: Shortcut: Only binding to one of multiple key bindings associated with 15. Use 'sequences: [ <key> ]' to bind to all of them.
KCrash: Application 'plasma-discover' crashing... crashRecursionCounter = 2
KCrash: Application Name = plasma-discover path = /usr/bin pid = 8764
KCrash: Arguments: /usr/bin/plasma-discover
KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi
Unable to start Dr. Konqi
org.kde.drkonqi: The specified process does not exist.

$ krunner

KCrash: Application 'krunner' crashing... crashRecursionCounter = 2
KCrash: Application Name = krunner path = /usr/bin pid = 9316
KCrash: Arguments: /usr/bin/krunner
KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi
QSocketNotifier: Invalid socket 5 and type 'Read', disabling...
QSocketNotifier: Invalid socket 9 and type 'Read', disabling...
QSocketNotifier: Invalid socket 11 and type 'Read', disabling...

Here is some info on the laptop:

$ inxi -v3

System:
  Host: t14s Kernel: 7.2.7-1-siduction-amd64 arch: x86_64 bits: 64
    compiler: gcc v: 15.3.0
  Desktop: KDE Plasma v: 6.7.4 Distro: siduction 2026.1.0 big-crime - kde -
    (202609010926) base: Debian GNU/Linux forky/sid
Machine:
  Type: Laptop System: LENOVO product: 20XGS06B00 v: ThinkPad T14s Gen 2a
    serial: <superuser required>
  Mobo: LENOVO model: 20XGS06B00 v: SDK0K17763 WIN
    serial: <superuser required> Firmware: UEFI vendor: LENOVO
    v: R1NET64W (1.34) date: 04/07/2025
Battery:
  ID-1: BAT0 charge: 39.6 Wh (85.2%) condition: 46.5/57 Wh (81.5%)
    volts: 16.46 min: 15.36 model: Sunwoda 5B10W51816 status: not charging
CPU:
  Info: 8-core model: AMD Ryzen 7 PRO 5850U with Radeon Graphics bits: 64
    type: MT MCP arch: Zen 3 rev: 0 cache: L1: 512 KiB L2: 4 MiB L3: 16 MiB
  Speed (MHz): avg: 2296 min/max: 407/4508 boost: enabled cores: 1: 2296
    2: 2296 3: 2296 4: 2296 5: 2296 6: 2296 7: 2296 8: 2296 9: 2296 10: 2296
    11: 2296 12: 2296 13: 2296 14: 2296 15: 2296 16: 2296 bogomips: 60684
  Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a
    ssse3 svm
Graphics:
  Device-1: Advanced Micro Devices [AMD/ATI] Cezanne [Radeon Vega Series /
    Radeon Mobile Series] vendor: Lenovo driver: amdgpu v: kernel arch: GCN-5
    bus-ID: 05:00.0 temp: 45.0 C
  Device-2: IMC Networks Integrated RGB Camera driver: uvcvideo type: USB
    bus-ID: 5-2:2
  Display: x11 server: X.Org v: 21.1.24 with: Xwayland v: 24.1.13 driver: X:
    loaded: amdgpu unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: amdgpu
    resolution: 1920x1080~60Hz
  API: OpenGL v: 4.6 vendor: amd mesa v: 26.2.3-2 glx-v: 1.4
    direct-render: yes renderer: AMD Radeon Graphics (radeonsi renoir ACO DRM
    3.64 7.2.7-1-siduction-amd64)
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor wl: wayland-info x11: xdriinfo,
    xdpyinfo, xprop, xrandr
Network:
  Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    vendor: Lenovo driver: r8169 v: kernel port: 2000 bus-ID: 02:00.0
  IF: enp2s0f0 state: down mac: 88:a4:c2:65:6f:c5
  Device-2: Qualcomm QCNFA765 Wireless Network Adapter vendor: Lenovo
    driver: ath11k_pci v: kernel bus-ID: 03:00.0
  IF: wlan0 state: up mac: 10:6f:d9:a1:84:c3
  IF-ID-1: tailscale0 state: unknown speed: -1 duplex: full mac: N/A
Drives:
  Local Storage: total: 238.47 GiB used: 118.94 GiB (49.9%)
Info:
  Memory: total: 16 GiB note: est. available: 14.46 GiB used: 5.89 GiB (40.7%)
  Processes: 423 Uptime: 20m Init: systemd
  Packages: 4272 Compilers: gcc: 16.2.0 Shell: Bash v: 5.3.15 inxi: 3.3.41

Any ideas?

towo

Ich gehe nicht zum Karneval, ich verleihe nur manchmal mein Gesicht.

finotti

Quote from: towo on Yesterday at 18:32:44No problem here for both.

Thanks towo for the reply.  I tried rebooting, and now plasma itself crashes...  SDDM starts fine, but logging in, plasma crashes.  I do get windows and my shortcuts still open applications (I am using it now), but no panel or widgets.

Here are some logs: https://luisfinotti.org/misc/errors.txt 
I see no errors in Xorg.0.log or dmesg.

The system is completely up-to-date.  (I just did another full-upgrade to be safe).

# kinfo
Operating System: siduction 2026.1
KDE Plasma Version: 6.7.4
KDE Frameworks Version: 6.30.0
Qt Version: 6.11.2
Kernel Version: 7.2.7-1-siduction-amd64 (64-bit)
Graphics Platform: X11
Processors: 16 × AMD Ryzen 7 PRO 5850U with Radeon Graphics
Memory: 16 GiB of RAM (14.5 GiB usable)
Graphics Processor: AMD Radeon Graphics

Any ideas?  Does Plasma have its logs in any particular file?

towo

QuoteAny ideas?
Sure, don't use xorg, use wayland. With the update to plasma 6.8, there is no xorg session anymore.
Ich gehe nicht zum Karneval, ich verleihe nur manchmal mein Gesicht.

finotti

Quote from: towo on Yesterday at 22:30:25
QuoteAny ideas?
Sure, don't use xorg, use wayland. With the update to plasma 6.8, there is no xorg session anymore.
I tried, and had the same result...

Teriarch

@finotti
Start with krunner to see what's causing the crash:
$ gdb --args krunnerWhen you see the (gdp) prompt type "run".
The crash (presumably a SEGFAULT) takes you
back to the gdb (GNU debugger) prompt. Type
(gdb) bt(bt aka backtrace). Post the output (maybe a shared
library relict is faulty).

finotti

Quote from: Teriarch on Today at 00:43:20@finotti
Start with krunner to see what's causing the crash:
$ gdb --args krunnerWhen you see the (gdp) prompt type "run".
The crash (presumably a SEGFAULT) takes you
back to the gdb (GNU debugger) prompt. Type
(gdb) bt(bt aka backtrace). Post the output (maybe a shared
library relict is faulty).

Thanks for the reply!  Here is what I got: https://luisfinotti.org/misc/krunner_bt.txt

Here are the packages that were installed and removed yesterday: https://luisfinotti.org/misc/dpkg_20260923.log  (Only  libavdevice62:amd64 7:8.1.2-2+b3 was removed.)

Any ideas would be really appreciated.  I am considering trying the new apt functionality of reverting upgrades, if necessary, but since other systems do not have this problem (including my home desktop), I would like to actually find out what is wrong, so that I can eventually update it again.

finotti

#7
Trying to start plasma from the TTY with "startplasma-wayland", the same problem occur, but the only error I see is:

[  283.666868] amdgpu 0000:05:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data

Googling this error around, I saw suggestions of adding "amdgpu.dcdebugmask=0x10" to the grub configuration, but it had not effect...

Trying to restart the plasma shell from a running (broken) session (with "kstart plasmashell") has the same problem.  The back trace produce does not seem useful:

Starting debugger gdb --init-eval-command=set auto-solib-add off -nw -n -batch -x /tmp/drkonqi.accwsR -x /tmp/drkonqi.wriaaU -p 7163 /usr/bin/plasmashell

This GDB supports auto-downloading debuginfo from the following URLs:
  <https://debuginfod.debian.net>
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.
[New LWP 7219]
[New LWP 7218]
[New LWP 7213]
[New LWP 7212]
[New LWP 7211]
[New LWP 7210]
[New LWP 7209]
[New LWP 7208]
[New LWP 7204]
[New LWP 7203]
[New LWP 7202]
[New LWP 7201]
[New LWP 7200]
[New LWP 7199]
[New LWP 7198]
[New LWP 7197]
[New LWP 7196]
[New LWP 7195]
[New LWP 7194]
[New LWP 7193]
[New LWP 7192]
[New LWP 7191]
[New LWP 7190]
[New LWP 7183]
[New LWP 7182]
[New LWP 7181]
[New LWP 7180]
[New LWP 7178]
[New LWP 7177]
[New LWP 7176]
[New LWP 7175]
[New LWP 7174]
[New LWP 7173]
[New LWP 7172]
[New LWP 7167]
[New LWP 7166]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/x86_64-linux-gnu/libthread_db.so.1".
0x00007f79a6ca6efe in ?? () from /usr/lib/x86_64-linux-gnu/libc.so.6
Traceback (most recent call last):
  File "/usr/share/drkonqi/gdb/python/gdb_preamble/preamble.py", line 667, in print_preamble
    print_preamble_internal()
    ~~~~~~~~~~~~~~~~~~~~~~~^^
  File "/usr/share/drkonqi/gdb/python/gdb_preamble/preamble.py", line 641, in print_preamble_internal
    resolve_modules()
    ~~~~~~~~~~~~~~~^^
  File "/usr/share/drkonqi/gdb/python/gdb_preamble/preamble.py", line 621, in resolve_modules
    raise RuntimeError("No corefile found. Cannot resolve modules.")
RuntimeError: No corefile found. Cannot resolve modules.
No corefile found. Cannot resolve modules.
A debugging session is active.

Inferior 1 [process 7163] will be detached.

Quit anyway? (y or n) [answered Y; input not from terminal]
[Inferior 1 (process 7163) detached]
Sentry is attempting to send 2 pending events
Waiting up to 30 seconds
Press Ctrl-C to quit
Debugging ended with exit code '1' and exit status 'NormalExit'

EDIT: Here is the GDB back trace of the plasmashell core dump: http://luisfinotti.org/misc/plasmashell_bt.txt

Teriarch

Telling from the symbols included, the SEGFAULT in both cases is most likely triggered
by libfontconfig.so.1. Let's see if the library is up to date:
$ sudo updatedb
$ locate libfontconfig.so.1
$ dpkg -S libfontconfig.so.1
$ dpkg -l|grep libfontconfig1
What do we get?

finotti

Thanks for your help!

I get:

$ locate libfontconfig.so.1
/home/finotti/miniforge3/envs/sage/lib/libfontconfig.so.1
/home/finotti/miniforge3/envs/sage/lib/libfontconfig.so.1.17.0
/home/finotti/miniforge3/pkgs/https/conda.anaconda.org/conda-forge/linux-64/fontconfig-2.18.3-h4db4eae_1/lib/libfontconfig.so.1
/home/finotti/miniforge3/pkgs/https/conda.anaconda.org/conda-forge/linux-64/fontconfig-2.18.3-h4db4eae_1/lib/libfontconfig.so.1.17.0
/usr/lib/insync/libfontconfig.so.1
/usr/lib/x86_64-linux-gnu/libfontconfig.so.1
/usr/lib/x86_64-linux-gnu/libfontconfig.so.1.16.1
/var/lib/flatpak/runtime/org.freedesktop.Platform/x86_64/24.08/4ba2d4a7248a77f6510ffab405a729232105958d8347854ab8be74ec67229192/files/lib/x86_64-linux-gnu/libfontconfig.so.1
/var/lib/flatpak/runtime/org.freedesktop.Platform/x86_64/24.08/4ba2d4a7248a77f6510ffab405a729232105958d8347854ab8be74ec67229192/files/lib/x86_64-linux-gnu/libfontconfig.so.1.14.0
/var/lib/flatpak/runtime/org.gnome.Platform/x86_64/49/e51263e53d04900556e2f97ac2b27201f632f604d68d67f50323f9a99389fdb0/files/lib/x86_64-linux-gnu/libfontconfig.so.1
/var/lib/flatpak/runtime/org.gnome.Platform/x86_64/49/e51263e53d04900556e2f97ac2b27201f632f604d68d67f50323f9a99389fdb0/files/lib/x86_64-linux-gnu/libfontconfig.so.1.16.0
/var/lib/flatpak/runtime/org.kde.Platform/x86_64/5.15-25.08/1e9b0aa4623015cebd20350b36dc515124567b0f43c2235bd4ea8259fc2b18de/files/lib/x86_64-linux-gnu/libfontconfig.so.1
/var/lib/flatpak/runtime/org.kde.Platform/x86_64/5.15-25.08/1e9b0aa4623015cebd20350b36dc515124567b0f43c2235bd4ea8259fc2b18de/files/lib/x86_64-linux-gnu/libfontconfig.so.1.16.0

$ dpkg -S libfontconfig.so.1
libfontconfig1:amd64: /usr/lib/x86_64-linux-gnu/libfontconfig.so.1.16.1
insync: /usr/lib/insync/libfontconfig.so.1
libfontconfig1:amd64: /usr/lib/x86_64-linux-gnu/libfontconfig.so.1

$ dpkg -l|grep libfontconfig1
ii  libfontconfig1:amd64                                     2.17.1-5                                  amd64        generic font configuration library - runtime

Teriarch

O.K. Among all your different libfontconfig.so.1's let's see, which one is actually
used and make sure we are ont the same page:
$ ls -la /usr/lib/x86_64-linux-gnu/libfontconfig.so.1*
lrwxrwxrwx 1 root root    23  9. Feb 2026  /usr/lib/x86_64-linux-gnu/libfontconfig.so.1 -> libfontconfig.so.1.16.1
-rw-r--r-- 1 root root 325552  9. Feb 2026  /usr/lib/x86_64-linux-gnu/libfontconfig.so.1.16.1
$ md5sum /usr/lib/x86_64-linux-gnu/libfontconfig.so.1.16.1
df177294d29c8510e80ff422a1baafb2  /usr/lib/x86_64-linux-gnu/libfontconfig.so.1.16.1
$ md5sum /usr/bin/krunner
84f29ae5c6799cc29c61a19c50281e9f  /usr/bin/krunner
$ ldd /usr/bin/krunner|grep libfontconfig.so.1
libfontconfig.so.1 => /usr/lib/x86_64-linux-gnu/libfontconfig.so.1 (0x00007fb44a529000)
Does your output match?

finotti

Let's see.  The first three seem to match

$ ls -la /usr/lib/x86_64-linux-gnu/libfontconfig.so.1*
lrwxrwxrwx 1 root root     23 Feb  9  2026 /usr/lib/x86_64-linux-gnu/libfontconfig.so.1 -> libfontconfig.so.1.16.1
-rw-r--r-- 1 root root 325552 Feb  9  2026 /usr/lib/x86_64-linux-gnu/libfontconfig.so.1.16.1


$ md5sum /usr/lib/x86_64-linux-gnu/libfontconfig.so.1.16.1
df177294d29c8510e80ff422a1baafb2  /usr/lib/x86_64-linux-gnu/libfontconfig.so.1.16.1



$ md5sum /usr/bin/krunner
84f29ae5c6799cc29c61a19c50281e9f  /usr/bin/krunner

The last is slightly different:

$ ldd /usr/bin/krunner|grep libfontconfig.so.1
libfontconfig.so.1 => /usr/lib/x86_64-linux-gnu/libfontconfig.so.1 (0x00007f84bd529000)