Hello all, I’m not sure it’s a graphics issue but seems to me .
I have Manjaro on this system last 2 years never had a problem. In NUC like box with Ryzen 9 Apu connected through DP.
After last week upgrade, after I log in I get the monitor to switch off and goes through all the inputs and then Manjaro starts with wallpaper and widgets but no system bar and icons.
If I do alt+F2 I can open settings or terminal but everything seems fine. This happens both in X or plasma (I always used plasma nicely).
Tried different kernels, couple of times solved it but the issue comes back. Also if I shut down it hangs on black screen on nvme drive and must use power button.
On same box I have win10 installed on another SSD and it’s fine.
I have the same Manjaro on a Dell intel laptop but that’s fine, upgraded too.
Anybody please lend advice? I don’t know what’s going on and system is unusable
Your Plasma configuration has gotten corrupted. It has happened to me twice as well in the last 3 months.
Switch to a tty, log in as yourself, and then issue the following commands…
sudo systemctl stop sddm
for fn in ~/.config/plasma* ; do mv $fn ~/.config/broken_$fn ; done
rm -f ~/.cache/*.kcache
sudo systemctl start sddm && exit
Now you can log in again, and from there on, reapply your customizations.
Once you’ve set everything up to your liking again, make sure to make a backup. A good way of saving your Plasma configuration is by way of konsave from the AUR…
pamac build konsave
However, the version in the AUR is not preconfigured for Plasma. You’ll have to open the file ~/.config/konsave/conf.yaml with a text editor, delete everything in the file, and then paste the entire content here-below into the file.
---
# This is the configuration file for konsave.
# This file is pre-configured for KDE Plasma users.
# This will backup all the important files for your Plasma customizations.
# Please make sure it follows the correct format for proper working of Konsave.
# The format should be:
# ---
# save:
# name:
# location: "path/to/parent/directory"
# entries:
# # these are files which will be backed up.
# # They should be present in the specified location.
# - file1
# - file2
# export:
# # This includes files which will be exported with your profile.
# # They will not be saved but only be exported and imported.
# # These may include files like complete icon packs and themes..
# name:
# location: "path/to/parent/directory"
# entries:
# - file1
# - file2
# ...
# You can use these placeholders in the "location" of each item:
# $HOME: the home directory
# $CONFIG_DIR: refers to "$HOME/.config/"
# $SHARE_DIR: refers to "$HOME/.local/share"
# $BIN_DIR: refers to "$HOME/.local/bin"
# ${ENDS_WITH="text"}: for folders with different names on different computers whose names end with the same thing.
# The best example for this is the "*.default-release" folder of firefox.
# ${BEGINS_WITH="text"}: for folders with different names on different computers whose names start with the same thing.
save:
configs:
location: "$CONFIG_DIR"
entries:
- gtk-2.0
- gtk-3.0
- gtk-4.0
- kate
- Kvantum
- latte
- dolphinrc
- katerc
- konsolerc
- kcminputrc
- kdeglobals
- kglobalshortcutsrc
- klipperrc
- krunnerrc
- kscreenlockerrc
- ksmserverrc
- kwinrc
- kwinrulesrc
- plasma-org.kde.plasma.desktop-appletsrc
- plasmarc
- plasmashellrc
- gtkrc
- gtkrc-2.0
- lattedockrc
- breezerc
- oxygenrc
- lightlyrc
- ksplashrc
- khotkeysrc
app_layouts:
location: "$HOME/.local/share/kxmlgui5"
entries:
- dolphin
- konsole
# Here are a few examples of how you can add more stuff to back up.
# Uncomment these lines if you want.
# firefox:
# location: "$HOME/.mozilla/firefox/${ENDS_WITH='.default-release'}"
# entries:
# - chrome # for firefox customizations
# code oss:
# location: "$CONFIG_DIR/Code - OSS/User/"
# entries:
# - settings.json
# The following files will only be used for exporting and importing.
export:
share_folder:
location: "$SHARE_DIR"
entries:
- plasma
- kwin
- konsole
- fonts
- color-schemes
- aurorae
- icons
- wallpapers
home_folder:
location: "$HOME/"
entries:
- .fonts
- .themes
- .icons
# You can add more files to export like this
# name:
# location: "path/to/parent/directory"
# entries:
# - file1
# - file2
# - folder1
# - folder2
...
Save the file, and then you can make a backup copy of your configuration, like so…
konsave -s my_plasma_configuration
You can of course choose a different name for your saved configuration. You can even save multiple configurations and switch between them on the fly. See…
yes, thanks for replying.
when I hit alt F2 for another tty it goes to login screen but hangs (only cursor moves). It’s strange as sometimes I can log in fine.
I posted system info in previous reply
Nowadays it is not to be taken for granted anymore that the Plasma session would be running at tty1. It varies between tty1 and tty2. So in order to get to an actual free tty with a login console, you have to press Ctrl+Alt+F3.
Alright did all that but on 2nd command it states that MV cannot work because there’s no such a directory.
I completed the other commands but when I logged in again it does the same thing: black screen cycling through all video outputs then as in 1st post
but after say 8-10 minutes it logs in but plasma seems messy: shows no connections, theen it connects to wifi but icon stays on disconnected
Is there a way to reset plasma without reinstalling manjaro?
this command
for fn in ~/.config/plasma* ; do mv $fn ~/.config/broken_$fn ; done
I did input all the lines you suggested but seems like nothing got reset
I don’t have wifi problems, it shows as not connected but it is. The wifi icon on the system bar shows as connected after a long while
That sounds like a stuck process — not with the WiFi itself, but with Plasma showing you that it’s connected.
Okay, once more, try this…
cd ~/.config
for fn in plasma* ; do mv $fn broken_$fn ; done
cd ~/.local/share
mv plasma plasma_broken
cd ~/.cache
rm -rf *
Do this from a tty while completely logged out of Plasma. If you cannot log out of Plasma due to it being stuck, log into the tty anyway and then first issue the command…
sudo systemctl stop sddm
Then execute the other commands here-above, and if you’ve had to stop sddm, then you must also restart it again, with…
Alright, did everything and had to reboot a couple of times until to get plasma at initial state. It was fine for a couple of boots and re customized it. But today it’s doing the same thing. Wallpaper on, no plasma, which appears 10 minutes later. It seems something more radical. Sometimes it hangs and everything goes black and white
Most likely, the cause is a no longer supported global theme. I would personally recommend not installing any global themes, but to customize the individual components instead, i.e. application theme, application color, window decorations, Plasma theme (panels and widgets), and so on.
Also always make a backup of your working configuration, so that you can restore it if things go wrong.
Ok I reinstalled Manjaro KDE from scratch, so far so good, still have to customize visuals but I have a question: could it be that I was using Wayland? I started to experience many lockups
That is possible. I do not know whether the recent installer images default to Wayland or not. I’m still on X11, and this system was installed in April 2019, which is quite a while ago.
Of course, I have kept it updated all along, but I’ve never had to reinstall, and as I consider Wayland a work in progress, I have therefore so far wisely declined to make the switch.
Sorry I didn’t explain myself. I was on Wayland previously and after last upgrade I started to have problems I outlined here, after 2 years. I also have Wayland on laptop and been fine.
I’m now on X as Manjaro defaults on it… after your answer I’ll keep it that way I think thanks