There is a glitch caused by Systemd if not many, on my Debian 11 desktop. The Netwrk Manager always waits for loading “remote” booting components e.g., drivers, whenever the operating system is booting . This is probably a design “feature” of UNIX-like system, which the idea could be tracked back to Time-sharing concept of system running on UNIX.

This “feature” made sense at 1980s but turns to be bugg-ish on modern hardware. Nowadays, even a single board computer could hold all drivers on a SD card, and operating system with desktop environment (DE) has been deigned to get online after DE login for obviously security reason. As a result, many Debian/Ubuntu-based system frequently been noticed stuck in Network-Manager-wait-online.service stage during booting, here is the case for Linux Mint.

As the answer of this StackExcange suggested, one should delete/disable Network Manager dependent on the DEs. For Gnome, deletion is NOT a option. Instead, one should stop & disable Network Manager permanently following this Ubuntu community doc page, run these shell commands

~# systemctl stop NetworkManager.service
~# systemctl stop NetworkManager-wait-online.service
~# systemctl stop NetworkManager-dispatcher.service
~# systemctl stop network-manager.service

to stop the current service, and then run these commands

~# systemctl disable NetworkManager.service
~# systemctl disable NetworkManager-wait-online.service
~# systemctl disable NetworkManager-dispatcher.service
~# systemctl disable network-manager.service

to permanently disable Network Manager from starting during boot process, then reboot system.

  • last time edited @10th. Feb. 2024