Arch Linux, "hang" on "Reached target Graphical Interface"

Question

EDIT: I just tried gnome and gdm and it worked flawlessly. So something with the virtualbox packages and the SDDM package seems to not work.

At first this question looks like this one (Arch Linux stuck at boot (reached target Graphical Interface)), however, I can still change to a different TTY.

Anyways, the following used to work before, but results in a core dump of sddm since recently. Interestingly enough, systems I simply update, which used this install method, do still work, but new installations lead to the issues below.

When installing Arch Linux in VirtualBox with Windows 10 as host system, I use this minimum [non]working example that is based on the official Arch Installer guide and used to work:

parted

mklabel GPT
mkpart ESP fat32 1MiB 513MiB
mkpart primary ext4 513MiB 100%
set 1 boot on
quit

mkfs.ext4 /dev/sda2
mkfs.fat -F32 /dev/sda1

mount /dev/sda2 /mnt

mkdir -p /mnt/boot
mount /dev/sda1 /mnt/boot

pacstrap /mnt base base-devel \
              virtualbox-guest-modules-arch \
              virtualbox-guest-utils \
              sddm plasma

arch-chroot /mnt bootctl --path=/boot install

cat <<-END > /mnt/boot/loader/entries/arch.conf
title Arch Linux
linux /vmlinuz-linux
initrd /initramfs-linux.img
options root=PARTUUID=$( blkid -s PARTUUID -o value /dev/sda2 ) rw
END

cat <<-END > /mnt/boot/loader/loader.conf
default arch
timeout 4
editor  0
END

genfstab -pU /mnt >> /mnt/etc/fstab

arch-chroot /mnt systemctl enable sddm

arch-chroot /mnt useradd -m -G wheel -s /bin/bash bob

It hangs on "reached target Graphical interface" but I can still use ctrl+alt+F2 in contrast to this question (Arch Linux stuck at boot (reached target Graphical Interface)) and calling journalctl -b -p err yields:

And here with more info:

Solution

It seems that SDDM/KDE no longer pulls xorg-server packages automatically. So if one adds the xorg-server package it works.

Found solution here: https://github.com/sddm/sddm/issues/605#issuecomment-275938076

Comments

[GPMueller]

unfortunately my VBox currently produces the same error...