--- Begin Message ---
Package: network-manager
Version: 1.2.4-2
Severity: normal
Dear Maintainer,
* What led up to the situation?
* Since my upgrade last Friday this happens on every boot.
* Before the login manager is displayed, I can see the following message,
waiting the full 90s:
[ *** ] A start job is running for Network Manager (30s/1min 30s)
* Sometimes I could see the following output on the console just before
the login manager takes over, but I have not seen those since installing
systemd from sid 231-5 and -6 instead of -4 from testing:
[FAILED] Failed to start Network Manager.
[DEPEND] Dependency failed for Network Manager Wait Online.
* The output of "journalctl -u NetworkManager" contains a first failed start
during boot, followed by a successful start (I have seen two failed starts
followed by a successful start, too):
Sep 12 12:28:31 pc systemd[1]: Starting Network Manager...
Sep 12 12:30:01 pc systemd[1]: NetworkManager.service: Start operation timed
out. Terminating.
Sep 12 12:30:01 pc systemd[1]: Failed to start Network Manager.
Sep 12 12:30:01 pc systemd[1]: NetworkManager.service: Unit entered failed
state.
Sep 12 12:30:01 pc systemd[1]: NetworkManager.service: Failed with result
'timeout'.
Sep 12 12:30:01 pc systemd[1]: NetworkManager.service: Service hold-off time
over, scheduling restart.
Sep 12 12:30:01 pc systemd[1]: Stopped Network Manager.
Sep 12 12:30:01 pc systemd[1]: Starting Network Manager...
Sep 12 12:31:23 pc NetworkManager[921]: <info> [1473697883.1057]
NetworkManager (version 1.2.4) is starting...
Sep 12 12:31:23 pc NetworkManager[921]: <info> [1473697883.1064] Read config:
/etc/NetworkManager/NetworkManager.conf
* What exactly did you do (or not do) that was effective (or ineffective)?
* I tried many things, none of which helped
* Plugging in the wired network cable to see if earlier network access
helps.
(Usually the wireless network connection is established after I log in.)
* Using "systemd-analyze critical-chain" I saw virtualbox at the top of the
chain, but purging it did not help.
* I tried to set logging level to DEBUG in
/etc/NetworkManager/NetworkManager.conf,
but only the successful second start of NetworkManager logged with DEBUG
level,
the output for the first start was unchanged (same as above).
* I tried commenting out CapabilityBoundingSet, ProtectSystem, and
ProtectHome as
described in #820174, nothing changed.
* Downgrading network-manager to the pre-upgrade version 1.2.2-2 did not
help.
* Upgrading network-manager to 1.4.0-3 from sid, nothing changed (well,
actually
the plasma desktop client to network-manager failed to pick up that a
network
connection was established).
* What outcome did you expect instead?
* I expect my system to boot in 30s not 3min. And I don't expect
NetworkManager
to fail to start for no obvious reason. So please help me figure out why
this
happens and how it can be fixed.
* I am adding some system information below that was asked for in #820174 and I
hope
is useful:
# systemctl status NetworkManager.service
● NetworkManager.service - Network Manager
Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor
preset: enabled)
Active: active (running) since Mon 2016-09-12 12:51:13 EDT; 27min ago
Docs: man:NetworkManager(8)
Main PID: 1012 (NetworkManager)
Tasks: 5 (limit: 4915)
CGroup: /system.slice/NetworkManager.service
├─1012 /usr/sbin/NetworkManager --no-daemon
└─1301 /sbin/dhclient -d -q -sf
/usr/lib/NetworkManager/nm-dhcp-helper -pf /var/run/dhclient-wlp3s0.pid -lf
/var/lib/NetworkManager/dhclien
Sep 12 12:51:20 pc NetworkManager[1012]: <info> [1473699080.2381] policy: set
'GuestWiFi' (wlp3s0) as default for IPv4 routing and DN
Sep 12 12:51:20 pc NetworkManager[1012]: <info> [1473699080.2397] device
(wlp3s0): Activation: successful, device activated.
Sep 12 12:51:20 pc NetworkManager[1012]: <info> [1473699080.2403] manager:
startup complete
Sep 12 12:51:20 pc dhclient[1301]: bound to 192.168.65.26 -- renewal in 5900
seconds.
Sep 12 13:07:08 pc NetworkManager[1012]: <warn> [1473700028.0004]
sup-iface[0x179fb80,wlp3s0]: connection disconnected (reason -4)
Sep 12 13:07:08 pc NetworkManager[1012]: <info> [1473700028.0050] device
(wlp3s0): supplicant interface state: completed -> disconnected
Sep 12 13:07:08 pc NetworkManager[1012]: <info> [1473700028.1048] device
(wlp3s0): supplicant interface state: disconnected -> scanning
Sep 12 13:07:08 pc NetworkManager[1012]: <info> [1473700028.3096] device
(wlp3s0): supplicant interface state: scanning -> authenticating
Sep 12 13:07:08 pc NetworkManager[1012]: <info> [1473700028.3162] device
(wlp3s0): supplicant interface state: authenticating -> associating
Sep 12 13:07:08 pc NetworkManager[1012]: <info> [1473700028.4372] device
(wlp3s0): supplicant interface state: associating -> completed
$ systemctl --version
systemd 231
+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP
+GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN
$ systemd-delta
[EXTENDED] /lib/systemd/system/systemd-resolved.service →
/lib/systemd/system/systemd-resolved.service.d/resolvconf.conf
[EXTENDED] /lib/systemd/system/systemd-timesyncd.service →
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
[EXTENDED] /lib/systemd/system/rc-local.service →
/lib/systemd/system/rc-local.service.d/debian.conf
$ findmnt
TARGET SOURCE FSTYPE OPTIONS
/ /dev/sda1 btrfs
rw,relatime,ssd,space_cache,subvolid=5,subvol=/
├─/sys sysfs sysfs
rw,nosuid,nodev,noexec,relatime
│ ├─/sys/kernel/security securityfs securityfs
rw,nosuid,nodev,noexec,relatime
│ ├─/sys/fs/cgroup tmpfs tmpfs
ro,nosuid,nodev,noexec,mode=755
│ │ ├─/sys/fs/cgroup/systemd cgroup cgroup
rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=sys
│ │ ├─/sys/fs/cgroup/cpu,cpuacct cgroup cgroup
rw,nosuid,nodev,noexec,relatime,cpu,cpuacct
│ │ ├─/sys/fs/cgroup/devices cgroup cgroup
rw,nosuid,nodev,noexec,relatime,devices
│ │ ├─/sys/fs/cgroup/cpuset cgroup cgroup
rw,nosuid,nodev,noexec,relatime,cpuset
│ │ ├─/sys/fs/cgroup/net_cls,net_prio
│ │ │ cgroup cgroup
rw,nosuid,nodev,noexec,relatime,net_cls,net_prio
│ │ ├─/sys/fs/cgroup/pids cgroup cgroup
rw,nosuid,nodev,noexec,relatime,pids
│ │ ├─/sys/fs/cgroup/freezer cgroup cgroup
rw,nosuid,nodev,noexec,relatime,freezer
│ │ ├─/sys/fs/cgroup/perf_event cgroup cgroup
rw,nosuid,nodev,noexec,relatime,perf_event
│ │ ├─/sys/fs/cgroup/memory cgroup cgroup
rw,nosuid,nodev,noexec,relatime,memory
│ │ └─/sys/fs/cgroup/blkio cgroup cgroup
rw,nosuid,nodev,noexec,relatime,blkio
│ ├─/sys/fs/pstore pstore pstore
rw,nosuid,nodev,noexec,relatime
│ └─/sys/kernel/debug debugfs debugfs rw,relatime
├─/proc proc proc
rw,nosuid,nodev,noexec,relatime
│ └─/proc/sys/fs/binfmt_misc systemd-1 autofs
rw,relatime,fd=33,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=1487
├─/dev udev devtmpfs
rw,nosuid,relatime,size=8054808k,nr_inodes=2013702,mode=755
│ ├─/dev/pts devpts devpts
rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000
│ ├─/dev/shm tmpfs tmpfs rw,nosuid,nodev
│ ├─/dev/mqueue mqueue mqueue rw,relatime
│ └─/dev/hugepages hugetlbfs hugetlbfs rw,relatime
├─/run tmpfs tmpfs
rw,nosuid,noexec,relatime,size=1612932k,mode=755
│ ├─/run/lock tmpfs tmpfs
rw,nosuid,nodev,noexec,relatime,size=5120k
│ ├─/run/user/109 tmpfs tmpfs
rw,nosuid,nodev,relatime,size=1612928k,mode=700,uid=109,gid=115
│ └─/run/user/1000 tmpfs tmpfs
rw,nosuid,nodev,relatime,size=1612928k,mode=700,uid=1000,gid=1000
├─/var /dev/sda7 btrfs
rw,relatime,ssd,space_cache,subvolid=5,subvol=/
├─/tmp /dev/sda6 btrfs
rw,relatime,ssd,space_cache,subvolid=5,subvol=/
└─/home /dev/sda8 btrfs
rw,relatime,ssd,space_cache,subvolid=5,subvol=/
$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda1 during installation
UUID=f05cc0a4-9381-46f3-9b67-d6a572417a0a / btrfs relatime
0 1
# /home was on /dev/sda8 during installation
UUID=688d5187-afe0-4eaf-a336-0e051994fe55 /home btrfs relatime
0 2
# /tmp was on /dev/sda6 during installation
UUID=e433911f-e9e8-4f7f-989c-573b3ea6911c /tmp btrfs relatime
0 2
# /var was on /dev/sda7 during installation
UUID=07cadc10-d17e-4cfe-87c6-8c43d47cf371 /var btrfs relatime
0 2
# swap was on /dev/sda5 during installation
UUID=c3abded8-dd65-4c59-bfe6-8ea0b4f4cc54 none swap sw
0 0
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (500, 'testing'), (50, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages network-manager depends on:
ii adduser 3.115
ii dbus 1.10.10-1
ii init-system-helpers 1.42
ii libaudit1 1:2.6.6-1
ii libbluetooth3 5.36-1+b2
ii libc6 2.23-5
ii libglib2.0-0 2.49.6-1
ii libgnutls30 3.5.3-4
ii libgudev-1.0-0 230-3
ii libmm-glib0 1.6.0-1
ii libndp0 1.6-1
ii libnewt0.52 0.52.18-3
ii libnl-3-200 3.2.27-1
ii libnm0 1.2.4-2
ii libpam-systemd 231-6
ii libpolkit-agent-1-0 0.105-16
ii libpolkit-gobject-1-0 0.105-16
ii libreadline6 6.3-8+b4
ii libselinux1 2.5-3
ii libsoup2.4-1 2.55.90-1
ii libsystemd0 231-6
ii libteamdctl0 1.26-1
ii libuuid1 2.28.1-1
ii lsb-base 9.20160629
ii policykit-1 0.105-16
ii udev 231-6
ii wpasupplicant 2.5-2+v2.4-2
Versions of packages network-manager recommends:
ii crda 3.13-1+b1
pn dnsmasq-base <none>
ii iptables 1.6.0-3
ii iputils-arping 3:20150815-2
ii isc-dhcp-client 4.3.4-1
pn modemmanager <none>
ii ppp 2.4.7-1+3
Versions of packages network-manager suggests:
pn libteam-utils <none>
-- no debconf information
--- End Message ---
signature.asc
