Your message dated Fri, 3 Jan 2020 09:16:42 +0100
with message-id <[email protected]>
and subject line Re: Bug#947993: systemd: mysterious timeout 
/sys/subsystem/net/device/multi/user
has caused the Debian Bug report #947993,
regarding systemd: mysterious timeout /sys/subsystem/net/device/multi/user
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
947993: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947993
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 241-7~deb10u2
Severity: normal

Mysterious timeout booting on multi/user ficticious device


-- Package-specific info:

-- System Information:
Debian Release: 10.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1), LANGUAGE=en_US 
(charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages systemd depends on:
ii  adduser          3.118
ii  libacl1          2.2.53-4
ii  libapparmor1     2.13.2-10
ii  libaudit1        1:2.8.4-3
ii  libblkid1        2.33.1-0.1
ii  libc6            2.28-10
ii  libcap2          1:2.25-2
ii  libcryptsetup12  2:2.1.0-5+deb10u2
ii  libgcrypt20      1.8.4-5
ii  libgnutls30      3.6.7-4
ii  libgpg-error0    1.35-1
ii  libidn11         1.33-2.2
ii  libip4tc0        1.8.2-4
ii  libkmod2         26-1
ii  liblz4-1         1.8.3-1
ii  liblzma5         5.2.4-1
ii  libmount1        2.33.1-0.1
ii  libpam0g         1.3.1-5
ii  libseccomp2      2.3.3-4
ii  libselinux1      2.8-1+b1
ii  libsystemd0      241-7~deb10u2
ii  mount            2.33.1-0.1
ii  util-linux       2.33.1-0.1

Versions of packages systemd recommends:
ii  dbus            1.12.16-1
ii  libpam-systemd  241-7~deb10u2

Versions of packages systemd suggests:
ii  policykit-1        0.105-25
pn  systemd-container  <none>

Versions of packages systemd is related to:
pn  dracut           <none>
ii  initramfs-tools  0.133+deb10u1
ii  udev             241-7~deb10u2

-- Configuration Files:
/etc/systemd/journald.conf changed:
[Journal]
Storage=volatile
ForwardToSyslog=1


-- no debconf information

--- End Message ---
--- Begin Message ---
Am 03.01.20 um 04:46 schrieb Joshua Hudson:
> Log file
> 

You have enabled a [email protected] service which
has

Requires=sys-subsystem-net-devices-%i.device
After=sys-subsystem-net-devices-%i.device

So systemd waiting for that device is correct.

You should check your wpasupplicant configuration if you don't actually
want to configure such a multi-user device.

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---

Reply via email to