After building workspace, Plasma starts but very slowly

I have managed to build the entire Plasma workspace group with kde-builder. I have built this on an Arch Linux bare minimum system (there is no other versions of Plasma or any other display managers or desktop environments). To start Plasma, I run the command found in /usr/local/share/wayland-sessions/plasmawayland-dev6.desktop, which is the following:

/home/mjq/kde/usr/lib/libexec/plasma-dbus-run-session-if-needed /home/mjq/kde/usr/lib/libexec/startplasma-dev.sh -wayland

Immediately, the splash screen appears, and stays for around 30 seconds. After which, a black screen with a mouse cursor appears. It’s like the display server is running because I can drag the mouse to the top left corner of the screen to view the other virtual desktops. But no background and no launcher or panels appear, just a black screen.

I’ve discovered though, that if I let it sit, after 3 minutes the background and everything else loads up. it just takes an incredibly long time.

I have attached a journalctl log of messages that appear

http://0x0.st/KC7k.txt

Can anyone determine what might be causing Plasma to load so slowly? There do seem to be a number of errors including a number of modules dumping core when I log out of the plasma session.

Is there any other information I can provide? Or should I submit a bug report? It seems like no one anywhere can help me with this issue.

30 seconds sounds like a timeout issue, and directly after the long gap, I see this in the log:


Dec 10 20:29:11 laplace /usr/lib/xdg-desktop-portal[713]: Failed to create settings proxy: Error calling StartServiceByName for org.freedesktop.impl.portal.desktop.kde: Timeout was reached

And a few more dbus errors (though some of them are common and I don’t think you need to be worrying about them).

So something seems to be going wrong with starting the desktop portal and a bunch of other things initally - it apparently works two minutes later, and blocks everything else in the mean time.

Not sure what could be the cause, I have no experience with such minimal installations.