its wayland and have been on vulcan for years , so doubt these would be causing plasmashell to crash , something wrong with plasmashell itself
it is the update on 23 but i am on wayland , and would really want to stay there
And you can - I just suggested it as a troubleshooting step…
sudo pacman -Syu plasma-x11-session
Then sign off, switch session type and sign on.
You can always switch session at the login manager - you can even remove the package afterwards - there are no repercussions.
1 Like
I learnt the hard way myself, so now I never update unless I’ve fixed all the issues first. Updating a broken system can make troubleshooting more difficult and in some cases hide the problem. Unless of course I can identify that the issue is fixed in the new version or I’ve exhausted all other avenues.
I’m afraid you will need to do the work yourself. You have two possible avenues – firstly, see if you can find anything related on KDE Discuss;
And then, search through confirmed bugs to see if any seem to explain what you’re experiencing – you might find that the issue has already been solved, if it is indeed a legitimate bug – otherwise, you will need to make a detailed report to KDE:
If the issue is with Plasmashell only, the best avenue to me is to switch to Unstable branch, update the system and see if the issue still occurs. Then you can switch back to Stable and wait for the next big Stable update.
Reporting the potential issue with Plasmashell to KDE, when you are out of date regarding the latest KDE updates is not really good option as the issue may already be fixed in current KDE (which is on Unstable, at least Stable is far behind).
2 Likes
i think this might have done the trick, last crash was 10 hours ago , switched to open gl as you suggested. i will monitor a bit more, then will give you the solution
1 Like
i marked your post as solution, it still crashes about once a day , switched to open gl , so i will wait for the update cycle , i think there is a problem with plasmashell, maybe a memory leak that hits harder when using vulkan, so running on open-gl for now
I removed the solution checkmark as that clearly didn’t completely solved your problem.
F.W.I.W.: I have a GTX 960 with Plasmashell, and I have absolutely no crashes during the day.
Try to see if you can spot some kind of pattern to the crashes. Do you have any cronjobs/systemd timers? Do the crashes happen when you do something specific? That kind of thing.
ok, thanks, i will keep looking then.
1 Like
sometimes they happen when i do something specific, like for example exit warthunder , but other time, when it was happening more frequently, i could not pin it down to anything, system would just be browsing , running vs-code or managing files, or doing nothing specific, and then it blinks out, usually the taskbar and the icons return, but sometimes i have restart plasmashell manually , so i have a terminal open for that , just in case.
now the cadence has been 1 a day, down from many an hour , so switching to open-gl definitely helped , but as you said, it is not a solution
i even put back a couple of widgets , and it is keeping a very low cadence , so yeah , keeping an eye
Another option, especially now that the Open GL has been changed is creating a new user and testing with that. If it doesn’t happen there, it’s something in your own directory and probably impossible for me to help track down. If, on the other hand, it continues to happen, it’s been narrowed down to either:
- a hardware issue; or
- something system-wide. In which case we…erm…maybe a reinstall would be easier than trying to track down the problem as a third party?
i have reinstalled plasmashell, and a couple of other kde related packages, the kernel usually dumps the offending peace of software, it only core dumps random apps if there is a ram issue, consistently dumping plasmashell can only indicate that something is wrong with plasmashell , i dont have systemd timer or any special cron jobs on my desktop, i do everything manually when i need them done , at the time of the crash for example, firefox was still running consuming 50 gigs of ram, it kept on running, only plasmashell got dumped … is there a pseudo package i can reinstall the latest plasma with , see if that may help?
It’s a meta-package, and while I’m sure there is, I don’t have it’s name.
However, I suddenly had a thought. Do you use Wayland or X11?
wayland, switched as soon as it was available, i deed to be on wayland now, x11 is dead to me
Then try, and post the output of:
journalctl --user --unit=kwin_wayland.service --no-pager --boot=-2
it comes back empty – No entries –
kinfo
Operating System: Manjaro Linux
KDE Plasma Version: 6.5.5
KDE Frameworks Version: 6.23.0
Qt Version: 6.10.2
Kernel Version: 6.19.2-1-MANJARO (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 3800X 8-Core Processor
Memory: 80 GiB of RAM (78.5 GiB usable)
Graphics Processor: AMD Radeon RX 580 Series
Hmm…
Then I’m honestly stumped!
Sorry.
i found this tho:
i did a journalctl --user --no-pager --boot=-5 | grep wayland
Feb 12 01:22:27 the-beast sddm[2091]: Reading from "/usr/share/wayland-sessions/plasma.desktop"
Feb 12 01:22:27 the-beast sddm[2091]: Session "/usr/share/wayland-sessions/plasma.desktop" selected, command: "/usr/lib/plasma-dbus-run-session-if-needed /usr/bin/startplasma-wayland" for VT 1
Feb 12 01:22:27 the-beast systemd-logind[1744]: New session '3' of user 'bogi' with class 'user' and type 'wayland'.
Feb 12 01:22:28 the-beast sddm-helper[2647]: Starting Wayland user session: "/usr/share/sddm/scripts/wayland-session" "/usr/lib/plasma-dbus-run-session-if-needed /usr/bin/startplasma-wayland"
Feb 17 10:43:30 the-beast sddm[2091]: Auth: sddm-helper (--socket /tmp/sddm-auth-7947a67d-930a-48ff-81c8-a6f58bb3d5cd --id 1 --start /usr/lib/plasma-dbus-run-session-if-needed /usr/bin/startplasma-wayland --user bogi) crashed (exit code 1)```