GNOME gdm service does not start after upgrade

[flexoron]

Hello,
again: After updating yesterday(see below), GNOME gdm login service did not start.

Instead, I got a login-shell and found a broken link:

Code: Select all

# cd /etc/systemd/system
# ls -l
... display-manager.service -> /usr/lib64/systemd/system/gdm-plymouth.service

# systemctl status display-manager.service
Unit display-manager.service could not be found.

# ls -l /usr/lib64/systemd/system/gdm-plymouth.service
ls: cannot access ....

Solution:

Code: Select all

# cd /etc/systemd/system
# rm display-manager.service

# systemctl enable gdm-plymouth.service
# ls -l
... display-manager.service -> /lib/systemd/system/gdm-plymouth.service

# ls -l /lib/systemd/system/gdm-plymouth.service
... /lib/systemd/system/gdm-plymouth.service

And I don't like Wayland:

Code: Select all

# cd /etc/gdm
# vi custem.conf
WaylandEnable=false

Code: Select all

# systemctl reboot

Maybe this update caused the misbehavior:

## U [sabayonlinux.org] sys-boot/plymouth-0.8.9_pre1-r3|1 [0.8.9_pre1-r3|0]

systemd gdm-plymouth.service moved to /lib/systemd/system

[albfneto]

You tried to verify the status of the gdm in the services of systemd?

Code: Select all

# systemctl status gdm.service

i dont use gdm or GNOME, bui i use KDE and their login manager, sddm...

and for good working the service of the sddm should be running:

Code: Select all

sudo systemctl status display-manager.service
Senha: 
● sddm.service - Simple Desktop Display Manager
   Loaded: loaded (/usr/lib/systemd/system/sddm.service; enabled; vendor preset: disabled)
   Active: active (running) since Wed 2018-12-05 16:54:28 -02; 3h 55min ago
     Docs: man:sddm(1)
           man:sddm.conf(5)
 Main PID: 858 (sddm)
    Tasks: 8 (limit: 4915)
   Memory: 100.3M
   CGroup: /system.slice/sddm.service
           ├─858 /usr/bin/sddm
           └─875 /usr/libexec/Xorg -nolisten tcp -auth /var/run/sddm/{7727142e-801a-4031-8ab4-3643e470b5c9} -back>

dez 05 14:54:52 sabayon.local sddm-helper[1134]: [PAM] Preparing to converse...
dez 05 14:54:52 sabayon.local sddm-helper[1134]: [PAM] Conversation with 1 messages
dez 05 14:54:52 sabayon.local sddm-helper[1134]: pam_kwallet5(sddm:auth): (null): pam_sm_authenticate
dez 05 14:54:52 sabayon.local sddm-helper[1134]: [PAM] returning.
dez 05 14:54:52 sabayon.local sddm[858]: Authenticated successfully
dez 05 14:54:52 sabayon.local sddm-helper[1134]: pam_kwallet5(sddm:setcred): pam_kwallet5: pam_sm_setcred
dez 05 14:54:52 sabayon.local sddm-helper[1134]: pam_unix(sddm:session): session opened for user albfneto by (uid>
dez 05 14:54:53 sabayon.local sddm[858]: Session started
dez 05 14:54:53 sabayon.local sddm[858]: Auth: sddm-helper exited successfully
dez 05 14:54:53 sabayon.local sddm[858]: Greeter stopped.

The output of the command:

Code: Select all

# systemctl status sddm.service

shows started and running the sddm.service.

[flexoron]

Yes, I did!
gdm.service works, too but gdm-plymouth.service is somehow cleaner.

Code: Select all

# cd /etc/systemd/system
# rm display-manager.service
# systemctl enable gdm
# ls -l
... display-manager.service -> /usr/lib/systemd/system/gdm.service
# ls -l /usr/lib/systemd/system/gdm.service
... /usr/lib/systemd/system/gdm.service

Thanks for the hint.

BTW
There is another broken link:

Code: Select all

# cd /etc/systemd/system/multi-user.target.wants
# ls -l 
... irqbalance.service ->/usr/lib64/systemd/system/irqbalance.service   <-- broken
# rm irqbalance.service
# ln -s /lib64/systemd/system/irqbalance.service irqbalance.service
# systemctl restart irqbalance.service

[albfneto]

My system is not similar as yours. I use Sabayon KDE, my system not have some of the *-plymouth.services, nor irqbalance:

Code: Select all

# systemctl status irqbalance.service
Senha: 
Unit irqbalance.service could not be found.

my service kdm-plymouth.service is unloaded, since kdm no more exists. Look, this is SystemdGenie (one GUI for systemd in KDE):

https://i.postimg.cc/hvPS7Q7W/servicos.png

[flexoron]

The problem as such has nothing to do with GNOME or KDE.
Perhaps it is a package upgrade issue.
If the new version moves its systemd service file to another location (here from /usr/lib64 to /lib)
it might recreate(if enabled) its 'enable link' in /etc/systemd/..., too?