started raise network interfaces - times out

Bug #1713984 reported by fossfreedom on 2017-08-30
This bug affects 4 people
Affects Status Importance Assigned to Milestone
systemd (Ubuntu)
Dimitri John Ledkov
Dimitri John Ledkov

Bug Description

Ubuntu Budgie 17.10 Beta 1 32bit virtualbox install

Test Case AutoResize

choose to encrypt home drive, install all updates and non free codecs for the installation options

On boot (and every subsequent boot) I see in the boot sequence

started raise network interfaces

this sits there for 1 minute 30 seconds before resuming.

On login, fired up chromium and connected to google so the networking is ok.

Question - why the 1 minute 30 seconds delay?

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: systemd 234-2ubuntu9
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic i686
ApportVersion: 2.20.6-0ubuntu7
Architecture: i386
CurrentDesktop: Budgie:GNOME
Date: Wed Aug 30 12:24:23 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-08-30 (0 days ago)
InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Alpha i386 (20170829)
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic root=UUID=cfd3c5b9-deb1-4d8f-8d6a-98996d260029 ro quiet splash
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install) 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: Virtual Machine VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH

fossfreedom (fossfreedom) wrote :
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in systemd (Ubuntu):
status: New → Confirmed

I am affected by this on Ubuntu MATE 17.10.

systemd-analyze blame shows:

2min 26ms systemd-networkd-wait-online.service

Seriously what the hell.
Holding up boot until the network comes up?

Maybe it makes sense in a server setting, but this should never happen for Desktop versions of Ubuntu.

Changed in systemd (Ubuntu Artful):
assignee: nobody → Dimitri John Ledkov (xnox)
importance: Undecided → High
Brian Murray (brian-murray) wrote :

I'm not certain this is related but I did not experience the delay when using lightdm, but do when using gdm3.

Davide (tarski10) wrote :

Ubuntu 17.10
systemd 234-2ubuntu6 -> boot time: 47 sec
systemd 234-2ubuntu9 -> boot time: 72 sec

Is it normal?

Sitsofe Wheeler (sitsofe) wrote :

Wild guess: this might be because you have only one network interface that is set to use DHCP but the DHCP server is set not to return any routers. See for this type of scenario.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.