I installed Kinoite today, and things worked fine directly after the install. After executing rpm-ostree upgrade and rebooting, the login screen isn't shown - instead the mouse cursor is shown on a black screen for a second, then the screen goes black. I can still log in with other TTYs.
rpm-ostree upgrade
The problem doesn't seem to be related to GPU drivers - it occurs exactly the same, whether I try to use Kinoite or Universal-Blue kinoite-nvidia.
To Reproduce
Please describe the steps needed to reproduce the bug: 1. Install Fedora Kinoite from Fedora-Kinoite-ostree-x86_64-39-1.5.iso and reboot. Observe that the system works. 2. Either execute sudo rpm-ostree upgrade in a terminal, or run the normal GUI updater 3. Reboot and select the new entry Fedora Linux 39.20240116.0 in Grub. The login screen isn't shown.
sudo rpm-ostree upgrade
Fedora Linux 39.20240116.0
The login screen should be shown as usual instead of a black screen.
State: idle BootedDeployment: â— fedora:fedora/39/x86_64/kinoite Version: 39.20240116.0 (2024-01-16T00:50:47Z) Commit: 8c7cf074576054a4ed47a39b45c7f0694c2be078837ef4840d906215aaa3a704 GPGSignature: Valid signature by E8F23996F23218640CB44CBE75CF5AC418B8E74C
(the dot before fedora:fedora is shown properly in the terminal)
I think the problem is related to kwin_wayland - journalctl shows: Jan 16 17:11:05 fedora systemd-coredump[1545]: Process 1391 (kwin_wayland) of user 981 dumped core. Since I couldn't figure out how to attach the log here, I uploaded it to Pastebin instead: https://pastebin.com/PvcF87te
Jan 16 17:11:05 fedora systemd-coredump[1545]: Process 1391 (kwin_wayland) of user 981 dumped core.
I attempted to get a backtrace, this is all gdb gives me:
#0 0x00007f3b9c0c6940 in ?? () #1 0x00007f3b6dffaa50 in ?? () #2 0x00007f3b961d9b3c in lp_fs_linear_run () from /usr/lib64/dri/kms_swrast_dri.so Backtrace stopped: previous frame inner to this frame (corrupt stack?)`
I tried getting it as described here, but it doesn't crash - though it replaces the TTY terminal, and still doesn't show anything.
Please let me know if I can provide any further information!
The problem doesn't occur if I force SDDM to use X11 as described here.
Update: The problem also doesn't occur if I disable the integrated graphics card in the UEFI.
This looks like a kwin bug that should be reported upstream. The easiest way to get a full backtrace might be to install a classic KDE Spin for now. Otherwise you should be able to use gdb or coredumpctl to get the coredump and then get the debug symbols.
Metadata Update from @siosm: - Issue tagged with: kinoite, nvidia
Can you confirm that you GPU is an NVIDIA one?
Edit: Apparently from the log it's all AMD.
Is this a Framework? There have been issues that are fixed with a firmware update.
Metadata Update from @siosm: - Issue untagged with: nvidia
Sorry, I should have specified the hardware - it's a custom-built desktop with an AMD CPU and an NVIDIA GPU.
I will try to do so if another issue arises. For now I don't want to modify things too much, and since dual boot isn't supported I'm afraid to break the installation. Thank you!
Metadata Update from @siosm: - Issue tagged with: nvidia
Sorry, I should have specified the hardware - it's a custom-built desktop with an AMD CPU and an NVIDIA GPU. I will try to do so if another issue arises. For now I don't want to modify things too much, and since dual boot isn't supported I'm afraid to break the installation. Thank you!
@timonlukas Could you confirm if you're still seeing this issue? If not, please let us know if we can close this issue. A lot has changed in regard to NVIDIA in the last couple of months with the release of 555 driver
This is now fairly old and a lot has changed since. Please comment here or create a new issue if you can still reproduce it on latest Kinoite. Thanks
Metadata Update from @siosm: - Issue close_status updated to: Can't fix - Issue status updated to: Closed (was: Open)