On Tue, 24 Nov 2020, Cristian Ionescu-Idbohrn wrote:
>
> I interpret that this way: dns-mgr is confused; it concludes something
> has changed, queues DNS updates, concludes nothing has changed and
> does not commit anything (after first cleaning up resolv.conf).
>
> I both cases (wired,
Hi!
> On Mon, 23 Nov 2020, Matteo F. Vescovi wrote:
> > I just found few minutes to do some more testing and I discovered that
> > the weird behavior happens only when an OpenVPN connection is in place,
> > using any of the connections available (in my case, I was used to set
> > automatic VPN
On Mon, 23 Nov 2020, Matteo F. Vescovi wrote:
>
> FTR, I mainly use a 4G WWAN connection with an integrated module in my
> ThinkPad. Sometimes, I also use home/office Wi-Fi.
In my case, I use the laptop mostly at home, wired and wireless, same
router, dhcp aquired dns, no 4G involved.
> I just
Control: severity -1 important
Control: tag -1 -confirmed
Hi Michael!
On 2020-11-22 at 21:04 (+01), Matteo F. Vescovi wrote:
[...]
> I'm still digging in to find the culprit (possibly, a particular version
> of NM or MM that introduced the issue) but I need some more tests with
> alternative
On Sun, 22 Nov 2020, Matteo F. Vescovi wrote:
> On 2020-11-04 at 21:09 (+01), Cristian Ionescu-Idbohrn wrote:
>
> [...]
>
> > IMO, my remarks and comments are all _but_ snide and stupid. The
> > problem here, as I see it, is this maintainer's _arrogant_ attitude.
>
> Michael, sorry to say, but
Hi!
On 2020-11-04 at 21:09 (+01), Cristian Ionescu-Idbohrn wrote:
[...]
> IMO, my remarks and comments are all _but_ snide and stupid. The
> problem here, as I see it, is this maintainer's _arrogant_ attitude.
Michael, sorry to say, but Cristian is right:
I see no snide and stupid comments to
On Tue, 3 Nov 2020, Michael Biebl wrote:
> Am 03.11.2020 um 22:58 schrieb Cristian Ionescu-Idbohrn:
> > On Tue, 3 Nov 2020, Michael Biebl wrote:
> > >
> > > This bug report doesn't contain any relevant information to be
> > > useful
> >
> > Bisides the expected comment, what "relevant
On Wed, 4 Nov 2020, Michael Biebl wrote:
>
> Is NM the sole application touching /etc/resolv.conf?
> No other application adding entries to /etc/resolv.conf which NM
> doesn't know about?
I don't know. Is there a way to find out?
The mark in /etc/resolv.conf:
# Generated by
On Tue, 3 Nov 2020, Michael Biebl wrote:
>
> Anything which would make this bug report more more useful. Leave
> out any snide remarks and stupid comments if you can.
Alright, one stupid thing is the subject line. Should be:
# systemctl restart NetworkManager.service
instead (cut/paste
On Tue, 3 Nov 2020, Michael Biebl wrote:
>
> This bug report doesn't contain any relevant information to be useful
Bisides the expected comment, what "relevant information" would I need
to provide to make this bug report useful? I'd be more than happy to
provide it.
--
Cristian
Control: tags -1 + moreinfo
Am 03.11.20 um 16:45 schrieb Cristian Ionescu-Idbohrn:
Package: network-manager
Version: 1.27.91-1
Severity: grave
/etc/resolve.conf includes the expected configuration (WRT
nameservers) on bootup.
After upgrading network-manager and restarting it,
Package: network-manager
Version: 1.27.91-1
Severity: grave
/etc/resolve.conf includes the expected configuration (WRT
nameservers) on bootup.
After upgrading network-manager and restarting it, /etc/resolve.conf
(which is a symlink to /run/NetworkManager/resolv.conf) is basically
wiped out.
12 matches
Mail list logo
