Too long boot time, a network problem?

I have a problem with boot time. I asked the question elsewhere and I was advised to come here.

czanat@linux:~> systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.

graphical.target @1min 13.764s
└─multi-user.target @1min 13.764s
  └─cron.service @1min 13.764s
    └─postfix.service @1min 11.932s +1.830s
      └─network.target @1min 11.931s
        └─NetworkManager.service @15.862s +56.068s
          └─basic.target @15.855s
            └─timers.target @15.855s
              └─systemd-tmpfiles-clean.timer @15.855s
                └─sysinit.target @15.854s
                  └─systemd-journald.service @1min 10.840s
                    └─system.slice
                      └─-.slice

NetworkManager.service takes quite a long time.

Perhaps this might tell us more

journalctl -b |grep Network

Here is what you asked;

linux:/home/czanat # journalctl -b |grep Network
Nov 10 10:41:15 linux NetworkManager[750]: <info> NetworkManager (version 0.9.10.0) is starting...
Nov 10 10:41:15 linux NetworkManager[750]: <info> Read config: /etc/NetworkManager/NetworkManager.conf
Nov 10 10:41:15 linux NetworkManager[750]: <info> WEXT support is enabled
Nov 10 10:41:15 linux avahi-daemon[745]: Network interface enumeration completed.
Nov 10 10:41:16 linux NetworkManager[750]: <info> VPN: loaded org.freedesktop.NetworkManager.vpnc
Nov 10 10:41:16 linux NetworkManager[750]: <info> VPN: loaded org.freedesktop.NetworkManager.pptp
Nov 10 10:41:16 linux NetworkManager[750]: <info> VPN: loaded org.freedesktop.NetworkManager.openvpn
Nov 10 10:41:16 linux NetworkManager[750]: <info> VPN: loaded org.freedesktop.NetworkManager.openconnect
Nov 10 10:41:16 linux NetworkManager[750]: <info> Loaded plugin ifcfg-suse: (C) 2008 Novell, Inc.  To report bugs please use the NetworkManager mailing list.
Nov 10 10:41:16 linux NetworkManager[750]: <info> Loaded plugin keyfile: (c) 2007 - 2013 Red Hat, Inc.  To report bugs please use the NetworkManager mailing list.
Nov 10 10:41:17 linux NetworkManager[750]: <info> new connection /etc/NetworkManager/system-connections/part16m1
Nov 10 10:41:17 linux NetworkManager[750]: <info> new connection /etc/NetworkManager/system-connections/part16m1 1
Nov 10 10:41:17 linux NetworkManager[750]: <info> monitoring kernel firmware directory '/lib/firmware'.
Nov 10 10:41:17 linux NetworkManager[750]: <info> rfkill3: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.1/0000:04:00.0/ieee80211/phy0/rfkill3) (driver iwlwifi)
Nov 10 10:41:17 linux NetworkManager[750]: <info> rfkill0: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1f.0/PNP0C09:00/VPC2004:00/rfkill/rfkill0) (platform driver ideapad_acpi)
Nov 10 10:41:17 linux NetworkManager[750]: <info> WiFi hardware radio set enabled
Nov 10 10:41:17 linux NetworkManager[750]: <info> WWAN hardware radio set enabled
Nov 10 10:41:17 linux NetworkManager[750]: <info> Loaded device plugin: /usr/lib64/NetworkManager/libnm-device-plugin-adsl.so
Nov 10 10:41:17 linux NetworkManager[750]: <info> Loaded device plugin: /usr/lib64/NetworkManager/libnm-device-plugin-bluetooth.so
Nov 10 10:41:17 linux NetworkManager[750]: <info> Loaded device plugin: /usr/lib64/NetworkManager/libnm-device-plugin-wifi.so
Nov 10 10:41:17 linux NetworkManager[750]: <info> Loaded device plugin: /usr/lib64/NetworkManager/libnm-device-plugin-wwan.so
Nov 10 10:41:17 linux NetworkManager[750]: <info> WiFi enabled by radio killswitch; enabled by state file
Nov 10 10:41:18 linux NetworkManager[750]: <info> WWAN enabled by radio killswitch; enabled by state file
Nov 10 10:41:19 linux NetworkManager[750]: <info> WiMAX enabled by radio killswitch; enabled by state file
Nov 10 10:41:19 linux NetworkManager[750]: <info> Networking is enabled by state file
Nov 10 10:41:19 linux NetworkManager[750]: <info> Setting system hostname to 'linux.site' (from system configuration)
Nov 10 10:41:19 linux.site NetworkManager[750]: <info> (lo): link connected
Nov 10 10:41:19 linux.site NetworkManager[750]: <info> (lo): carrier is ON
Nov 10 10:41:19 linux.site NetworkManager[750]: <info> (lo): new Generic device (driver: 'unknown' ifindex: 1)
Nov 10 10:41:19 linux.site NetworkManager[750]: <info> (lo): exported as /org/freedesktop/NetworkManager/Devices/0
Nov 10 10:41:19 linux.site NetworkManager[750]: <info> (enp3s0): carrier is OFF
Nov 10 10:41:19 linux.site NetworkManager[750]: <info> (enp3s0): new Ethernet device (driver: 'atl1c' ifindex: 2)
Nov 10 10:41:19 linux.site NetworkManager[750]: <info> (enp3s0): exported as /org/freedesktop/NetworkManager/Devices/1
Nov 10 10:41:19 linux.site NetworkManager[750]: <info> (enp3s0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Nov 10 10:41:19 linux.site NetworkManager[750]: <info> (enp3s0): preparing device
Nov 10 10:41:19 linux.site NetworkManager[750]: <info> (enp3s0): created default wired connection 'Wired connection 1'
Nov 10 10:41:19 linux.site NetworkManager[750]: <info> (wlp4s0): using nl80211 for WiFi device control
Nov 10 10:41:19 linux.site NetworkManager[750]: <info> (wlp4s0): new 802.11 WiFi device (driver: 'iwlwifi' ifindex: 3)
Nov 10 10:41:19 linux.site NetworkManager[750]: <info> (wlp4s0): exported as /org/freedesktop/NetworkManager/Devices/2
Nov 10 10:41:19 linux.site NetworkManager[750]: <info> (wlp4s0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Nov 10 10:41:19 linux.site NetworkManager[750]: <info> (wlp4s0): preparing device
Nov 10 10:41:19 linux.site NetworkManager[750]: <info> use BlueZ version 5
Nov 10 10:41:19 linux.site NetworkManager[750]: <info> ModemManager available in the bus
Nov 10 10:41:19 linux.site NetworkManager[750]: <info> (wlp4s0) supports 5 scan SSIDs
Nov 10 10:41:19 linux.site NetworkManager[750]: <info> (wlp4s0): supplicant interface state: starting -> ready
Nov 10 10:41:19 linux.site NetworkManager[750]: <info> (wlp4s0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
Nov 10 10:41:19 linux.site NetworkManager[750]: <info> (wlp4s0): supplicant interface state: ready -> disconnected
Nov 10 10:41:19 linux.site NetworkManager[750]: <info> (wlp4s0) supports 5 scan SSIDs
Nov 10 10:41:19 linux.site NetworkManager[750]: <info> (wlp4s0): supplicant interface state: disconnected -> inactive
Nov 10 10:41:24 linux.site NetworkManager[750]: <info> startup complete
Nov 10 10:49:45 linux.site NetworkManager[750]: <info> Auto-activating connection 'part16m1 1'.
Nov 10 10:49:45 linux.site NetworkManager[750]: <info> Activation (wlp4s0) starting connection 'part16m1 1'
Nov 10 10:49:45 linux.site NetworkManager[750]: <info> Activation (wlp4s0) Stage 1 of 5 (Device Prepare) scheduled...
Nov 10 10:49:45 linux.site NetworkManager[750]: <info> Activation (wlp4s0) Stage 1 of 5 (Device Prepare) started...
Nov 10 10:49:45 linux.site NetworkManager[750]: <info> (wlp4s0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Nov 10 10:49:45 linux.site NetworkManager[750]: <info> NetworkManager state is now CONNECTING
Nov 10 10:49:45 linux.site NetworkManager[750]: <info> Activation (wlp4s0) Stage 2 of 5 (Device Configure) scheduled...
Nov 10 10:49:45 linux.site NetworkManager[750]: <info> Activation (wlp4s0) Stage 1 of 5 (Device Prepare) complete.
Nov 10 10:49:45 linux.site NetworkManager[750]: <info> Activation (wlp4s0) Stage 2 of 5 (Device Configure) starting...
Nov 10 10:49:45 linux.site NetworkManager[750]: <info> (wlp4s0): device state change: prepare -> config (reason 'none') [40 50 0]
Nov 10 10:49:45 linux.site NetworkManager[750]: <info> Activation (wlp4s0/wireless): connection 'part16m1 1' has security, and secrets exist.  No new secrets needed.
Nov 10 10:49:45 linux.site NetworkManager[750]: <info> Config: added 'ssid' value 'part16m1'
Nov 10 10:49:45 linux.site NetworkManager[750]: <info> Config: added 'scan_ssid' value '1'
Nov 10 10:49:45 linux.site NetworkManager[750]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
Nov 10 10:49:45 linux.site NetworkManager[750]: <info> Config: added 'auth_alg' value 'OPEN'
Nov 10 10:49:45 linux.site NetworkManager[750]: <info> Config: added 'psk' value '<omitted>'
Nov 10 10:49:45 linux.site NetworkManager[750]: <info> Activation (wlp4s0) Stage 2 of 5 (Device Configure) complete.
Nov 10 10:49:45 linux.site NetworkManager[750]: <info> Config: set interface ap_scan to 1
Nov 10 10:49:45 linux.site NetworkManager[750]: <info> (wlp4s0): supplicant interface state: inactive -> scanning
Nov 10 10:49:46 linux.site NetworkManager[750]: <info> (wlp4s0): supplicant interface state: scanning -> authenticating
Nov 10 10:49:46 linux.site NetworkManager[750]: <info> (wlp4s0): supplicant interface state: authenticating -> associating
Nov 10 10:49:46 linux.site NetworkManager[750]: <info> (wlp4s0): supplicant interface state: associating -> associated
Nov 10 10:49:47 linux.site NetworkManager[750]: <info> (wlp4s0): supplicant interface state: associated -> 4-way handshake
Nov 10 10:49:47 linux.site NetworkManager[750]: <info> (wlp4s0): supplicant interface state: 4-way handshake -> completed
Nov 10 10:49:47 linux.site NetworkManager[750]: <info> Activation (wlp4s0/wireless) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'part16m1'.
Nov 10 10:49:47 linux.site NetworkManager[750]: <info> Activation (wlp4s0) Stage 3 of 5 (IP Configure Start) scheduled.
Nov 10 10:49:47 linux.site NetworkManager[750]: <info> Activation (wlp4s0) Stage 3 of 5 (IP Configure Start) started...
Nov 10 10:49:47 linux.site NetworkManager[750]: <info> (wlp4s0): device state change: config -> ip-config (reason 'none') [50 70 0]
Nov 10 10:49:47 linux.site NetworkManager[750]: <info> Activation (wlp4s0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Nov 10 10:49:47 linux.site NetworkManager[750]: <info> dhclient started with pid 1519
Nov 10 10:49:47 linux.site NetworkManager[750]: <info> Activation (wlp4s0) Stage 3 of 5 (IP Configure Start) complete.
Nov 10 10:49:54 linux.site NetworkManager[750]: Internet Systems Consortium DHCP Client 4.2.6
Nov 10 10:49:54 linux.site NetworkManager[750]: Copyright 2004-2014 Internet Systems Consortium.
Nov 10 10:49:54 linux.site NetworkManager[750]: All rights reserved.
Nov 10 10:49:54 linux.site NetworkManager[750]: For info, please visit https://www.isc.org/software/dhcp/
Nov 10 10:49:54 linux.site NetworkManager[750]: <info> (wlp4s0): DHCPv4 state changed nbi -> preinit
Nov 10 10:49:54 linux.site NetworkManager[750]: Listening on LPF/wlp4s0/8c:a9:82:65:e3:a6
Nov 10 10:49:54 linux.site NetworkManager[750]: Sending on   LPF/wlp4s0/8c:a9:82:65:e3:a6
Nov 10 10:49:54 linux.site NetworkManager[750]: Sending on   Socket/fallback
Nov 10 10:49:54 linux.site NetworkManager[750]: DHCPDISCOVER on wlp4s0 to 255.255.255.255 port 67 interval 2 (xid=0x6a69a2fe)
Nov 10 10:49:54 linux.site NetworkManager[750]: DHCPOFFER from 192.168.100.1
Nov 10 10:49:59 linux.site NetworkManager[750]: DHCPREQUEST on wlp4s0 to 255.255.255.255 port 67 (xid=0x6a69a2fe)
Nov 10 10:49:59 linux.site NetworkManager[750]: DHCPACK from 192.168.100.1 (xid=0x6a69a2fe)
Nov 10 10:49:59 linux.site NetworkManager[750]: <info> (wlp4s0): DHCPv4 state changed preinit -> bound
Nov 10 10:49:59 linux.site NetworkManager[750]: <info>   address 192.168.100.2
Nov 10 10:49:59 linux.site NetworkManager[750]: <info>   plen 24 (255.255.255.0)
Nov 10 10:49:59 linux.site NetworkManager[750]: <info>   gateway 192.168.100.1
Nov 10 10:49:59 linux.site NetworkManager[750]: <info>   server identifier 192.168.100.1
Nov 10 10:49:59 linux.site NetworkManager[750]: <info>   lease time 259200
Nov 10 10:49:59 linux.site NetworkManager[750]: <info>   nameserver '10.0.0.1'
Nov 10 10:49:59 linux.site NetworkManager[750]: <info>   nameserver '194.50.156.5'
Nov 10 10:49:59 linux.site NetworkManager[750]: <info> Activation (wlp4s0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
Nov 10 10:49:59 linux.site NetworkManager[750]: <info> Activation (wlp4s0) Stage 5 of 5 (IPv4 Commit) started...
Nov 10 10:49:59 linux.site NetworkManager[750]: <info> (wlp4s0): device state change: ip-config -> ip-check (reason 'none') [70 80 0]
Nov 10 10:49:59 linux.site NetworkManager[750]: <info> Activation (wlp4s0) Stage 5 of 5 (IPv4 Commit) complete.
Nov 10 10:49:59 linux.site NetworkManager[750]: bound to 192.168.100.2 -- renewal in 107222 seconds.
Nov 10 10:49:59 linux.site NetworkManager[750]: <info> (wlp4s0): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
Nov 10 10:49:59 linux.site NetworkManager[750]: <info> (wlp4s0): device state change: secondaries -> activated (reason 'none') [90 100 0]
Nov 10 10:49:59 linux.site NetworkManager[750]: <info> NetworkManager state is now CONNECTED_LOCAL
Nov 10 10:49:59 linux.site NetworkManager[750]: <info> NetworkManager state is now CONNECTED_GLOBAL
Nov 10 10:49:59 linux.site NetworkManager[750]: <info> Policy set 'part16m1 1' (wlp4s0) as default for IPv4 routing and DNS.
Nov 10 10:49:59 linux.site NetworkManager[750]: <info> Activation (wlp4s0) successful, device activated.

Thanks for the help

I do not believe it is the network that slows you down.

Look at this:

Nov 10 10:41:19 linux.site NetworkManager[750]: <info> (wlp4s0): supplicant interface state: disconnected -> inactive
Nov 10 10:41:24 linux.site NetworkManager[750]: <info> startup complete
Nov 10 10:49:45 linux.site NetworkManager[750]: <info> Auto-activating connection 'part16m1 1'.

There must be something else between 10:41:24 and 10:49:45 which keeps your cpu busy.

Maybe you do the journalctl again without the “grep Network” and check what is happening in between of the two time stamps mentionned.

Hi Suworow,

czanat@linux:~> journalctl -b
-- Logs begin at Fri 2014-11-07 13:34:42 CET, end at Mon 2014-11-10 13:22:43 CET
Nov 10 13:19:43 linux.site org.a11y.Bus[1350]: Activating service name='org.a11y
Nov 10 13:19:48 linux.site org.a11y.Bus[1350]: Successfully activated service 'o
Nov 10 13:19:48 linux.site org.a11y.atspi.Registry[1426]: SpiRegistry daemon is 
Nov 10 13:19:48 linux.site org.a11y.atspi.Registry[1426]: Xlib:  extension "XEVI
Nov 10 13:19:48 linux.site gnome-session[1285]: gnome-keyring-daemon: insufficie
Nov 10 13:19:49 linux.site gnome-session[1285]: gnome-keyring-daemon: insufficie
Nov 10 13:19:49 linux.site gnome-session[1285]: gnome-keyring-daemon: insufficie
Nov 10 13:19:49 linux.site gnome-session[1285]: SSH_AUTH_SOCK=/run/user/1000/key
Nov 10 13:19:49 linux.site gnome-session[1285]: SSH_AUTH_SOCK=/run/user/1000/key
Nov 10 13:19:49 linux.site gnome-session[1285]: gnome-keyring-daemon: insufficie
Nov 10 13:19:49 linux.site gnome-session[1285]: SSH_AUTH_SOCK=/run/user/1000/key
Nov 10 13:19:49 linux.site gnome-session[1285]: GPG_AGENT_INFO=/run/user/1000/ke
Nov 10 13:19:49 linux.site pulseaudio[1513]: [pulseaudio] pid.c: Daemon already 
Nov 10 13:19:49 linux.site gnome-session[1285]: (gnome-settings-daemon:1454): Gt
Nov 10 13:19:49 linux.site gnome-session[1285]: (gnome-shell:1594): Gtk-WARNING 
Nov 10 13:19:50 linux.site gnome-session[1285]: (gnome-shell:1594): Gtk-WARNING 
Nov 10 13:19:51 linux.site org.gnome.OnlineAccounts[1350]: goa-daemon-Message: g
Nov 10 13:19:51 linux.site org.gnome.Caribou.Daemon[1350]: (caribou:1645): Gtk-W
Nov 10 13:19:51 linux.site org.gtk.Private.AfcVolumeMonitor[1350]: Volume monito
Nov 10 13:19:51 linux.site gnome-session[1285]: (nm-applet:1681): Gtk-WARNING **
Nov 10 13:19:51 linux.site gnome-session[1285]: (org.gnome.Software:1687): Gtk-W
Nov 10 13:19:51 linux.site org.gnome.evolution.dataserver.Sources3[1350]: Bus na
Nov 10 13:19:51 linux.site gnome-session[1285]: (nm-applet:1681): GLib-GObject-W
Nov 10 13:19:51 linux.site gnome-session[1285]: (nm-applet:1681): GLib-GObject-W
Nov 10 13:19:51 linux.site gnome-session[1285]: (nm-applet:1681): GLib-GObject-W
Nov 10 13:19:51 linux.site gnome-session[1285]: (nm-applet:1681): GLib-GObject-W
Nov 10 13:19:51 linux.site gnome-session[1285]: (canberra-gtk-play:1689): Gtk-WA
Nov 10 13:19:52 linux.site gnome-session[1285]: Gjs-Message: JS LOG: loading use
Nov 10 13:19:52 linux.site gnome-session[1285]: Failed to play sound: File or da
Nov 10 13:19:52 linux.site org.gnome.Caribou.Daemon[1350]: ** (caribou:1645): WA
Nov 10 13:19:52 linux.site gnome-session[1285]: (uint32 1,)
Nov 10 13:19:52 linux.site gnome-session[1285]: (evolution-alarm-notify:1685): G
Nov 10 13:19:52 linux.site gnome-session[1285]: vmware-user: could not open /pro
Nov 10 13:19:52 linux.site vmusr[1730]:  warning] [vmtoolsd] The vmusr service 
Nov 10 13:19:54 linux.site vmusr[1730]:  warning] [Gtk] Unable to locate theme 
Nov 10 13:19:54 linux.site vmusr[1730]:  warning] [Gtk] Unable to locate theme 
Nov 10 13:19:54 linux.site vmusr[1730]:  warning] [Gtk] Unable to locate theme 
Nov 10 13:19:54 linux.site gnome-session[1285]: (gnome-shell:1594): GLib-GObject
Nov 10 13:19:54 linux.site org.gnome.evolution.dataserver.Calendar4[1350]: Bus n
Nov 10 13:19:55 linux.site gnome-session[1285]: Gjs-Message: JS WARNING: [/home/
Nov 10 13:19:55 linux.site gnome-session[1285]: Gjs-Message: JS WARNING: [/home/
Nov 10 13:19:55 linux.site gnome-session[1285]: Gjs-Message: JS WARNING: [/home/
Nov 10 13:19:55 linux.site gnome-session[1285]: Gjs-Message: JS WARNING: [/home/
Nov 10 13:19:55 linux.site gnome-session[1285]: Gjs-Message: JS WARNING: [/home/
Nov 10 13:19:55 linux.site org.gnome.Caribou.Daemon[1350]: ** (caribou:1645): WA
Nov 10 13:19:55 linux.site gnome-session[1285]: (gnome-shell:1594): GLib-GObject
Nov 10 13:19:55 linux.site gnome-session[1285]: (gnome-shell:1594): mutter-WARNI
Nov 10 13:19:55 linux.site gnome-session[1285]: (gnome-shell:1594): mutter-WARNI
Nov 10 13:19:55 linux.site gnome-session[1285]: (gnome-shell:1594): GLib-GObject
Nov 10 13:19:55 linux.site gnome-session[1285]: (gnome-shell:1594): GLib-GObject
Nov 10 13:19:55 linux.site gnome-session[1285]: (gnome-shell:1594): GLib-GObject
Nov 10 13:19:55 linux.site gnome-session[1285]: (gnome-shell:1594): GLib-GObject
Nov 10 13:19:55 linux.site gnome-session[1285]: (gnome-shell:1594): GLib-GObject
Nov 10 13:19:55 linux.site gnome-session[1285]: (gnome-shell:1594): GLib-GObject
Nov 10 13:19:55 linux.site gnome-session[1285]: Window manager warning: "XF86Hel
Nov 10 13:19:56 linux.site gnome-session[1285]: GNOME Shell started at Mon Nov 1
Nov 10 13:20:00 linux.site firefox.desktop[1781]: (process:1781): GLib-CRITICAL 
Nov 10 13:20:00 linux.site firefox.desktop[1781]: (firefox:1781): Gtk-WARNING **
Nov 10 13:20:00 linux.site firefox.desktop[1781]: (firefox:1781): Gtk-WARNING **
Nov 10 13:20:00 linux.site firefox.desktop[1781]: (firefox:1781): Gtk-WARNING **
  

I can’t insert all the results of journalctl -b here as this web page won’t allow it, so I am placing part of it.

I was told that it is the network service that takes so long.

But journald takes a comparable time. Is it a laptop? Does it have a slow disk (e.g. SATA-I)?
I had even worse problems, see if disabling journal to disk helps, writing “Storage=volatile” in /etc/systemd/journald.conf
If so, you may choose to limit the space used on disk by the Journal.

Your output suggests you have your WiFi radio on (and connecting) <and> an active wired connection simultaneously.

If both wired and wireless connect to Network(s) that connect to the Internet, that’s wrong.
The wireless might be connecting to your own network or can be connecting to a neighboring network.
Even worse is if the wired and wireless networks are configured with the same networking (same address space, and possibly even same DG address).

If connected by wire (802.3), then disable your wireless.
If your machine doesn’t have a hardware switch, you can use rfkill (looks like it’s already installed) to disable your wireless interface by software.
If you wish to use your wireless, then physically unplug the wired network cable from your machine.

Should solve your problem.

BTW - One of the first things you should always do when troubleshooting a network issue is to print out your network interfaces using either of the following commands, which would have revealed your 2 connected networks immediately

ip addr
ifconfig

TSU

Like I said in the other post, I came here because someone adviced me to do so, considering that the Network Manager service is taking too long.
It looks like, the problem is in starting the display manager service. And, I cannot go on posting this is every section.

No, I am not using both wired and wireless. I use only wireless as I carry my laptop in the premises. In the other post, I gave systemd-analyze blame for this Opensuse and the Debian install for comparing. Same laptop, same wireless, same systemd, same Gnome 3.14.1. The Debian install is taking 1/3 of the time Opensuse takes.

If you can find a solution, TSU, I’d be much obliged.

The things you asked:

linux:/home/czanat # ifconfig
enp3s0    Link encap:Ethernet  HWaddr F0:DE:F1:4C:5C:87  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

wlp4s0    Link encap:Ethernet  HWaddr 8C:A9:82:65:E3:A6  
          inet addr:192.168.100.2  Bcast:192.168.100.255  Mask:255.255.255.0
          inet6 addr: fe80::8ea9:82ff:fe65:e3a6/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:9646 errors:0 dropped:0 overruns:0 frame:0
          TX packets:9572 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:7865778 (7.5 Mb)  TX bytes:1313411 (1.2 Mb)

czanat@linux:~> ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: enp3s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
    link/ether f0:de:f1:4c:5c:87 brd ff:ff:ff:ff:ff:ff
3: wlp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 8c:a9:82:65:e3:a6 brd ff:ff:ff:ff:ff:ff
    inet 192.168.100.2/24 brd 192.168.100.255 scope global dynamic wlp4s0
       valid_lft 256981sec preferred_lft 256981sec
    inet6 fe80::8ea9:82ff:fe65:e3a6/64 scope link 
       valid_lft forever preferred_lft forever

If you can help, TSU, I’d be much obliged.

On 2014-11-10 16:46, OrsoBruno wrote:

> Code:
> --------------------
> > >
> > └─network.target @1min 11.931s
> > └─NetworkManager.service @15.862s +56.068s
> > └─systemd-journald.service @1min 10.840s
> >
> --------------------
>>>
>>
>> NetworkManager.service takes quite a long time.
>
> But journald takes a comparable time.

No, it does not. The “@” means when it is started, the “+” how long it
takes. NM takes 56 seconds to complete, journald nothing.


Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

On 2014-11-10 11:06, Chdslv wrote:

> Code:
> --------------------
> linux:/home/czanat # journalctl -b |grep Network
> Nov 10 10:41:15 linux NetworkManager[750]: <info> NetworkManager (version 0.9.10.0) is starting…

4 seconds of things

> Nov 10 10:41:19 linux.site NetworkManager[750]: <info> ModemManager available in the bus
> Nov 10 10:41:19 linux.site NetworkManager[750]: <info> (wlp4s0) supports 5 scan SSIDs
> Nov 10 10:41:19 linux.site NetworkManager[750]: <info> (wlp4s0): supplicant interface state: starting -> ready
> Nov 10 10:41:19 linux.site NetworkManager[750]: <info> (wlp4s0): device state change: unavailable -> disconnected (reason ‘supplicant-available’) [20 30 42]
> Nov 10 10:41:19 linux.site NetworkManager[750]: <info> (wlp4s0): supplicant interface state: ready -> disconnected
> Nov 10 10:41:19 linux.site NetworkManager[750]: <info> (wlp4s0) supports 5 scan SSIDs
> Nov 10 10:41:19 linux.site NetworkManager[750]: <info> (wlp4s0): supplicant interface state: disconnected -> inactive

5 seconds of nothing

> Nov 10 10:41:24 linux.site NetworkManager[750]: <info> startup complete

Minutes of nothing, then more activity - maybe after login, so not
related to issue.

> Nov 10 10:49:45 linux.site NetworkManager[750]: <info> Auto-activating connection ‘part16m1 1’.
> Nov 10 10:49:45 linux.site NetworkManager[750]: <info> Activation (wlp4s0) starting connection ‘part16m1 1’

> Nov 10 10:49:45 linux.site NetworkManager[750]: <info> Activation (wlp4s0) Stage 1 of 5 (Device Prepare) scheduled…

> Nov 10 10:49:45 linux.site NetworkManager[750]: <info> (wlp4s0): supplicant interface state: inactive → scanning
> Nov 10 10:49:46 linux.site NetworkManager[750]: <info> (wlp4s0): supplicant interface state: scanning → authenticating
> Nov 10 10:49:46 linux.site NetworkManager[750]: <info> (wlp4s0): supplicant interface state: authenticating → associating
> Nov 10 10:49:46 linux.site NetworkManager[750]: <info> (wlp4s0): supplicant interface state: associating → associated
> Nov 10 10:49:47 linux.site NetworkManager[750]: <info> (wlp4s0): supplicant interface state: associated → 4-way handshake

> Nov 10 10:49:47 linux.site NetworkManager[750]: <info> Activation (wlp4s0) Stage 3 of 5 (IP Configure Start) complete.
> Nov 10 10:49:54 linux.site NetworkManager[750]: Internet Systems Consortium DHCP Client 4.2.6

> Nov 10 10:49:54 linux.site NetworkManager[750]: DHCPDISCOVER on wlp4s0 to 255.255.255.255 port 67 interval 2 (xid=0x6a69a2fe)
> Nov 10 10:49:54 linux.site NetworkManager[750]: DHCPOFFER from 192.168.100.1
> Nov 10 10:49:59 linux.site NetworkManager[750]: DHCPREQUEST on wlp4s0 to 255.255.255.255 port 67 (xid=0x6a69a2fe)

> Nov 10 10:49:59 linux.site NetworkManager[750]: <info> Activation (wlp4s0) successful, device activated.
>
> --------------------

We are looking at the wrong log, or wrong point. We have to find 56" of
some network initialization problem.


Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

So, what could be the solution to this problem?

On 2014-11-11 11:46, Chdslv wrote:
>
> So, what could be the solution to this problem?

I don’t know. You have to investigate it. I’m not there. I gave you
clues to look further.


Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)