[Pkg-utopia-maintainers] Bug#832093: NetworkManager-wait-online.service fails to start and delays boot

[Bastian Venthur]

Package: network-manager
Version: 1.54.1-1
Followup-For: Bug #832093
X-Debbugs-Cc: venthur at debian.org

Hi,

I think I stumbled upon the same issue: My new laptop would boot in about
~2seconds until starting GDM3, however it then spends ~10seconds waiting before
GDM3 is actually shown.

After some digging in journalctl, it seems the last thing it consistently does
before finally showing GDM3 is activating the wifi, however I also see in the
logs that the Ethernet device is almost instantly available after launching
GDM3, so I guess it should not be necessary to wait for the wiwi

Okt 06 08:02:36 flix systemd[1]: Started gdm.service - GNOME Display Manager.
Okt 06 08:02:36 flix systemd[1]: Received SIGRTMIN+21 from PID 474 (plymouthd).
Okt 06 08:02:36 flix systemd[1]: Started cups.service - CUPS Scheduler.
Okt 06 08:02:36 flix NetworkManager[1338]: <info>  [1759730556.2647] device (enx84ba59066cd2): carrier: link connected
Okt 06 08:02:36 flix NetworkManager[1338]: <info>  [1759730556.2651] device (enx84ba59066cd2): state change: unavailable -> disconnected (reason 'carrier-changed', managed-type: 'full')
Okt 06 08:02:36 flix NetworkManager[1338]: <info>  [1759730556.2654] policy: auto-activating connection 'Wired connection 1' (31f52007-6122-32cc-b7f4-ffb0ec6596eb)
Okt 06 08:02:36 flix NetworkManager[1338]: <info>  [1759730556.2657] device (enx84ba59066cd2): Activation: starting connection 'Wired connection 1' (31f52007-6122-32cc-b7f4-ffb0ec6596eb)
Okt 06 08:02:36 flix NetworkManager[1338]: <info>  [1759730556.2658] device (enx84ba59066cd2): state change: disconnected -> prepare (reason 'none', managed-type: 'full')
Okt 06 08:02:36 flix NetworkManager[1338]: <info>  [1759730556.2658] manager: NetworkManager state is now CONNECTING
Okt 06 08:02:36 flix NetworkManager[1338]: <info>  [1759730556.2659] device (enx84ba59066cd2): state change: prepare -> config (reason 'none', managed-type: 'full')
Okt 06 08:02:36 flix NetworkManager[1338]: <info>  [1759730556.2662] device (enx84ba59066cd2): state change: config -> ip-config (reason 'none', managed-type: 'full')
Okt 06 08:02:36 flix NetworkManager[1338]: <info>  [1759730556.2664] dhcp4 (enx84ba59066cd2): activation: beginning transaction (timeout in 45 seconds)
Okt 06 08:02:36 flix avahi-daemon[1203]: Joining mDNS multicast group on interface enx84ba59066cd2.IPv6 with address fe80::d6d5:a816:1822:fafb.
Okt 06 08:02:36 flix avahi-daemon[1203]: New relevant interface enx84ba59066cd2.IPv6 for mDNS.
Okt 06 08:02:36 flix avahi-daemon[1203]: Registering new address record for fe80::d6d5:a816:1822:fafb on enx84ba59066cd2.*.
Okt 06 08:02:36 flix NetworkManager[1338]: <info>  [1759730556.2674] dhcp4 (enx84ba59066cd2): state changed no lease

... # ~10 seconds later

Okt 06 08:02:45 flix NetworkManager[1338]: <info>  [1759730565.2278] device (wlp194s0): state change: ip-config -> ip-check (reason 'none', managed-type: 'full')
Okt 06 08:02:45 flix NetworkManager[1338]: <info>  [1759730565.2286] device (wlp194s0): state change: ip-check -> secondaries (reason 'none', managed-type: 'full')
Okt 06 08:02:45 flix NetworkManager[1338]: <info>  [1759730565.2287] device (wlp194s0): state change: secondaries -> activated (reason 'none', managed-type: 'full')
Okt 06 08:02:45 flix NetworkManager[1338]: <info>  [1759730565.2298] device (wlp194s0): Activation: successful, device activated.
Okt 06 08:02:45 flix NetworkManager[1338]: <info>  [1759730565.2300] manager: startup complete
Okt 06 08:02:45 flix systemd[1]: Finished NetworkManager-wait-online.service - Network Manager Wait Online.
Okt 06 08:02:45 flix systemd[1]: Reached target network-online.target - Network is Online.
Okt 06 08:02:45 flix systemd[1]: Started cups-browsed.service - Make remote CUPS printers available locally.
Okt 06 08:02:45 flix systemd[1]: Starting exim4.service - exim Mail Transport Agent...
Okt 06 08:02:45 flix systemd[1]: Started exim4.service - exim Mail Transport Agent.
Okt 06 08:02:46 flix systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Okt 06 08:02:46 flix gdm-launch-environment][1819]: pam_unix(gdm-launch-environment:session): session opened for user Debian-gdm(uid=110) by (uid=0)


Is this a bug or is this the intended behaviour? And is there a way to make the
NetworkManager-wait-online.service become "ready" already when the first of the
available devices is online?


Cheers,

Bastian


My /etc/network/interfaces:

> # This file describes the network interfaces available on your system
> # and how to activate them. For more information, see interfaces(5).
> 
> source /etc/network/interfaces.d/*
> 
> # The loopback network interface
> auto lo
> iface lo inet loopback

and /etc/NetworkManager/NetworkManager.conf

> [main]
> plugins=ifupdown,keyfile
> 
> [ifupdown]
> managed=false


-- System Information:
Debian Release: forky/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.16.9+deb14-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages network-manager depends on:
ii  adduser                         3.153
ii  dbus [default-dbus-system-bus]  1.16.2-2
ii  libaudit1                       1:4.1.2-1
ii  libbluetooth3                   5.84-1
ii  libc6                           2.41-12
ii  libcurl3t64-gnutls              8.16.0-2
ii  libglib2.0-0t64                 2.84.4-3
ii  libgnutls30t64                  3.8.10-2
ii  libjansson4                     2.14-2+b3
ii  libmm-glib0                     1.24.2-1
ii  libndp0                         1.9-1+b1
ii  libnewt0.52                     0.52.25-1
ii  libnm0                          1.54.1-1
ii  libpsl5t64                      0.21.2-1.1+b1
ii  libreadline8t64                 8.3-3
ii  libselinux1                     3.8.1-1
ii  libsystemd0                     258-1
ii  libteamdctl0                    1.31-1+b3
ii  libudev1                        258-1

Versions of packages network-manager recommends:
ii  dnsmasq-base [dnsmasq-base]  2.91-1
ii  libpam-systemd               258-1
ii  modemmanager                 1.24.2-1
ii  network-manager-l10n         1.54.1-1
ii  polkitd                      126-2
ii  ppp                          2.5.2-1+1.1
ii  udev                         258-1
ii  wireless-regdb               2025.07.10-1
ii  wpasupplicant                2:2.10-24+b1

Versions of packages network-manager suggests:
ii  iptables       1.8.11-2
pn  libteam-utils  <none>

Versions of packages network-manager is related to:
pn  isc-dhcp-client  <none>

-- no debconf information