Arch Linux

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 78,526

Re: GDM takes a while to start.

You have systemd-networkd and networkmanager enabled.
Pick *one* service to manage your network, otherwise they enter a race and getting the network up will take longer.

Also:

systemctl list-unit-files --state=enabled

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

ceqp90

Member

Registered: 2019-03-22

Posts: 16

Re: GDM takes a while to start.

You have systemd-networkd and networkmanager enabled.
Pick *one* service to manage your network, otherwise they enter a race and getting the network up will take longer.

Also:

systemctl list-unit-files --state=enabled

Thanks! I disabled systemd-networkd.

 [carlos@carlos-pc ~]$ systemctl list-unit-files --state=enabled
UNIT FILE                                   STATE  
autovt@.service                             enabled
cpupower.service                            enabled
dbus-org.freedesktop.NetworkManager.service enabled
dbus-org.freedesktop.nm-dispatcher.service  enabled
display-manager.service                     enabled
gdm.service                                 enabled
getty@.service                              enabled
haveged.service                             enabled
NetworkManager-dispatcher.service           enabled
NetworkManager-wait-online.service          enabled
NetworkManager.service                      enabled
remote-fs.target                            enabled

12 unit files listed.
[carlos@carlos-pc ~]$ 

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 78,526

Re: GDM takes a while to start.

The implicit question was whether that would improve the GDM startup…

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

ceqp90

Member

Registered: 2019-03-22

Posts: 16

Re: GDM takes a while to start.

The implicit question was whether that would improve the GDM startup…

..apparently in about two seconds (compared with the output in my first post):

 [carlos@carlos-pc ~]$ sudo systemd-analyze critical-chain
[sudo] password for carlos: 
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.

graphical.target @12.207s
└─gdm.service @12.032s +172ms
  └─systemd-user-sessions.service @12.013s +17ms
    └─nss-user-lookup.target @12.239s
[carlos@carlos-pc ~]$ 

It still feels a little bit slow, but maybe its a matter of controlling the OCD...

Thanks.

Last edited by ceqp90 (2019-04-06 14:28:06)