Bug 1952748

Description of problem: I just spun up the latest F34 kde spin disk image on a rpi4 running the PFTF UEFI firmware for the rpi4. The image starts, I can set the root password, network, etc and then it says everything has started successfully but the screen never appears to start wayland/X11 or SDDM. Instead i'm left with just a blank screen and a flashing cursor. Changing to another vt, doesn't show anything of note in the logs other than that sddm has successfully started. I can jump through some hoops and startkde it, but the startplasma-wayland/X11 won't by themselves start it.

installing gdm and switching it on as the displaymanager rather than sddm allows me to boot, login and use KDE. Although I don't see the wayland options in gdm, probably because i'm missing something, the only optin is "Plasma (X11)"

I'm actually a pretty heavy user of KDE, on aarch64, but rarely since the master of seat issue that I pointed out a while back have I tried debugging SDDM. This is vaguely reminiscent of that since I again am running on a dumb frame buffer.

So any requests?


Version-Release number of selected component (if applicable): sddm-0.19.0-8.fc34.aarch64


How reproducible: Every boot.


Steps to Reproduce:
1. Grab aarch64 install image, write it to a USB disk, plug it into a rpi4 using the PFTF UEFI on the sd card. https://github.com/pftf/RPi4/releases
2. power on machine, do initial machine setup
3. wait for graphical login

Actual results: Blank screen flashing cursor.


Expected results: Pretty sddm login.


Additional info: Now that I'm using it a bit there are a couple abrt cores in comming.