[SOLVED] GDM-Plymouth does not start at boot anymore

macaco · 2022-01-18 18:45:05

Since roughly one week when booting my system it ends in a virtual console. I can still start the gdm by simply

 sudo systemctl start gdm.service

but for some reason this does not happen automatically anymore. Also

 sudo systemctl enable gdm.service

just yields:

 Failed to enable unit: File /etc/systemd/system/display-manager.service already exists and is a symlink to /usr/lib/systemd/system/gdm-plymouth.service.

Why did it stop all of a sudden?

Last edited by macaco (2022-01-26 19:22:06)

yochananmarqos · 2022-01-18 20:10:20

It happened with the recent plymouth update from 0.9.5-7 to to 22.02.122-1. I downgraded plymouth for now, I haven't figured out the cause yet.

FYI, this probably should have been posted in AUR Issues.

icar · 2022-01-18 23:54:45

Works here, even after the update. Do you have early KMS configured?

yochananmarqos · 2022-01-19 01:14:01

I do, yes.

MODULES=(nvidia nvidia_modeset nvidia_uvm nvidia_drm)

macaco · 2022-01-20 10:24:53

Yes you are right, this would be rather an AUR issue. Since I didn't know which part of my system causes the problem I posted it here.

The thing is, now even with a downgrade the situation remains the same. How can I find out what's going on?

Edit:

 journalctl -p 3 -b
Jan 20 11:21:44 laptopmmmh kernel: x86/cpu: VMX (outside TXT) disabled by BIOS
Jan 20 11:22:00 laptopmmmh systemd[568]: (pam_mount.c:173): conv->conv(...): Conversation error
Jan 20 11:22:00 laptopmmmh systemd[568]: (pam_mount.c:476): warning: could not obtain password interactively either
Jan 20 11:22:00 laptopmmmh systemd[568]: (mount.c:68): Messages from underlying mount program:
Jan 20 11:22:00 laptopmmmh systemd[568]: (mount.c:72): Device _dev_sda3 already exists.
Jan 20 11:22:00 laptopmmmh systemd[568]: (mount.c:72): crypt_activate_by_passphrase: File exists
Jan 20 11:22:00 laptopmmmh systemd[568]: (mount.c:72): Device _dev_sda3 is still in use.
Jan 20 11:22:00 laptopmmmh systemd[568]: (pam_mount.c:522): mount of /dev/sda3 failed
Jan 20 11:22:00 laptopmmmh systemd[568]: (pam_mount.c:173): conv->conv(...): Conversation error
Jan 20 11:22:00 laptopmmmh systemd[568]: (pam_mount.c:476): warning: could not obtain password interactively either
Jan 20 11:22:13 laptopmmmh gnome-session-binary[681]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
Jan 20 11:22:13 laptopmmmh gnome-session-binary[681]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
Jan 20 11:22:19 laptopmmmh gdm-password][893]: gkr-pam: unable to locate daemon control file
Jan 20 11:22:19 laptopmmmh gdm-password][893]: (mount.c:68): Messages from underlying mount program:
Jan 20 11:22:19 laptopmmmh gdm-password][893]: (mount.c:72): Device _dev_sda3 already exists.
Jan 20 11:22:19 laptopmmmh gdm-password][893]: (mount.c:72): crypt_activate_by_passphrase: File exists
Jan 20 11:22:19 laptopmmmh gdm-password][893]: (mount.c:72): Device _dev_sda3 is still in use.
Jan 20 11:22:19 laptopmmmh gdm-password][893]: (pam_mount.c:522): mount of /dev/sda3 failed
Jan 20 11:22:24 laptopmmmh gdm-launch-environment][660]: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jan 20 11:52:02 laptopmmmh kernel: done.
Jan 20 11:52:02 laptopmmmh pulseaudio[993]: Device /org/bluez/hci0/dev_38_18_4C_BD_72_63 points to a nonexistent adapter /org/bluez/hci0.
Jan 20 11:52:02 laptopmmmh pulseaudio[993]: Device /org/bluez/hci0/dev_5C_FB_7C_F8_5E_1F points to a nonexistent adapter /org/bluez/hci0.
Jan 20 11:52:02 laptopmmmh pulseaudio[993]: Device /org/bluez/hci0/dev_FC_A8_9A_9D_1B_FF points to a nonexistent adapter /org/bluez/hci0.

Last edited by macaco (2022-01-20 10:57:20)

macaco · 2022-01-25 12:20:25

icar wrote:

Works here, even after the update. Do you have early KMS configured?

To answer your question, yes I have as well:

 MODULES="intel_agp i915"

d_fajardo · 2022-01-25 17:13:12

Did you try running mkinicpio again afterwards. I had the same 'Failed enable unit' but I ran mkinicpio again and plymouth starts working again.

Taijian · 2022-01-25 19:37:48

macaco wrote:

just yields:

 Failed to enable unit: File /etc/systemd/system/display-manager.service already exists and is a symlink to /usr/lib/systemd/system/gdm-plymouth.service.

Why did it stop all of a sudden?

Here is your issue - the symlink to gdm-plymouth.service has been deprecated for a looooooooooong time. The last update has now just straight up removed it. Simply remove that symlink from your system and you should then be able to enable gdm.service.

Also: If you use the comment section under my AUR packages for questions like this, I do get notified and can help you more quickly.

macaco · 2022-01-26 19:21:41

Taijian wrote:

macaco wrote:
just yields:
 Failed to enable unit: File /etc/systemd/system/display-manager.service already exists and is a symlink to /usr/lib/systemd/system/gdm-plymouth.service. 
Why did it stop all of a sudden?
Here is your issue - the symlink to gdm-plymouth.service has been deprecated for a looooooooooong time. The last update has now just straight up removed it. Simply remove that symlink from your system and you should then be able to enable gdm.service.
Also: If you use the comment section under my AUR packages for questions like this, I do get notified and can help you more quickly.

Thanks, this did solve the problem. I am using the same Arch since nearly 10 years now... this was obviously a leftofer. Next time I post in the right corner.

Edit: Thanks for maintaining the AUR btw

Last edited by macaco (2022-01-26 19:23:28)

Arch Linux

#1 2022-01-18 18:45:05

[SOLVED] GDM-Plymouth does not start at boot anymore

#2 2022-01-18 20:10:20

Re: [SOLVED] GDM-Plymouth does not start at boot anymore

#3 2022-01-18 23:54:45

Re: [SOLVED] GDM-Plymouth does not start at boot anymore

#4 2022-01-19 01:14:01

Re: [SOLVED] GDM-Plymouth does not start at boot anymore

#5 2022-01-20 10:24:53

Re: [SOLVED] GDM-Plymouth does not start at boot anymore

#6 2022-01-25 12:20:25

Re: [SOLVED] GDM-Plymouth does not start at boot anymore

#7 2022-01-25 17:13:12

Re: [SOLVED] GDM-Plymouth does not start at boot anymore

#8 2022-01-25 19:37:48

Re: [SOLVED] GDM-Plymouth does not start at boot anymore

#9 2022-01-26 19:21:41

Re: [SOLVED] GDM-Plymouth does not start at boot anymore

Board footer