Problem: After entering password and confirm in sddm, system will show blank screen with cursor and get stuck here. If set autologin then system will directly get stuck in black screen with cursor. Reboot does not fix it.
Way to Bypass: 1. switch to tty and 'sudo pkill X' to kill Xorg and sddm will restart and this time can login. It is said that use 'systemctl' to restart sddm may also work but I have no tried because of something I will mention later. 2. When booting to grub choose former ostree deployment and this problem will not happen. I have met with this problem for about 3 times. It happens after updating or installing new rpm packages, BUT IT IS NOT BECAUSE OF THE PACKAGES INSTALLED THEMSELVES for reasons below. 3. Just try installing some more new rpm packages and this problem may just disappear. 4. Rollback and then re-update or re-install the packages that have broken kde/sddm login, very likely that this problem will not happen and everything is just fine. Combining such clues I think this problem only occurs at certain ostree deployment. Whatever I do, just to escape current ostree deployment and such problem can disapear. 5. in tty 'startx' can start kde when get stuck
Other Clue: 1. Black screen with cursor is a well-known bug of sddm, see https://wiki.archlinux.org/title/SDDM However on archwiki it reports that black screen bug happens before sddm greeter starts but on Kinoite it is stuck after login. 2. I talked about this problem with friends to tell whether it is about sddm or about kde. They advised me to see 'ps' when stuck to tell whether kde is start. But I managed to escape from the problematic ostree deploy and forgot to pin it so I cannot try it until I meet such problem next time, and I will try 'systemctl restart' too.
Current advice for Kinoite group: 1. To add a package in repo or even pre-installed that make a systemd service to autokill Xorg when get stuck. Here may need some point to detect whether it is stuck, maybe timing? 2. Seem that this bug has something to do with both kde/sddm and rpm-ostree, so please try to tell whether it is a kde bug or sddm bug ( I cannot study about it till I meet this bug next time ) and you can contact with sddm group for 'blank screen with cursor' is such a well-known problem of sddm.
FInally, my system information: OS: Fedora 36 Kinoite CPU: AMD Ryzen 5900HX GPU: Radeon / RTX 3070 mobile rpm-ostree statues: State: idle Deployments: ● fedora:fedora/36/x86_64/kinoite Version: 36.20220727.0 (2022-07-27T01:21:10Z) BaseCommit: 3217dbb7dc0b19fbc43d4ecfabd80c0c550886c0359e20b39709f88defbdf926 GPGSignature: Valid signature by 53DED2CB922D8B8D9E63FD18999F7CBF38AB71F4 LayeredPackages: acpid akmod-nvidia dnf fcitx5-qt gnome-boxes libvirt snapper spice-protocol spice-server tlp virt-manager xorg-x11-drv-nvidia-cuda LocalPackages: expressvpn-3.28.0.6-1.x86_64 rpmfusion-free-release-36-1.noarch rpmfusion-nonfree-release-36-1.noarch
Thanks
@siosm If I meet this bug next time I will remember to try understanding more. Could you please pay attention to related problem and tell those have similar problem to contact with me. Thanks.
In short my advice to users with such problem: 1. sudo killall Xorg 2. rollback or update or install packages to get out of current ostree deployment
Metadata Update from @siosm: - Issue tagged with: kinoite
Metadata Update from @siosm: - Issue tagged with: nvidia
Sorry, I don't have an NVIDIA card and I don't use Xorg anymore so I won't be able to investigate.
I just installed Fedora Kinoite 37 (beta) and I seem to hit this issue. When I reboot I'm just presented by black screens. Simply restarting sddm using systemctl fixes the issue.
In the journal log I can see it fails on:
zář 26 11:12:15 fedora.home sddm-helper[1517]: Starting X11 session: "" "/usr/bin/sddm-greeter --socket /tmp/sddm-:0-cRcmQr --theme /usr/share/sddm/themes/01-breeze-fedora" zář 26 11:12:15 fedora.home sddm-greeter[1533]: could not connect to display :0 zář 26 11:12:15 fedora.home audit[1533]: ANOM_ABEND auid=4294967295 uid=976 gid=975 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 pid=1533 comm="sddm-greeter" exe="/usr/bin/sddm-greeter" sig=6 res=1 zář 26 11:12:15 fedora.home sddm-greeter[1533]: Could not load the Qt platform plugin "xcb" in "" even though it was found. zář 26 11:12:15 fedora.home sddm-greeter[1533]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem. Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb.
Given restarting SDDM does make it work, there is possibly some wrong order and SDDM just starts too early and fails on that? I'm not really an expert in this field.
@ngompa what do you think?
I just installed Fedora Kinoite 37 (beta) and I seem to hit this issue. When I reboot I'm just presented by black screens. Simply restarting sddm using systemctl fixes the issue. Given restarting SDDM does make it work, there is possibly some wrong order and SDDM just starts too early and fails on that? I'm not really an expert in this field. @ngompa what do you think?
That sounds plausible, this needs to be forwarded to SDDM upstream, though.
I find it unlikely to be a Kinoite only issue (but it could be). Installing a classic KDE Spin and confirming that this does not happen there would be great.
This started happening to me as well now. It doesn't seem to be related to specific deployment in my case. I did a rebase to F37 and few updates till this started happening, but it's still happening.
The workaround with killing X session and starting it manually works:
$ sudo pkill X $ startx
I think this issue might be gone with some recent update, I didn't see this issue lately.
It's still happening on my machine.
And this is in journalctl (but I'm not sure if this is related)
lis 08 18:46:22 fedora unix_chkpwd[1409]: could not obtain user info (sddm) lis 08 18:46:22 fedora unix_chkpwd[1410]: could not obtain user info (sddm) lis 08 18:46:22 fedora systemd[1408]: PAM failed: Authentication service cannot retrieve authentication info lis 08 18:46:22 fedora systemd[1408]: user@976.service: Failed to set up PAM session: Operation not permitted lis 08 18:46:22 fedora systemd[1408]: user@976.service: Failed at step PAM spawning /usr/lib/systemd/systemd: Operation not permitted lis 08 18:46:22 fedora systemd[1]: user@976.service: Main process exited, code=exited, status=224/PAM lis 08 18:46:22 fedora systemd[1]: user@976.service: Failed with result 'exit-code'. lis 08 18:46:22 fedora systemd[1]: Failed to start user@976.service - User Manager for UID 976.
And then coredump from sddm-greeter:
lis 08 18:46:22 fedora sddm-greeter[1411]: Loading file:///usr/share/sddm/themes/01-breeze-fedora/Main.qml... lis 08 18:46:22 fedora systemd-coredump[1439]: [🡕] Process 1425 (xdg-document-po) of user 976 dumped core.
Login to comment on this ticket.