Plasmashell crashes often

Hi Community,

Unfortunately, the KDE Plasma shell crashes very often at the moment (my system is up to date). Mostly when I click with the mouse on the kickstart bar and, for example, bring another program to the foreground. The crashes add up to 10 per hour when I am actively working.

Are these known problems with the plasma shell? There are several bug reports about the Plasma shell crashing. There are several bug reports about the Plasma shell crashing.

Is there anything I can actively do to minimize the crashes?

Here is the bug list for the plasma shell:
Plasmashell bugs

Is there anything I can actively do to minimize the crashes?

My system:
Operating System: KDE neon 6.0
KDE Plasma Version: 6.1.4
KDE Frameworks Version: 6.5.0
Qt Version: 6.7.2
Kernel Version: 6.8.0-40-generic (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-3770S CPU @ 3.10GHz
Memory: 15.5 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 4000

Greetings
Bluelupo

5 Likes

I’m also facing this on multiple machines.

3 Likes

Help fix the issue :laughing:

Users can’t solve crashes generally speaking, apart reporting them and updating to get fixes.

The simplest thing to do is to report the issue.
Crashes are simple to investigate.

Install gdb if not already done.
`coredumptctl -1 gdb
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
And let the process run until the end, type in ‘c’ when you get line :laughing:

--Type <RET> for more, q to quit, c to continue without paging--

This could be 491847 – Plasmashell Crash

If you have kcrash installed, then we might have telemetry for the crash.

3 Likes

I have activated the automatic crash report. Shortly afterwards, the plasma shell crashed again and the data was sent.

1 Like

I am also experiencing this issue, for example as I was writing this text it happened spontaneously, without me doing anything that could’ve triggered the bug.

  • It doesn’t impact performance very much, except for a slight drop in performance before the crash. I know about it only because the application bar disappears and the window of the current app stretches if it’s full-window, or the background goes black if it’s windowed.
  • Usually restarts itself in a matter of 10 seconds at most (unless I hit autoreport, at which it freezes - that’s a different thing though, that was here before this bug occurred, or at least I think so).
1 Like

Hi Tomsci,
I also noticed exactly the behavior you described. Let’s hope that the bug is fixed in the next release.

Greetings
Bluelupo

Auto-reporting bug is CPU intensive, especially the first time you use it unfortunately.

It launches a debugger to get a stacktrace and might need to download debug symbols along the way.
@sitter is making a blog serie detailing its inner-working.

According at 490791 – Metabug: many crashes in QWindowPrivate::connectToScreen() that arrive there by different means

It seems it will be fixed with Qt 6.7.4 and Qt 6.8.

1 Like

Please, please, please – change the topic’s title to indicate on which platform this is occurring.

  • Yes, in the KDE Bug Reporting system a search reveals that, there are 315 bugs reported related to Plasmashell crashing – the oldest dating back to 2017 – the newest confirmed bug reports are from this week.

But, please be aware that, not all system platforms are experiencing this issue – one has to be be carefully specific … :imp:

Hi meven, When will the versions you specified be released?

https://wiki.qt.io/Qt_6.7_Release
https://wiki.qt.io/Qt_6.8_Release

Beyond that your guess is as good as mine.
It might be fixed in Qt 6.7.3.
Then it depends on your distro, arch or neon will be within a week.

3 Likes

I am experiencing the same problem after upgrading to 6.1.4 yesterday. The crashing is severe and has disabled my computer. Plasmashell crashes ever 4 or 5 minutes sometimes every 30 seconds.

It crashes whenever I copy to the clipboard, whenever I minimize or maximize an app, whenever I open the launcher, whenever I try to edit the desktop. It even crashes without any user interaction.

Sometimes the crash reporter comes up, some times it does not and sometimes it comes up and it crashes as well.

I am writing this from my phone because KDE has disabled the pc.

How did this happen? Do KDE developers not do any basic testing before releasing updates? Does KDE not have any sort of validation process or procedures to review code before pushing it out? Has a rogue developer taken over KDE?

This is really a disillusioning.

Yes in the KDE community we test are software and uses it daily. Here this wasn’t a KDE software that’s causing the issue.

Still a KDE dev fixed Qt.

Unfortunately we don’t manage Qt release or distros packages.
KDE Plasma maintenance updates are monthly in contrast.

Yes, that’s called beta release. I would encourage anyone with the time to participate.
Arguably rolling release act as beta for release-based ones. So Kubuntu and Fedora users can thank Arch users.

Clearly it does not affect all users the same way, I have Arch with plasma 6.1.4 and Qt 6.7.2, and I am not sure I experienced it once.

Still this crash is still affecting users and the fix might not be before end of September unfortunately. Sorry it affects you. We can try to ship earlier.

Plasma is free-software developed by passionate devs, most of which are benevolent as I am. Stay mindful of your expectations.

3 Likes

If it helps, I am running KDE Neon 6.1.4, using Wayland and as of writing this the Qt version is 6.7.2

1 Like

I have now performed a restore (from August 14, 2024) on one of my PCs affected by the bug in Qt when Plasma version 6.1.3 and Qt version 6.7.2 were still installed. As a result, the Plasma shell no longer crashed.

Unfortunately, the bug in Qt (as posted by Meven) will probably not be fixed until September, a long time with such a serious bug.

This is my current software status after the restore
Operating System: KDE neon 6.0
KDE Plasma Version: 6.1.3
KDE Frameworks Version: 6.4.0
Qt Version: 6.7.2
Kernel Version: 6.5.0-45-generic (64-bit)
Graphics Platform: Wayland

As a workaround, each time you disconnect logout and log-in back-in. It should help prevent crashes, though that’s not great.

1 Like

You’re not on your own, seeing this on at least 3 unrelated machines at the moment.

1 Like

I have the same problem with KDE neon.
I already suspected the hardware and was about to replace it.
Lately KDE neon has become very unreliable.
I have now switched to EndeavourOs.
Despite the same Qt version, the OS runs well.

1 Like

am also having this issue, system info below

Operating System: EndeavourOS
KDE Plasma Version: 6.1.4
KDE Frameworks Version: 6.5.0
Qt Version: 6.7.2
Kernel Version: 6.10.6-arch1-1 (64-bit)
Graphics Platform: X11
Processors: 32 × AMD Ryzen 9 5950X 16-Core Processor
Memory: 62.7 GiB of RAM
Graphics Processor: AMD Radeon RX 6700 XT

happy to grab any info needed to help fix this

1 Like

Would it be possible for Neon to introduce a Qt package with the fix cherry-picked onto 6.7.2? Otherwise, could a Qt package with the fix be posted here? (I might look into building a Neon-style Qt package later when I have more time).

1 Like