I just fresh installed EOS plasma with Btrfs with encryption from latest ISO. After updating the packages it is showing me this screen.
I haven’t changed anything at all.
Is this known issue to the developers?
Hmm, normally KDE will rollback to a previous version but since this a new install…
I know this might be a hassle but if you re-install offline does the same occur afrer updating?
I know this might be a hassle but if you re-install offline does the same occur afrer updating?
I installed this with Offline mode only. It worked as expected, this happened only after updating the packages.
Ok, I don’t want to update to test now but since you are in this state does changing the theme make it work? Or using another 3rd party theme? (Just don’t want to risk it as just starting a something)
EDIT - I will be updating but not til I work something out
1 Like
I think possible to reproduce this from live-iso?
As the screen suggested I tried Ctrl+Alt+F2 it showed me the login screen but I couldn’t login from there. Keyboard didn’t work. So I simply rebooted the system, now all seems okay.
Is it still like this after a reboot? I would also check up recent bug reports to make sure it is a solved issue or even reported as it may be new or only releated to the disto
Nope, no such “screen locker” broken message after the reboot and I didn’t even follow any of the mentioned instructions.
I think it might already be fixed but this is just a guess what I would do since you can log in is run another u[date later and I would think it should be resolved. If this doen’t happen report it so it can be worked on
1 Like
I just logout and tried Ctrl+Alt+F1.
It’s showing a black/blank console screen with blinking cursor, where typing doesn’t work. What kind of TTY is this?
Ctrl+Alt+F2 works as the GUI login screen.
Before I ask anything more is there a reason you are logging in this way? I thought you had solved it before… (was probably me mistunderstanding)
1 Like
Yes it’s solved. Just testing why tty1 doesn’t work and if it’s a bug and if I should report it to eos-iso developers.
It doesn’t give good 1st impression to new EOS users so…
After updating but before rebooting right?
I think that’s the intended behavior because plasma has just been updated and without rebooting some services are not working.
1 Like
Was going to reply proper, not you can do the work as it not affecting me and I am on limited data. Re-install in a vm - if same issue - report it. If not you just installed at an unforyutate time, not having a go and would normally try my data is just too slow at the moment to try anything
1 Like
After updating but before rebooting right?
Yes.
Ok, so as I said, the behavior is expected
These 2 are the concerning issues. It doesn’t affect the over all desktop experience as you can login from tty2. I just wanted to point out these little inconveniences for devs.
If possible I’ll test on VM later.
FWIW I had the same experience: (I have a v old intel only laptop.) Did a hard shutdown, logged in using xfce, rebuilt my AUR packages using
yay -S --rebuildall $(pacman -Qm)
(takes a long time and requires several admin passwords), rebooted and logged in using wayland and all is well.
Wiser folk will know which packages I should have rebuilt rather than doing the whole lot!