[Pkg-utopia-maintainers] Bug#949530: network-manager 1.22.4 still failing dhcp on some wifi networks

[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.

-BenRI

On 1/31/20 7:49 PM, Michael Biebl wrote:
> On Tue, 21 Jan 2020 12:44:17 -0500 Benjamin Redelings
> <benjamin.redelings at gmail.com> wrote:
>> 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.
> Please test with 1.22.6 and report back
>