Graphics platform crashes a lot

Help
1

Hi, as of the latest updates of KDE (from 5.25 to the more recent 5.27.5) keeps crashing on Debian Bookworm. My desktop has the same installation, but there it works fine.

Hint: You are currently not seeing messages from other users and the system.
Users in groups ‘adm’, ‘systemd-journal’ can see all messages.
Pass -q to turn off this notice.
PID: 4580 (drkonqi)
UID: 1000 (anticrust)
GID: 1000 (anticrust)
Signal: 11 (SEGV)
Timestamp: Fri 2024-11-15 12:33:21 CET (4 days ago)
Command Line: /usr/lib/x86_64-linux-gnu/libexec/drkonqi --platform wayland --appname plasma-discover --apppath /usr/bin --signal 11 --pid 4507 --appversion 5.27.5 --programname Ontdekken --bugaddress submit@bugs.kde.org --productname discover/discover
Executable: /usr/lib/x86_64-linux-gnu/libexec/drkonqi
Control Group: /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.kde.discover-3f303bee4a564a939cc461c8eb1cd4e5.scope
Unit: user@1000.service
User Unit: app-org.kde.discover-3f303bee4a564a939cc461c8eb1cd4e5.scope
Slice: user-1000.slice
Owner UID: 1000 (anticrust)
Boot ID: 966cabc0c57e487bbb87634c0f02014e
Machine ID: 6559aeeea60a42d4ae74a2b998afd225
Hostname: laptop
Storage: /var/lib/systemd/coredump/core.drkonqi.1000.966cabc0c57e487bbb87634c0f02014e.4580.1731670401000000.zst (missing)
Message: Process 4580 (drkonqi) of user 1000 dumped core.

            Module libsystemd.so.0 from deb systemd-252.31-1~deb12u1.amd64
            Module libudev.so.1 from deb systemd-252.31-1~deb12u1.amd64
            Stack trace of thread 4580:
            #0  0x00007f1a29aa9ebc n/a (libc.so.6 + 0x8aebc)
            #1  0x00007f1a29a5afb2 raise (libc.so.6 + 0x3bfb2)
            #2  0x00007f1a2bcb3b46 _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x5b46)
            #3  0x00007f1a29a5b050 n/a (libc.so.6 + 0x3c050)
            #4  0x00007f1a27fe2678 n/a (libwayland-client.so.0 + 0xb678)
            #5  0x00007f1a27fddbf8 n/a (libwayland-client.so.0 + 0x6bf8)
            #6  0x00007f1a27fde0a2 wl_proxy_marshal_array_flags (libwayland-client.so.0 + 0x70a2)
            #7  0x00007f1a27fde2be wl_proxy_marshal_flags (libwayland-client.so.0 + 0x72be)
            #8  0x00007f1a0c0b1aeb n/a (KF5IdleTimeWaylandPlugin.so + 0x6aeb)
            #9  0x00007f1a0c0b1137 n/a (KF5IdleTimeWaylandPlugin.so + 0x6137)
            #10 0x00007f1a0c0b1387 n/a (KF5IdleTimeWaylandPlugin.so + 0x6387)
            #11 0x00007f1a29d07cec _ZN9QHashData11free_helperEPFvPNS_4NodeEE (libQt5Core.so.5 + 0x107cec)
            #12 0x00007f1a0c0afda0 n/a (KF5IdleTimeWaylandPlugin.so + 0x4da0)
            #13 0x00007f1a0c0afdc9 n/a (KF5IdleTimeWaylandPlugin.so + 0x4dc9)
            #14 0x00007f1a29ea72b5 n/a (libQt5Core.so.5 + 0x2a72b5)
            #15 0x00007f1a29eab4af n/a (libQt5Core.so.5 + 0x2ab4af)
            #16 0x00007f1a29ea89d9 n/a (libQt5Core.so.5 + 0x2a89d9)
            #17 0x00007f1a29a5cff7 __cxa_finalize (libc.so.6 + 0x3dff7)
            #18 0x00007f1a29cafe07 n/a (libQt5Core.so.5 + 0xafe07)
            #19 0x00007f1a2bf1512a n/a (ld-linux-x86-64.so.2 + 0x112a)
            #20 0x00007f1a2bf1881e n/a (ld-linux-x86-64.so.2 + 0x481e)
            #21 0x00007f1a29a5d55d n/a (libc.so.6 + 0x3e55d)
            #22 0x00007f1a29a5d69a exit (libc.so.6 + 0x3e69a)
            #23 0x00007f1a29a46251 n/a (libc.so.6 + 0x27251)
            #24 0x00007f1a29a46305 __libc_start_main (libc.so.6 + 0x27305)
            #25 0x00005601f83b3121 n/a (drkonqi + 0x2c121)
            ELF object binary architecture: AMD x86-64

Usually my laptop starts fine and works fine, but frequently the graphical engine freezes up (both Wayland and X11)
I use my laptop mainly for data recovery and discforensics.

Can anybody please help me, I am no programmer, more a novice.

My laptop set up is a 32 GB AMD Ryzen 7 8865HS laptop (intergrated GPU ‘Phoenix 780M’), Running Debian 12 ‘Bookworm’ with Plasma 5.27.5

2

other crash logs

BlockquoteHint: You are currently not seeing messages from other users and the system.
Users in groups ‘adm’, ‘systemd-journal’ can see all messages.
Pass -q to turn off this notice.
PID: 3669 (appimagepool)
UID: 1000 (anticrust)
GID: 1000 (anticrust)
Signal: 6 (ABRT)
Timestamp: Tue 2024-11-19 13:29:22 CET (1h 10min ago)
Command Line: appimagepool
Executable: /app/appimagepool/appimagepool
Control Group: /user.slice/user-1000.slice/user@1000.service/app.slice/app-flatpak-io.github.prateekmedia.appimagepool-3651.scope
Unit: user@1000.service
User Unit: app-flatpak-io.github.prateekmedia.appimagepool-3651.scope
Slice: user-1000.slice
Owner UID: 1000 (anticrust)
Boot ID: c49eb81f4ae441c9a00f754f3e0ffe0f
Machine ID: 6559aeeea60a42d4ae74a2b998afd225
Hostname: laptop
Storage: /var/lib/systemd/coredump/core.appimagepool.1000.c49eb81f4ae441c9a00f754f3e0ffe0f.3669.1732019362000000.zst (missing)
Message: Process 3669 (appimagepool) of user 1000 dumped core.

            Stack trace of thread 10:
            #0  0x00007ff6ffbabd94 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x99d94)
            #1  0x00007ff6ffb5308e n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x4108e)
            #2  0x00007ff6ffb3a882 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x28882)
            #3  0x00007ff6e522e2d0 n/a (/usr/lib/x86_64-linux-gnu/GL/default/lib/libgallium-24.2.6.so + 0xa2e2d0)
            #4  0x00007ff6e5231730 n/a (/usr/lib/x86_64-linux-gnu/GL/default/lib/libgallium-24.2.6.so + 0xa31730)
            #5  0x00007ff6e4942181 n/a (/usr/lib/x86_64-linux-gnu/GL/default/lib/libgallium-24.2.6.so + 0x142181)
            #6  0x00007ff6e496560c n/a (/usr/lib/x86_64-linux-gnu/GL/default/lib/libgallium-24.2.6.so + 0x16560c)
            #7  0x00007ff6ffba9ddd n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x97ddd)
            #8  0x00007ff6ffc2e794 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x11c794)
            ELF object binary architecture: AMD x86-64
3

Hi - I’m also not a programmer, but I do have to advise you, Debian (by design) uses versions of KDE software that are out of date and no longer supported by KDE. This means it’s possible that the issues you’re experiencing exist only in Debian at this point, and that only Debian maintainers would be looking at crash logs for those versions.

It also looks like from your second set of logs that Flatpak applications are crashing as well beyond the core Plasma desktop environment, so there may be something broader going on after that upgrade.

One common troubleshooting step is to try creating a new user on the device having trouble, and seeing if you can reproduce the issues - if a new user doesn’t experience the same issues, then they are likely being caused by some combination of configurations under your existing user account. If a new user account does have the same issues, then it’s likely some combination of the installed system-level software.

Other folks here may have additional troubleshooting ideas, but you may also have some luck seeing if the Debian bug reporting process could help you there.

1 Like