Login screen changed today and i can only use icewm desktop environment now

English Install/Boot/Login
, ,
1

i booted my pc today and the login screen changed for some reason and it wont let me use any other desktop environment other than IceWM
for reference i used kde plasma before this happened
yes i’ve tried restarting
any tips?

2

Ad you did not run an update just before the shutdown? There must be a reason. Try to remember what happened. Also check an older snapshot.

3

heres my recent bash log

protontricks-launch --appid 1446780 /home/wago/windowsdesktop-runtime-8.0.14-win-x64.exe
protontricks-launch 1446780 /home/wago/Downloads/HunterPie-181-2-12-0-867-1745193393/HunterPie.exe
protontricks-launch 1446780 '/home/wago/Downloads/HunterPie-181-2-12-0-867-1745193393/HunterPie.exe'
protontricks-launchs --appid 1446780 /home/wago/Downloads/HunterPie-181-2-12-0-867-1745193393/HunterPie.exe
protontricks-launch --appid 1446780 /home/wago/Downloads/HunterPie-181-2-12-0-867-1745193393/HunterPie.exe
sudo rm -rf ./del/
ffmpeg -i Guilty\ Gear\ Isuka\ OST\ -\ Kill\ DOG\ as\ a\ Sacrifice\ to\ DOG\ \[FsZjnYoUUKs\].wav -vn -ar 44100 -ac 2 -b:a 192k killADog.mp3
ffmpeg
sudo zypper install ffmpeg
ffmpeg -i Guilty\ Gear\ Isuka\ OST\ -\ Kill\ DOG\ as\ a\ Sacrifice\ to\ DOG\ \[FsZjnYoUUKs\].wav -vn -ar 44100 -ac 2 -b:a 192k killADog.mp3
sudo chmod u+x xorg.conf.d/
sudo chmod 777 xorg.conf.d/
sudo chmod u+x /usr/share/screen-resolution-extra/nvidia-polkit
sudo chmod +x /usr/share/screen-resolution-extra/nvidia-polkit
xrandr 
xrandr --output HDMI-0 --set TearFree on
sudo flatpak install flathub org.nicotine_plus.Nicotine
touch ~/.icewm/prefoverride```
4

the snapshot named “openSUSE Tumbleweed (6.18.0-1,2026-03-04T08:30,pre,yast snapper)” seems to have reverted the login screen change and my desktop environment is back to normal when using it do oyu know if i can revert to this for default launch

5

I asked you if you did an update shortly before. You did not answer that question, but I assume that you indeed did and that that update created the snapshot. When booting that one redresses your problem that is of course fine for now. But you can not stay on that snapshot, not doing any updates anymore. You must try to find out what in that update caused the problem and then possibly file a bug report. Even when you can not pin iy down to a particular package, you still can file a bug report. And without any bug report it is unlikely to be repaired in a future update.

6

the thing is i didnt initiate an update it must of auto updated when i restarted or installed a package
and i dont really know where to start when trying to pin down which package caused the issue
the snapshot right after the one i mentioned has the bug and its labeled “post” so it might be where the bug is