When I try to login to the Plasma with the Wayland, it gives me black screen and about 2-3 seconds it drops me back to the login page. I’m a newbie so I really don’t know what to do.
My specs;
CPU - Ryzen 7 5800X
GPU - RX 6800 XT
RAM - 32 GB
Display Manager: SDDM
Oh, wait a minute, you don’t have a Nvidia card, forget my post…
the RX 6800 XT is AMD 
Did you try a reboot before logging into Wayland? In the past (1-2 years ago) I had some issues when I tried to switch from X11 session to Wayland session without a reboot. Haven’t tried switching session types without rebooting since.
Wayland in general works great here on my RX 6750XT
Did you try a reboot before logging into Wayland?
Yes, I did. But it didn’t help.
Try to log into the X11 session after logging into the wayland session failed and post the output of journalctl -p 3 -xb - do not reboot for that or the command has to differ to show the logs of the previous boot.
Output:
Oca 15 15:56:15 squash-PC kernel: Bluetooth: hci0: Opcode 0xfc1e failed: -16
Oca 15 15:56:19 squash-PC libvirtd[892]: Unable to read from monitor: Connection reset by peer
Oca 15 15:56:19 squash-PC libvirtd[892]: internal error: QEMU unexpectedly closed the monitor (vm='win10'): 2024-01-15T12:56:19.365579Z qemu-system-x86_64: -device {"driver":"virtio-vga-gl","id":"video0","max_outputs":1,"bus":"pcie.0","addr":"0x1"}: opengl is not available
Oca 15 15:56:19 squash-PC libvirtd[892]: internal error: Failed to autostart VM 'win10': internal error: QEMU unexpectedly closed the monitor (vm='win10'): 2024-01-15T12:56:19.365579Z qemu-system-x86_64: -device {"driver":"virtio-vga-gl","id":"video0","max_outputs":1,"bus":"pcie.0","addr":"0x1"}: opengl is not available
Oca 15 15:56:41 squash-PC libddcutil[1561]: busno=8, sleep-multiplier = 1,30. Testing for supported feature 0x10 returned Error_Info[EIO in ddc_write_read_with_retry, causes: EIO]
Oca 15 15:59:13 squash-PC libddcutil[3355]: busno=8, sleep-multiplier = 1,30. Testing for supported feature 0x10 returned Error_Info[EIO in ddc_write_read_with_retry, causes: EIO]
that looks like you are outstarting some qemu-vm which does not work for some reason. You might disable that outstart to check if that solves the issue.
the libddcutil part can be an issue, too but that should be caught in the code and not lead to a failed DE load - the issues I found by a quick google search simply lead to a non-working powerdevil.
I fixed the powerdevil error by downgrading it and libvirtd by removing the win10 VM, but I still have the Wayland problem.
If you have the exec startx command in your ~/.bash_profile, you should remove it.
It worked, thanks!
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.