Your message dated Fri, 7 Feb 2020 18:29:25 +0100
with message-id <[email protected]>
and subject line Re: network-manager 1.22.4 still failing dhcp on some wifi 
networks
has caused the Debian Bug report #949530,
regarding network-manager 1.22.4 still failing dhcp on some wifi networks
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.)


-- 
949530: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949530
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: network-manager
Version: 1.22.4-1
Severity: important

Dear Maintainer,

For some wifi networks, network-manager fails to join the network.  1.22.4 was 
a big improvement over 1.22.2, but there are still some problems.
It logs lines like these:

NetworkManager[854]: <info>  [1578839858.0531] device (p2p-dev-wlp4s0): 
supplicant management interface state: associated -> complet>
NetworkManager[854]: <info>  [1578839858.0534] device (wlp4s0): state change: 
config -> ip-config (reason 'none', sys-iface-state: '>
NetworkManager[854]: <info>  [1578839858.0551] dhcp4 (wlp4s0): activation: 
beginning transaction (timeout in 45 seconds)
NetworkManager[854]: <warn>  [1578839861.0781] dhcp4 (wlp4s0): selecting lease 
failed: 12
NetworkManager[854]: <warn>  [1578839864.7164] dhcp4 (wlp4s0): selecting lease 
failed: 12
NetworkManager[854]: <warn>  [1578839873.5769] dhcp4 (wlp4s0): selecting lease 
failed: 12
NetworkManager[854]: <warn>  [1578839892.0217] dhcp4 (wlp4s0): selecting lease 
failed: 12
NetworkManager[854]: <info>  [1578839901.4961] manager: sleep: sleep requested 
(sleeping: no  enabled: yes)
NetworkManager[854]: <info>  [1578839901.4965] device (enp0s31f6): state 
change: unavailable -> unmanaged (reason 'sleeping', sys-if>

I used to be able to join this network with previous versions of 
network-manager.

The gitlab issue links a commit after 1.22.4.

Issue: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/324
Commit: 
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/c19eefc6ec9d0a52f4d3ce75e70cfd6dab60aa2f

I've seen the log message "Activation: Stage 5 of 5 (IPv4 Commit) error 
accepting lease: failed to accept lease: Cannot allocate memory"
but I don't get this every time.

If you roll an update that includes commit c19eefc6, I will check whether this 
fixes the problem.

-BenRI



*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (2000, 'unstable'), (1999, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.4.0-trunk-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages network-manager depends on:
ii  adduser                3.118
ii  dbus                   1.12.16-2
ii  init-system-helpers    1.57
ii  libaudit1              1:2.8.5-2+b1
ii  libbluetooth3          5.50-1+b1
ii  libc6                  2.29-9
ii  libcurl3-gnutls        7.67.0-2
ii  libglib2.0-0           2.62.4-1
ii  libgnutls30            3.6.11.1-2
ii  libjansson4            2.12-1
ii  libmm-glib0            1.10.4-0.1
ii  libndp0                1.6-1+b1
ii  libnewt0.52            0.52.21-4
ii  libnm0                 1.22.4-1
ii  libpam-systemd         244-3
ii  libpolkit-agent-1-0    0.105-26
ii  libpolkit-gobject-1-0  0.105-26
ii  libpsl5                0.20.2-2
ii  libreadline8           8.0-3
ii  libselinux1            3.0-1
ii  libsystemd0            244-3
ii  libteamdctl0           1.30-1
ii  libudev1               244-3
ii  libuuid1               2.34-0.1
ii  policykit-1            0.105-26
ii  udev                   244-3
ii  wpasupplicant          2:2.9-6

Versions of packages network-manager recommends:
ii  crda                         3.18-1
ii  dnsmasq-base [dnsmasq-base]  2.80-1.1
ii  iptables                     1.8.4-1
ii  modemmanager                 1.10.4-0.1
ii  ppp                          2.4.7-2+4.1+b1

Versions of packages network-manager suggests:
ii  isc-dhcp-client  4.4.1-2
pn  libteam-utils    <none>

-- no debconf information

--- End Message ---
--- Begin Message ---
Version: 1.22.6-1

Am 07.02.2020 um 16:25 schrieb Benjamin Redelings:
> Hi,
> 
> OK, 1.22.6 works for the same router that 1.22.4 didn't work. This is on
> a new laptop, but it seems unlikely that the hardware was causing the
> problem.


Thank you for reporting back. Closing the bug report then.

Regards,
Michael


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---

Reply via email to