You are not logged in.
Operating System: Arch Linux
KDE Plasma Version: 5.20.2
KDE Frameworks Version: 5.75.0
Qt Version: 5.15.1
Kernel Version: 5.9.3-arch1-1
OS Type: 64-bit
You have to downgrade in order to login and deactivate autologin, and then you can upgrade but once you activate autologin again... it breaks again on a startup.
Offline
Confirm. It happen to me, I fixed by that way. I asked on kde reddit, and this is a bug report.
Offline
Bug report:
https://bugs.archlinux.org/task/68520
Edit: Its fixed now
Last edited by amish (2020-11-04 09:37:20)
Offline
Bug report:
https://bugs.archlinux.org/task/68520Edit: Its fixed now
No. It's not. I tried. But still error. Downgrade sddm again.
Offline
I'm curious, would it be possible to write an integration test to catch this?
Offline
Thanks for the report. I ran into the issue as well and can confirm that the bugfix did not fix resolve the issue and I downgraded back to 0.18 as well.
Offline
and what error are you still getting?
Offline
Those who still have problem, are you sure you upgraded to sddm 0.19.0-2 and not 0.19.0-1?
And also make sure to reboot the system. (I had to reboot)
My autologin is working fine with sddm 0.19.0-2 after a reboot
Last edited by amish (2020-11-04 14:13:58)
Offline
Those who still have problem, are you sure you upgraded to sddm 0.19.0-2 and not 0.19.0-1?
And also make sure to reboot the system. (I had to reboot)
My autologin is working fine with sddm 0.19.0-2 after a reboot
Ya. Now, it's ok. Maybe i was not clear pacman cache. I updated to 0.19-2. Now it's ok.
Bug fixed.
Offline
and what error are you still getting?
After reading through this thread once again, I realized that my issue is not the same, apologies for the miscommunication. I do not have autologin enabled and while SDDM did crash on bootup, I was able to open another virtual terminal and start it. However starting SDDM this way and then opening KDE Plasma makes the screen nonresponsive. However, I am still able to open another virtual terminal, start SDDM and more importantly, login using my other window manager, i3. So I believe that the bug lies with KDE Plasma. I will look into this in more detail in the coming days and open another bug report.
Those who still have problem, are you sure you upgraded to sddm 0.19.0-2 and not 0.19.0-1?
Yes, I did try with 0.19.0-2 as well and my issue persisted.
Update : Well, looks like I only had to reboot that was silly of me. Thanks for the tip!
Last edited by sriramsk1999 (2020-11-04 18:15:20)
Offline
My issue persists with sddm 0.19.0-2, after reboot. What I see happening is sddm starts, then X starts, then nothing starts. When I kill X everything continues, and I get the loginscreen for my desktop environment (plasma/kde).
Offline
I had the same problem, but could not even kill X or switch to another text console. Only a clean reboot via Strg+Alt-Del worked. Without autologin, sddm 0.19.0-2 starts cleanly.
For those running into problems even without autostart, there may be a different regression: https://bbs.archlinux.org/viewtopic.php?id=260525
Offline
I had the same problem, but could not even kill X or switch to another text console.
I have to switch to another console twice. System boots, and ends in a blank screen, nothing visible. I then switch to another console, nothing seems to happen, I switch back I get a mousepointer over a screen that shows the prompt for the dmcrypt-password (not the password, the prompt asking for one that I've obviously entered as the system booted on). Thén when I switch to a textconsole I can actually login, kill X and get a login for the graphical desktop.
Offline