Black Screen after logout

Rebased from F35 Kinoite to F36. Login to desktop works okay. When I logout, I get a black screen on both my monitors and they go to sleep. Pressing keys or mouse movement does not wake it up and I cannot log back into the desktop. I am using the NVidia proprietary drivers from RPM Fusion with X11. Had to rollback to F35 and all is working well again with the NVidia drivers. Anyone else seen this behavior?

Edit: Here are my system details

rpm-ostree status
State: idle
AutomaticUpdates: stage; rpm-ostreed-automatic.timer: no runs since boot
Deployments:
â—Ź fedora:fedora/36/x86_64/kinoite
                   Version: 36.20220515.0 (2022-05-15T00:42:39Z)
                BaseCommit: da506619ffcff9fd4d754d86abf932fd6d34bc99f616699939574a43c52885c7
              GPGSignature: Valid signature by 53DED2CB922D8B8D9E63FD18999F7CBF38AB71F4
           LayeredPackages: akmod-nvidia arm-image-installer fedora-workstation-repositories ffmpeg fish gnome-tweaks kde-connect powerline-fonts pulseview
                            rpmfusion-free-release rpmfusion-nonfree-release sigrok-firmware-fx2lafw stlink virt-install virt-manager virt-viewer xorg-x11-drv-nvidia


uname -r
5.17.6-300.fc36.x86_64

cat /proc/cmdline
BOOT_IMAGE=(hd2,gpt2)/ostree/fedora-0eb8087f8058184b99815a30e7940ea3da476c5f09305e009f5a4a9dfec906a7/vmlinuz-5.17.6-300.fc36.x86_64 rhgb quiet root=UUID=86cf0e5e-bca2-4fbe-b315-565c385f419b rootflags=subvol=root ostree=/ostree/boot.1/fedora/0eb8087f8058184b99815a30e7940ea3da476c5f09305e009f5a4a9dfec906a7/0 mitigations=off rd.driver.blacklist=nouveau modprobe.blacklist=nouveau nvidia-drm.modeset=1

rpm -qa | grep nvidia
xorg-x11-drv-nvidia-kmodsrc-510.68.02-1.fc36.x86_64
xorg-x11-drv-nvidia-cuda-libs-510.68.02-1.fc36.x86_64
xorg-x11-drv-nvidia-libs-510.68.02-1.fc36.x86_64
nvidia-settings-510.68.02-1.fc36.x86_64
xorg-x11-drv-nvidia-power-510.68.02-1.fc36.x86_64
xorg-x11-drv-nvidia-510.68.02-1.fc36.x86_64
akmod-nvidia-510.68.02-1.fc36.x86_64

lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06)
01:00.0 VGA compatible controller: NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] (rev a1)

2 Likes

I’m experiencing a similar issue here: rpmsoftwaremanagement/rpm-gitoverlay-1557737067.379652

For me, login to desktop doesn’t work but unlocking after suspend works.

Here are some logs from when it locked up. Looks like Xorg crashed maybe.

May 15 14:58:05 mustang systemd[1]: run-user-982.mount: Deactivated successfully.
May 15 14:58:05 mustang systemd[1]: user-runtime-dir@982.service: Deactivated successfully.
May 15 14:58:05 mustang systemd[1]: Stopped user-runtime-dir@982.service - User Runtime Directory /run/user/982.
May 15 14:58:05 mustang audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=user-runtime-dir@982 comm="systemd" e>
May 15 14:58:05 mustang systemd[1]: Removed slice user-982.slice - User Slice of UID 982.
May 15 14:58:27 mustang kernel: watchdog: BUG: soft lockup - CPU#1 stuck for 27s! [Xorg:3279]
May 15 14:58:27 mustang kernel: Modules linked in: snd_seq_dummy snd_hrtimer nft_objref nf_conntrack_netbios_ns nf_conntrack_broadcast nft_fib_inet nft_fib_ipv4 nft_fib_i>
May 15 14:58:27 mustang kernel:  snd_timer snd soundcore acpi_pad zram dm_multipath hid_logitech_hidpp hid_logitech_dj i915 mxm_wmi crct10dif_pclmul crc32_pclmul crc32c_i>
May 15 14:58:27 mustang kernel: CPU: 1 PID: 3279 Comm: Xorg Tainted: P           OEL    5.17.6-300.fc36.x86_64 #1
May 15 14:58:27 mustang kernel: Hardware name: Gigabyte Technology Co., Ltd. Z97X-Gaming 7/Z97X-Gaming 7, BIOS F8 09/18/2015
May 15 14:58:27 mustang kernel: RIP: 0010:os_io_read_dword+0x8/0x10 [nvidia]
May 15 14:58:27 mustang kernel: Code: 40 00 0f 1f 44 00 00 89 fa ec c3 cc 66 0f 1f 44 00 00 0f 1f 44 00 00 89 fa 66 ed c3 cc 0f 1f 44 00 00 0f 1f 44 00 00 89 fa ed <c3> c>
May 15 14:58:27 mustang kernel: RSP: 0018:ffffb0a681793b78 EFLAGS: 00000202
May 15 14:58:27 mustang kernel: RAX: 00000000af0c9320 RBX: 00000000000017ea RCX: 00000000000c0000
May 15 14:58:27 mustang kernel: RDX: 000000000000e00c RSI: 00000000000c43ec RDI: 000000000000e00c
May 15 14:58:27 mustang kernel: RBP: ffff9c7ec0702c00 R08: ffffffffc3080340 R09: 0000000000000282
May 15 14:58:27 mustang kernel: R10: 0000000000000202 R11: 0000000000000001 R12: ffff9c7ec0702c68
May 15 14:58:27 mustang kernel: R13: ffff9c7ec0702c64 R14: 000000000000c000 R15: 000000000000c000
May 15 14:58:27 mustang kernel: FS:  00007f98fbedafc0(0000) GS:ffff9c811fa40000(0000) knlGS:0000000000000000
May 15 14:58:27 mustang kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
May 15 14:58:27 mustang kernel: CR2: 0000555f35e198e0 CR3: 0000000161284004 CR4: 00000000001706e0
May 15 14:58:27 mustang kernel: Call Trace:
May 15 14:58:27 mustang kernel:  <TASK>
May 15 14:58:27 mustang kernel:  _nv039083rm+0x4c/0x70 [nvidia]
May 15 14:58:27 mustang kernel:  ? _nv000753rm+0x4f/0x130 [nvidia]
May 15 14:58:27 mustang kernel:  ? _nv030048rm+0x14c/0x200 [nvidia]
May 15 14:58:27 mustang kernel:  ? _nv038086rm+0x2a/0x80 [nvidia]
May 15 14:58:27 mustang kernel:  ? _nv015812rm+0x9cc/0xad0 [nvidia]
May 15 14:58:27 mustang kernel:  ? _nv034293rm+0x174/0x180 [nvidia]
May 15 14:58:27 mustang kernel:  ? _nv035937rm+0x265/0x2c0 [nvidia]
May 15 14:58:27 mustang kernel:  ? _nv011415rm+0x4fe/0x620 [nvidia]
May 15 14:58:27 mustang kernel:  ? _nv034427rm+0x53/0xb0 [nvidia]
May 15 14:58:27 mustang kernel:  ? _nv000642kms+0x90/0x90 [nvidia_modeset]
May 15 14:58:27 mustang kernel:  ? _nv010344rm+0x52/0xa0 [nvidia]
May 15 14:58:27 mustang kernel:  ? _nv010343rm+0x46/0x50 [nvidia]
May 15 14:58:27 mustang kernel:  ? _nv010343rm+0x2f/0x50 [nvidia]
May 15 14:58:27 mustang kernel:  ? rm_kernel_rmapi_op+0x141/0x190 [nvidia]
May 15 14:58:27 mustang kernel:  ? _nv000642kms+0x90/0x90 [nvidia_modeset]
May 15 14:58:27 mustang kernel:  ? nvkms_call_rm+0x38/0x60 [nvidia_modeset]
May 15 14:58:27 mustang kernel:  ? _nv002519kms+0x51/0x60 [nvidia_modeset]
May 15 14:58:27 mustang kernel:  ? _nv002562kms+0x3e/0x90 [nvidia_modeset]
May 15 14:58:27 mustang kernel:  ? _nv002338kms+0x1a2/0x1c0 [nvidia_modeset]
May 15 14:58:27 mustang kernel:  ? _nv000647kms+0x30/0x60 [nvidia_modeset]
May 15 14:58:27 mustang kernel:  ? _nv000642kms+0x66/0x90 [nvidia_modeset]
May 15 14:58:27 mustang kernel:  ? nvKmsIoctl+0x96/0x1d0 [nvidia_modeset]
May 15 14:58:27 mustang kernel:  ? _raw_spin_lock_irqsave+0x25/0x50
May 15 14:58:27 mustang kernel:  ? nvkms_ioctl+0xdc/0x150 [nvidia_modeset]
May 15 14:58:27 mustang kernel:  ? nvidia_frontend_unlocked_ioctl+0x35/0x50 [nvidia]
May 15 14:58:27 mustang kernel:  ? __x64_sys_ioctl+0x8a/0xc0
May 15 14:58:27 mustang kernel:  ? do_syscall_64+0x37/0x80
May 15 14:58:27 mustang kernel:  ? entry_SYSCALL_64_after_hwframe+0x44/0xae
May 15 14:58:27 mustang kernel:  </TASK>

Is there any more information I can provide to help solve this issue? Maybe I am asking in the wrong place? There seems to be others that have similar issues with Wayland and NVidia drivers related to black screens. Any ideas on what the problem may be and if anyone is already working on a solution?

Fedora 36 is supporting Plasma Desktop with Wayland as the default now and going forward. Neither the Nvidia proprietary nor Noveau driver supports Wayland very well under Plasma Desktop. I am going to try to switch over to an AMD card, since from what I can tell, has better support for Wayland.

I also have this issue. My device does not have an Nvidia gpu. This is a fresh install of fedora 36 Kinoite.
Operating System: Fedora Linux 36 ( Kinoite )
KDE Plasma Version: 5.24.5
KDE Frameworks Version: 5.93.0
Qt Version: 5.15.3
Kernel Version: 5.17.12-300.fc36.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 8 × 11th Gen Intel® Core™ i3-1125G4 @ 2.00GHz
Memory: 7.5 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics