You are not logged in.
I got the issue that Gnome is not starting automatically during the booting process. I have to login via tty and start Gnome manually.
Upon further investigation, I found out that the vendor preset for gdm.service is disabled.
systemctl list-unit-files --state=enabled
UNIT FILE STATE VENDOR PRESET
gdm.service enabled disabled
getty@.service enabled enabled
NetworkManager-dispatcher.service enabled disabled
NetworkManager-wait-online.service enabled disabled
NetworkManager.service enabled disabled
vpnagentd.service enabled disabled
remote-fs.target enabled enabled
7 unit files listed.
I tried to enable it with
systemctl enable gdm.service
However, the vendor preset status for gdm.service remains unchanged.
Here is also the output of systemctl status gdm.service in case that information is relevant.
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 Thu 2021-02-11 20:13:49 CET; 5h 13min ago
Main PID: 371 (gdm)
Tasks: 3 (limit: 37183)
Memory: 5.7M
CGroup: /system.slice/gdm.service
└─371 /usr/bin/gdm
Feb 11 20:13:49 archLaptop gdm[371]: Gdm: Child process -456 was already dead.
Feb 11 20:13:49 archLaptop gdm[371]: Gdm: Child process -456 was already dead.
Feb 11 20:13:49 archLaptop gdm[371]: Gdm: Child process -533 was already dead.
Feb 11 20:14:29 archLaptop gdm-password][1007]: gkr-pam: unable to locate daemon control file
Feb 11 20:14:29 archLaptop gdm-password][1007]: gkr-pam: stashed password to try later in open session
Feb 11 20:14:29 archLaptop gdm-password][1007]: pam_systemd_home(gdm-password:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
Feb 11 20:14:29 archLaptop gdm-password][1007]: pam_unix(gdm-password:session): session opened for user steven(uid=1000) by (uid=0)
Feb 11 20:14:29 archLaptop gdm-password][1007]: pam_env(gdm-password:session): deprecated reading of user environment enabled
Feb 11 20:14:29 archLaptop gdm-password][1007]: gkr-pam: gnome-keyring-daemon started properly and unlocked keyring
Feb 11 20:14:32 archLaptop gdm[371]: Gdm: Child process -661 was already dead.
Last edited by Akas (2021-02-13 23:19:16)
Offline
Vendor presets don't change when a service is enabled or disabled .
please post (run as root) journalctl -b
It will be large, check https://wiki.archlinux.org/index.php/Li … in_clients for methods to make uploading it easy
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Hi,
thanks for the reply. Here is the output of journalctl -b: http://sprunge.us/WOOux0
Offline
The log shows lots of errors on firmware level, and acer released 3 newer versions, check https://www.acer.com/ac/en/US/content/s … .Q3RAA.002
I don't think that's causing gdm to fail though .
This looks very much like a common race condition where gdm (also happens with other DMs) tries to use the videocard before it's fully initialised.
Try configuring https://wiki.archlinux.org/index.php/Ke … _KMS_start .
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Thanks for pointing out that there is a firmware update available. Unfortunately, it seems I am unable to update the firmware as I do not have a Windows partition installed.
I added the amdgpu module in the MODULES array in /etc/mkinitcpio.conf. However, I still get the issue that Gnome is not starting automatically.
When I got the Notebook in Autumn 2019 everything was fine and I got no issues with Gnome. However, since a systemd update in winter 2020 or at the beginning of this year (I cannot remember exactly), I got this issue.
Offline
Fresh logs please,
# journalctl -b | grep -v audit
(the audit messages are rarely useful for this kind of troubleshooting, removing them makes log a lot more readable)
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Fresh logs: http://sprunge.us/nCvQGu
Offline
Feb 13 20:40:27 archLaptop /usr/lib/gdm-x-session[533]: Unable to run X server
Feb 13 20:40:27 archLaptop gdm[372]: Gdm: Child process -533 was already dead.
Feb 13 20:40:28 archLaptop kernel: [drm] Initialized amdgpu 3.40.0 20150101 for 0000:04:00.0 on minor 1
Verify you do have amdgpu in your modules= line in mkinitcpio AND regenerate initramfs .
(==) Using config directory: "/etc/X11/xorg.conf.d"
Post ls -lR /etc/X11 & the contents of files in /etc/X11/xorg.conf.d folder.
Also install xf86-video-amdgpu.
Reboot and post fresh log .
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Verify you do have amdgpu in your modules= line in mkinitcpio AND regenerate initramfs .
Thank you very much! Regenerating the initramfs did the trick. Thank you for taking the time.
Offline