From: codingHahn <codingHahn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] NetworkManager 1.22.2 no ipv4 address
Date: Thu, 07 Jan 2021 15:35:15 +0100 [thread overview]
Message-ID: <20210107143515.sH4wAZMttk-8Qiz5pT_uNj5TcdxsrhfHACRfPeiMmS4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-18434@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 881 bytes --]
Closed issue by codingHahn on void-packages repository
https://github.com/void-linux/void-packages/issues/18434
Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System
* xuname:
`Void 5.4.13_2 x86_64 GenuineIntel notuptodate rrrmDFFFFFFFFFFFFFFFF`
* package:
*NetworkManager-1.22.2_1*
### Expected behavior
When connecting to a Wifi AP, automatically fetch ipv4 with dhcp
### Actual behavior
No ipv4 address on wifi interface
### Steps to reproduce the behavior
Install the latest version.
The same problem happened at 36c3, as mentioned here https://github.com/void-linux/void-packages/pull/13560#issuecomment-569531959 . I currently do not have time to test this further. Downgrading to 1.18 for now.
prev parent reply other threads:[~2021-01-07 14:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-20 21:02 [ISSUE] " voidlinux-github
2020-01-20 21:38 ` voidlinux-github
2020-01-21 7:44 ` voidlinux-github
2020-01-30 7:28 ` voidlinux-github
2020-01-30 7:30 ` voidlinux-github
2020-02-05 4:27 ` voidlinux-github
2020-02-07 5:24 ` voidlinux-github
2020-02-10 9:09 ` voidlinux-github
2020-02-10 9:10 ` voidlinux-github
2020-02-25 10:55 ` xtraeme
2020-02-25 20:00 ` yopito
2021-01-07 14:35 ` codingHahn
2021-01-07 14:35 ` codingHahn [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210107143515.sH4wAZMttk-8Qiz5pT_uNj5TcdxsrhfHACRfPeiMmS4@z \
--to=codinghahn@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).