On every ~1 out of ~3 boots GDM gets stuck, not showing the user / password promt:
I can move my mouse and open the calendar at the top and the power menu. I cannot shutdown / reboot my computer from GDM though, but this seems to be an unrelated bug: Can't shutdown/reboot from gdm - #5 by AlanP
Therefore I have to kill the power to reboot and try again and with some luck my user will appear and I can login.
/var/log/gdm is empty.
journalctl: -- Journal begins at Tue 2021-07-13 20:42:14 CEST, ends at Sun 2021-10-03 13:01: - Pastebin.com
With the most relevant entries probably being:
Okt 03 12:08:30 my-manjaro systemd-coredump[4997]: Failed to connect to coredump service: Connection refused
Okt 03 12:08:31 my-manjaro gdm[1119]: Gdm: Failed to contact accountsservice: Error calling StartServiceByName for org.freedesktop.Accounts: Refusing activation, D-Bus is shutting down.
Okt 03 12:08:31 my-manjaro systemd[1]: gdm.service: Main process exited, code=exited, status=1/FAILURE
Okt 03 12:08:31 my-manjaro systemd[1]: gdm.service: Failed with result 'exit-code'.
Okt 03 12:08:31 my-manjaro systemd[1]: Stopped GNOME Display Manager.
Okt 03 12:08:31 my-manjaro systemd[1]: gdm.service: Triggering OnFailure= dependencies.
Okt 03 12:08:31 my-manjaro systemd[1]: Requested transaction contradicts existing jobs: Transaction for plymouth-quit.service/start is destructive (home.mount has 'stop' job queued, but 'start' is included in transaction).
Okt 03 12:08:31 my-manjaro systemd[1]: gdm.service: Failed to enqueue OnFailure= job, ignoring: Transaction for plymouth-quit.service/start is destructive (home.mount has 'stop' job queued, but 'start' is included in transaction).
inxi: System: Kernel: 5.13.19-2-MANJARO x86_64 bits: 64 compiler: gcc v: 11.1.0 - Pastebin.com
systemctl status gdm.service
gdm.service - GNOME Display Manager
Loaded: loaded (/usr/lib/systemd/system/gdm.service; enabled; vendor preset: disabled)
Active: active (running) since Sun 2021-10-03 12:13:07 CEST; 58min ago
Main PID: 1129 (gdm)
Tasks: 3 (limit: 38405)
Memory: 5.7M
CPU: 51ms
CGroup: /system.slice/gdm.service
ââ1129 /usr/bin/gdm
Okt 03 12:13:07 my-manjaro systemd[1]: Starting GNOME Display Manager...
Okt 03 12:13:07 my-manjaro systemd[1]: Started GNOME Display Manager.
Okt 03 12:13:15 my-manjaro gdm-password][1865]: gkr-pam: unable to locate daemon control file
Okt 03 12:13:15 my-manjaro gdm-password][1865]: gkr-pam: stashed password to try later in open session
Okt 03 12:13:15 my-manjaro gdm-password][1865]: pam_systemd_home(gdm-password:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
Okt 03 12:13:15 my-manjaro gdm-password][1865]: pam_unix(gdm-password:session): session opened for user user(uid=1000) by (uid=0)
Okt 03 12:13:15 my-manjaro gdm-password][1865]: pam_env(gdm-password:session): deprecated reading of user environment enabled
Okt 03 12:13:15 my-manjaro gdm-password][1865]: gkr-pam: gnome-keyring-daemon started properly and unlocked keyring
Okt 03 12:13:23 my-manjaro gdm[1129]: Gdm: Child process -1179 was already dead.
Maybe gkr-pam: unable to locate daemon control file has something to do with it?
The issue appeared a few days ago for me, possibly after updates. I have seen similar issues on the forum, but was not able to resolve it. Any help is appreciated! 
