Everytime I login (Tumbleweed/KDE), for the past couple of weeks, I get this message:
Anyone else.
Any fix?
Thanks.
Anyone else.
Any fix?
Thanks.
1 Like
Did you try:
Please report this error to help improve this software.
And the Report Bug button ?
1 Like
Tells me I canāt report bug:
But was basically wondering if it is a ājust meā issue, anywayā¦
You can report a bug manually to bugs.kde.org for plasma by providing the āDeveloper Informationā provided by this utility.
It does not matter if it is just you, plasmashell isnāt supposed to crash, on start.
You didnāt give any other information as to the circumstances this happens, so only the ādeveloper Informationā (i.e stack trace) will tell us what is this crash origin and will allow to determine how many users have encountered it.
Hi all,
some experiences from the last days/week from my side.
Iām using Plasma 6 on Fedora 41, Lenovo laptop Z13 Gen1.
Since two days, lot of crashes with plasmashell and some other crashes. Before it started, Iāve changed to GNOME session yesterday, coming back to Plasma, the language of the keyboard changed, crashes every 5 - 10 seconds of plasmashell, system asking for which backend to use (opengl, vulkan, ā¦). Problems partly solved by rebooting (keyboard language), but the issues with crashing plasmashell remains. A small overview:
Donāt know what to do, no problems with GNOME, crashes with Plasma and not rally usable. Sudden āblackoutsā of the display and recovering within 1-2 seconds, abrt-dialogue afterwards.
Does someone has similliar experiences at the moment? Of course, I can work with GNOME, but ā¦
BR
Bit
Make sure youāve updated to the latest plasma-workspace package, there was a bad issue with plasmashell couple weeks back. I was bad enough that I could not log into KDE at all so I worked around it by setting the login manager to GDM and I used KDE/Xorg instead of KDE/Wayland. The bug was wayland specific. Then an updated KDE plasma-workspace package came out that fixed it. This was on Fedora
Sorry to barge in. Itās not very clear by reading the message but do you have both Plasma and Gnome installed on the same Fedora installation?
Yes, have both on my TUMBLEWEED install, and always haveā¦
I see. The few times that I tried in the past (when X11 was still the default display server for Fedora) to install both DEs, I also had various issues, especially with the keyboard shortcuts not working in the Plasma session and setting mismatches, among other things. Evidently, Tumbleweed must handle something differently. I honestly thought it was unadvised to install both DEs alongside each other.
Same to me. Both installed on the laptop. Started with GNOME on F36, parallel installation of Plasma several months ago with F40. Not so much trouble until few weeks ago. In addition, Lenovo/Fedora is messing up device BIOS/UEFI nearly 3 times a week. Currently, dmesg asks me in the first lines of the output to report failed microcode installation. Lot of trouble with this device.
Yesterday, Iāve also had a plasmashell failure right after login.
BR
Bit
I havenāt seen this one for a long time.
I did have a niggly problem with icons, not only resetting their position - but also not showing custom icons until after I select, context menu and escapeā¦
Anyway, as always, most Plasma bugs are PEBCAK bugs - so the first couple of steps are these:
- Create TEST user, log in, test it thereā¦ usually thatās clear - and if it isnāt, then itās not your files or settings (so itās a real problem).
- Post here, give any information requested - inxi/journals etc to find out the problem.
If TEST user was clear, then thereās no bug - so you can now rename your .config to .configFORKED and log out/in to see if THAT clears it.
If that does clear it, then copy back piece by piece.
My latest problem was something Plasma didnāt like in my plasma-org.kde.plasma.desktop-appletsrc - so basically I got most of my config back, then had to set up panels/desktop slideshow and mouse actions and Iām good to goā¦
You can try to be more targeted and organised (configās a big folder) like this:
mv .config/plasma* ~/.config/backup_plasma/
mv ~/.config/kdeglobals ~/.config/backup_kdeglobals
However, Iām clumbsy - I just move the whole thing - then select and move MOST things back (nearly all folders are safe anyways) and after doing a quick log out/in again, Iāll move half whatās left - doesnāt take more than 3-4 goes at best to have it narrowed down; just make sure you count/remember the last bunch movedā¦ as youāll be wanting to move half that back if you canāt start making good guesses.
Hi ben2talk,
your suggestion of using a test user makes me smile: Iāve tested an existing administration account (never used with Plasma) on my laptop. And? No more crashes in plasmashell, itās running perfectly as my personal account was before.
Thanks for the tipp. Now itās on me to grab for differences and error sources.
BR
Bit
Differences Iāve directly recognized are with the application bar (colours) and some minor differences. But itās working as before
1 Like
Ummmā¦
Would appear that whatever it was, has been fixedā¦?
Just did an update, and noticed there were several āplamaxxxā updates.
workspace/desktop/session/addonsā¦
All good.
Iāve had an update (a big one including firmware, microcode etc, approx. 2 Gb in total) before the crash of plasmashell starts repeatedly. Update was progressing in background and I remember that I didnāt reboot before changing to GNOME and finally back to Plasma. Maybe this was the error? But ok, I was able to restore most of my configs. Iām using Plasma nearly right out of the box, only some minor changes were necessary. But I also noticed that Snapper was not logging correctly because I didnāt respect migration from dnf4 to dnf5 in F41 meaning to easy rollback was possible.
Up to now, nearly everything is running smooth.
BR
Bit