I’m having some odd issues. When I log in, plasmashell crashes, tries restarting for a bit, then gives up. Settings can’t launch either, nor most plasma-related apps. I’m able to see my desktop wallpaper and shortcuts for just a moment, but they disappear in moments. Certain apps (well, just discord for now) don’t freeze, but become unresponsive to the cursor. I’m having trouble listing files too. I can’t open dolphin at all, and when I try to browse them in the terminal instead, using the “ls” command in certain directories causes konsole to crash. I’m still able to open windows from terminal, and do things like snap them to position, and switch between virtual desktops.
I worked with a friend to narrow things down, but we weren’t able to figure out the root cause ultimately. We did discover that the files I was having trouble with are accessible when logged in via tty. And when another user is logged in, there are no problems at all. We tried initializing my config files for plasma, but it didn’t change anything. We think the source of the issue has to be in my home directory somewhere, but it’s not in the obvious places.
Here’s my system information:
Operating System: Fedora Linux 44
KDE Plasma Version: 6.7.5
KDE Frameworks Version: 6.30.0
Qt Version: 6.11.2
Kernel Version: 7.2.4-200.fc44.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 5600 6-Core Processor
Memory: 32 GiB of RAM (31.3 GiB usable)
Graphics Processor: AMD Radeon RX 580 Series
Any help to get to the bottom of this is appreciated!
We will need more details to try and understand what is happening.
Type Ctrl-Alt-F3 and login to the console. From the console you will be able to look at the user journal.
What does this report after you have seen the crash?
journalctl -b 0 --user -g kwin
Also have a look at the system journal for gpu errors after you have seen the crash.
sudo journalctl - b 0 -g amdgpu
You can also try creating a new user and then login as that new user.
Does plasmashell crash for the new user?
To create a user from the console
sudo useradd testuser
sudo passwd testuser
(edit fix passwd)
If the plasmashell does not crash for the new user that suggests you have a bad seeing in your user’s config.
I think if you rm .config/plasmashellrc then login that may help.
As for the test user thing, as mentioned in the first post, a fresh account can indeed run plasma with no issue. I tested it again just to make sure and that’s still the case. I’m sure you’re right that something is going wrong with my user config somehow, but simply removing .config/plasmashellrc doesn’t seem to change anything.
Alright. Thank you for pointing me to them. I’m still pretty much a beginner, so it’s hard to know to what extent this is just user error without a second opinion.
I have the same problem after updating. It looks like there are some bugs with the font cache. Deleting the cache folder with rm -rf ~/.cache/fontconfig fixes the problem temporarily, until the problematic cache is created again.
I do have Chromium browser installed. But I don’t use it. I don’t even remember the last time I opened it. At the next boot, I will try to run chromium and see if that causes any issues.
Having exactly the same issue. For me the root cause is helium browser (which I believe should be a ungoogled-chromium downstream). Same issue is triggered by google chrome. See this issue.
And it’s kind of strange that chromium from Fedora is working just fine. The chromium version of the 3 browsers tested are all 154.0.8037.57. Not sure what magic Fedora did when building chromium, but it’s working for me.
