This bug was fixed in the package ifupdown - 0.8.36+nmu1ubuntu3.1
---
ifupdown (0.8.36+nmu1ubuntu3.1) jammy; urgency=medium
[ Uwe Kleine-König ]
* Fix if-up.d/resolved hook to properly work with nameservers and search
domains (LP: #1981103)
[ Heinrich Schuchardt ]
*
Validated according to test case from description. No error messages
shown, and networking has been correctly configured.
root@halves-lp1907878-j:~# dpkg -l | grep ifupdown
ii ifupdown 0.8.36+nmu1ubuntu3.1
amd64high level tools to configure
Hello Jacopo, or anyone else affected,
Accepted ifupdown into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/ifupdown/0.8.36+nmu1ubuntu3.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
@jasimioni I've dropped some bits of your diff that aren't necessary for
SRU (the typo fix), and sponsored your changes with mine from bug
1981103. Thank you for the help on fixing this!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
That other bug report says:
> I fixed it by removing the quotes around $DNS and $DOMAINS on line 47
and 51.
I found that in my version of the relevant file (which is - yes? -
/etc/network/if-up.d/resolved) the lines at issue were lines 48 and 52.
(I use Linux Mint 21.1, which is based upon
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1910273
This one seems to have the full patch repair in the bug description.
None of the other bugs I've found relating to this have the full
solution.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
ifupdown is in universe these days, so I'll unsubscribe foundations.
** Tags removed: foundations-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1907878
** Tags added: foundations-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1907878
Title:
wrong var declaration in if-up.d/resolved (nm-dispatcher[54417]:
While we're about it, the use of a bash variable named "DNS" for both
the actual server names and the name of the variable in which we're
going to store the server names is confusing.
** Patch added: "Sum of patches I've seen so far plus name change"
If someone's fixing the syntax errors, note there's also
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1981103 which
(in the initial comment) mentions another problem and its fix.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Also affects: ifupdown (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: ifupdown (Ubuntu Jammy)
Status: New => Triaged
** Changed in: ifupdown (Ubuntu Jammy)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of
I am also affected by this bug, un Ubuntu 22.04. Can somebody at least release
a script that fixes it?
Porting it to Jammy would be great!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
Hello Heinrich,
yes, very gladly.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1907878
Title:
wrong var declaration in if-up.d/resolved (nm-dispatcher[54417]:
The fix was make for Kinetic Kudu (0.8.36+nmu1ubuntu4). It would take an
SRU to port the fix to Jammy.
The stable release upgrade process is described here:
https://wiki.ubuntu.com/StableReleaseUpdates
Do you want to give it a try?
Best regards
Heinrich
--
You received this bug notification
Hi, as of today the fix is not available via apt at Ubuntu jammy x64.
Am I doing something wrong?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1907878
Title:
wrong var
as ~larsoner mentioned, those scripts contain some `return` but not in
functions, so they may fail in some cases; you should change all
`return` to `exit 0`
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
This bug was fixed in the package ifupdown - 0.8.36+nmu1ubuntu4
---
ifupdown (0.8.36+nmu1ubuntu4) kinetic; urgency=medium
* Remove invalid lines from resolved integration scripts (LP:
#1907878)
-- Heinrich Schuchardt Sun, 15 May
2022 15:35:51 +0200
** Changed in: ifupdown
** Changed in: ifupdown (Ubuntu)
Status: Confirmed => Fix Committed
** Changed in: ifupdown (Ubuntu)
Assignee: (unassigned) => Heinrich Schuchardt (xypron)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown
** Patch added: "ifupdown-0.8.36+nmu1ubuntu4.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1907878/+attachment/5589837/+files/ifupdown-0.8.36+nmu1ubuntu4.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
FWIW this is still a problem as of Ubuntu 22.04. I'm aware that using
/etc/network is deprecated in favor of netplan, I guess that's why the
script can stay in a broken state for so long. I'll be looking at
porting my configuration to that.
--
You received this bug notification because you are a
I just commended out the line "mystatedir statedir ifindex interface" on
both files /etc/network/if-up.d/resolved and /etc/network/if-
down.d/resolved
works without issues.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
For what it's worth, I commented out the `mystatedir statedir ifindex
interface` line, and changed the three `return` lines to be `exit 0` and
now I no longer get the angry red FAILED line during boot, `systemctl
status networking.service` looks okay, and my internet continues to
function just
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ifupdown (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
I gotta say, removing the line causes DNS resolution to fail on my
machine... perhaps this integration is not really working.
In case it matters, I have openresolv installed and set 'rc-
manager=resolvconf' in NetworkManager's config. (My use case is picking
up DNS settings from WireGuard.)
--
The same applies for if-down.d/resolved
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1907878
Title:
wrong var declaration in if-up.d/resolved (nm-dispatcher[54417]:
25 matches
Mail list logo
