Kde plasma 6.3.5, when the Settings menu was opened, scrolling the mouse wheel caused the desktop to crash

Support KDE Plasma
1

The specific manifestation is that the system Settings window closes unexpectedly, and Dr Konqi pops up a prompt asking to report the defect. When you open the application launcher and scroll the wheel, a similar problem will occur, but it will prompt a plasmashell crash. The following is my diary:

May 12 20:02:37 linux systemsettings[18303]: KCrash: Application 'systemsettings' crashing... crashRecursionCounter = 2

#2  0x00007bcb30d6fd47 _ZN6KCrash19defaultCrashHandlerEi (libKF6Crash.so.6 + 0x7d47)

#16 0x00007bcb3086d5f8 _ZN12QQuickWindow5eventEP6QEvent (libQt6Quick.so.6 + 0x26d5f8)

May 12 20:02:39 linux systemd[759]: Started Launch DrKonqi for a systemd-coredump crash (PID 18364/UID 0).

May 12 20:02:47 linux kwin_wayland[809]: kf.config.core: Watching absolute paths is not supported "/home/cxy/.local/share/color-schemes/WhiteSurDark.colors"

may 12 20:03:25 linux kwin_wayland[809]: kf.windowsystem: static bool KX11Extras::mapViewport() may only be used on X11

May 12 20:04:09 linux systemsettings[18820]: KCrash: Application 'systemsettings' crashing... crashRecursionCounter = 2

#2  0x00007d4dec1a5d47 _ZN6KCrash19defaultCrashHandlerEi (libKF6Crash.so.6 + 0x7d47)

#16 0x00007d4debc6d5f8 _ZN12QQuickWindow5eventEP6QEvent (libQt6Quick.so.6 + 0x26d5f8)

May 12 20:04:10 linux systemd[759]: Started Launch DrKonqi for a Systemd-core dump crash (PID 18880/UID 0).

May 12 20:04:19 linux kwin_wayland[809]: kf.config.core: Watching absolute paths is not supported "/home/cxy/.local/share/color-schemes/WhiteSurDark.colors"

May 12 20:07:30 linux kwin_wayland_wrapper[916]: I2025-05-12 20:07:30.198631 instance.cpp:1232] Running autosave...

May 12 20:07:30 linux kwin_wayland_wrapper[916]: I2025-05-12 20:07:30.234213 instance.cpp:1234] End autosave

May 12 20:12:53 linux systemsettings[20046]: KCrash: Application 'systemsettings' crashing... crashRecursionCounter = 2

#2  0x000078184854fd47 _ZN6KCrash19defaultCrashHandlerEi (libKF6Crash.so.6 + 0x7d47)

#16 0x000078184806d5f8 _ZN12QQuickWindow5eventEP6QEvent (libQt6Quick.so.6 + 0x26d5f8)

May 12 20:12:54 linux systemd[759]: Started Launch DrKonqi for a Systemd-core dump crash (PID 20107/UID 0).

May 12 20:13:22 linux systemsettings[20184]: KCrash: Application 'systemsettings' crashing... crashRecursionCounter = 2

#2  0x000076972db43d47 _ZN6KCrash19defaultCrashHandlerEi (libKF6Crash.so.6 + 0x7d47)

#16 0x000076972d66d5f8 _ZN12QQuickWindow5eventEP6QEvent (libQt6Quick.so.6 + 0x26d5f8)

May 12 20:13:24 linux systemd[759]: Started Launch DrKonqi for a Systemd-core dump crash (PID 20245/UID 0).

May 12 20:15:51 linux plasmashell[3233]: KCrash: Application 'plasmashell' crashing... crashRecursionCounter = 2

#2  0x0000759e39fd4d47 _ZN6KCrash19defaultCrashHandlerEi (libKF6Crash.so.6 + 0x7d47)

#16 0x0000759e38e6d5f8 _ZN12QQuickWindow5eventEP6QEvent (libQt6Quick.so.6 + 0x26d5f8)

May 12 20:15:54 linux systemd[759]: Started Launch DrKonqi for a systemd-coredump crash (PID 20665/UID 0).

May 12 20:15:54 linux drkonqi-coredump-launcher[20770]:                 #2  0x0000759e39fd4d47 _ZN6KCrash19defaultCrashHandlerEi (libKF6Crash.so.6 + 0x7d47)

May 12 20:15:54 linux drkonqi-coredump-launcher[20770]:                 #16 0x0000759e38e6d5f8 _ZN12QQuickWindow5eventEP6QEvent (libQt6Quick.so.6 + 0x26d5f8)

May 12 20:17:23 linux kwin_wayland[809]: kf.config.core: Watching absolute paths is not supported "/home/cxy/.local/share/color-schemes/WhiteSurDark.colors"
2 
sudo downgrade kirigami

from 6.14.0 to 6.13.0, the problem has been solved.

3

Wow, the start menu bug is much more serious. I usually do not scroll in there but it freezes the whole system for a bit. KDE Plasma releasing updates without proper checks is a reality i assume. We need to be wary.

4

Whereā€™s the Start Menu. I wasnā€™t aware KDE had one. I thought that was a Windows Anti Feature.

2 Likes
5

Kernel 6.13.12 is EOL for the the 6.13.x kernel. You would be better off going to 6.12.x as that series is LTS.

2 Likes
6

What you call ā€œapplication launcherā€ i call ā€œstart menuā€. I have a long history with windows so yeah, that is a start menu to me :slight_smile:

2 Likes
7

I notice that is an ARM issue, not x86.

8

Downgrading kirigami fixes it too.

9

I run Plasma 6, and I donā€™t have a Start Menu. I do however have an Application Dashboard.

Application Dashboard - 01
Application Dashboard - 011920Ɨ1080 145 KB

In order to get proper assistance with GNU/Linux, it pays to name things for what they are, not for what something with a similar appearance or functionality is called in an operating system that doesnā€™t even remotely have anything to do with UNIX. :wink:

2 Likes
10

Yep, Me Too.

I open mine by moving the Mouse pointer to the top LH corner of my screen.

1 Like
11

The issue is not architectural related: 503703 ā€“ With qt 6.9.0 simple scrolling crashes the apps (and plasmashell)

Qt 6.9 is at fault here. Also kirigami is known to have issues ā€¦

12

So weā€™re going to be skipping that, right? :stuck_out_tongue:

I could be wrong, but I seem to have read that theyā€™ve been working on Kirigami recentlyā€¦ :thinking:

13

Else they say revert of this: WheelHandler: smooth scroll for a greater variety of movement sizes (!1773) Ā· Merge requests Ā· Frameworks / Kirigami Ā· GitLab. Well we already ship Qt 6.9, hence the error. Also is the issue on x11 or wayland or both?

14

Iā€™m on Wayland and I am not experiencing any crashes. :man_shrugging:

What I am seeing is that scrolling sometimes abruptly halts and that you have to click or focus something else first in order to break out of the frozen menu.

15

I checked with KDE devs. Reverting WheelHandler: smooth scroll for a greater variety of movement sizes (!1773) Ā· Merge requests Ā· Frameworks / Kirigami Ā· GitLab seems safe. Arch devs are informed and KDE devs try to fix it. I can check later.

1 Like
16

However now the feedback is: someone says it doesn't fix the issue for them; hole on while we figure it out

So for now: donā€™t scroll. Who needs that anyway :smile:

ā€¦ lets see what the actual fix will be.

17

Same here. Iā€™ve noticed no issues.

18

Well, thereā€™s theā€¦ :point_down:

ā€¦ but thatā€™s not a crash, of course. Itā€™s more of a hiccup. :man_shrugging:

19

Yes I saw you had posted that comment, but no, Iā€™ve noticed no issues.

20

This is a fascinating decisionā€¦ especially when there is a much broader scope for launching applications in Linux than the one-horse show that is the Windows 95 Start Menu.

Technical ambiguity is the main reaction to your misnomerā€¦ and using ā€˜Start Menuā€™ labels you as a habitual Windows user in a foreign environment, which is very likely to invite condescension from Linux users who aspire to educate, use more precise terminology - especially when troubleshooting or giving instructions.

Regards.

2 Likes