Thanks for the update. We'll have a look at this in a couple days.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884248
Title:
networkd-dispatcher gives corrupted information
To manage
In fact, I can confirm that hirsute package cleanly installs in focal
and (almost) fixes the issue.
Almost because the Address is set to the string "172.25.117.104 (DHCP4)"
which is not very useful. Expecting scripts to parse that string and
take it apart makes a farce of passing all that
Any idea whether this fix can be back-ported to focal?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884248
Title:
networkd-dispatcher gives corrupted information
To manage notifications about
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: networkd-dispatcher (Ubuntu Bionic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Any idea whether this fix can be back-ported to focal?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884248
Title:
networkd-dispatcher gives corrupted information
To manage notifications about
This bug was fixed in the package networkd-dispatcher - 2.1-1
---
networkd-dispatcher (2.1-1) unstable; urgency=medium
* New upstream release 2.1 (Closes: #968941)
- fixes parsing of current systemd (LP: #1884248)
-- Julian Andres Klode Tue, 10 Nov 2020 14:35:05
+0100
**
Uploaded in Debian as 2.1-1, pending processing there and autosync.
** Changed in: networkd-dispatcher (Ubuntu Hirsute)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Oh, that's good news. Let us know when it is uploaded and I give it a
spin.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884248
Title:
networkd-dispatcher gives corrupted information
To manage
This is fixed in 2.1 I'll have to upload it.
** Changed in: networkd-dispatcher (Ubuntu)
Status: Confirmed => In Progress
** Also affects: networkd-dispatcher (Ubuntu Hirsute)
Importance: High
Status: In Progress
** Also affects: networkd-dispatcher (Ubuntu Bionic)
** Tags added: fr-878
** Tags removed: rls-hh-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884248
Title:
networkd-dispatcher gives corrupted information
To manage notifications about
it is valid json bu thte keys and valu es l ook malforme d.
** Changed in: networkd-dispatcher (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884248
** Tags added: rls-hh-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884248
Title:
networkd-dispatcher gives corrupted information
To manage notifications about this bug go to:
Any hope for this bug? A look at the corrupted json suggests that
networkd-dispatcher is assembling it by parsing log entries (?!?!?).
Something about my environment must be generating log entries that fit
the filters it is using but are normally not present (or many others
would be complaining).
I'm a recent upgrader from bionic to focal thanks to a new System76
laptop that came with 20.04 pre-installed. I've been moving my
netplan/dnsmasq configuration over to the new laptop and ran into this
bug (I use a networkd-dispatcher script to pass DNS to dnsmasq via
openresolv). I added a
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: networkd-dispatcher (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884248
So does this silence mean people have tried to reproduce this but
couldn't or that they could and are working on it or that nobody has
tried?
I would have thought this kind of corruption is hinting at a possibility
of there being some possibility that this could be exploited and get a
bit more
Ok, it looks like the networkd crash & error message about enslaving a
bridge to a bridge was caused by the fact that the network file for one
of the bridge ports had a Match on MACAddress and came before the
bridge's own network file. Therefore, on restarting networkd matched the
port network
17 matches
Mail list logo
