Right, nothing so far. Have also cleared the KDE cache. I don’t know where else to look
@Spam If you create a test user and log in as that test user, does that work?
Definetly an issue within my home directory. The test user works fine on Wayland.
A user config issue (often theming related). These are some of the common culprits…
~/.config/plasma-org.kde.plasma.desktop-appletsrc
~/.config/plasmashellrc
~/.config/kscreenlockerrc
~/.config/kwinrc
Unfortunately it can be a bit tedious to track down. You’ll need to log in as the affected user on a VT (Ctrl+Alt+F3) and move a few files out of the way:
mv ~/.config/kwin* ~/kwin-backup/
mv ~/.config/plasma* ~/plasma-backup/
mv ~/.local/share/kscreen ~/kscreen-backup
mv ~/.config/kglobalshortcutsrc ~/kshortcuts-backup
Then try logging in to a graphical Plasma Wayland session as that user.
If it works, you can either re-apply your theme/configuration from scratch, or restore the moved files one by one to identify which one was breaking the session.
Thanks!
I already tried doing it with the entire .config/ and .local/ folders. It still didn’t work, which I find extremely odd.
But yeah, all those you mentioned are in either one or the other.
Honestly considering making a completely new user and gradually migrate home/ over there, but not particularly thilled about the prospect.
It might be due to broken environment files in home directory (~/.profile
or ~/.bashrc) perhaps?
Or something problematic in the user’s ~/.cache directory? You can remove that safely if required,
That was it, .bashrc!
I had set export DISPLAY=:0.0 
I don’t remember why I had to do that.
Ok, thanks for the update. Glad to have been of guidance.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.