vpnc-scripts doesn't properly use resolvectl
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
vpnc-scripts (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
When using openconnect, it was updating /etc/resolv.conf directly instead of using resolvectl. I traced that down to the file /usr/share/
grep '^hosts' /etc/nsswitch.conf 2>/dev/null|grep resolve >/dev/null 2>&1 && command systemd-resolve --status >/dev/null 2>&1
Even though my system is using systemd-resolved, "resolve" is not in the hosts line of /etc/nssswitch and systemd-resolve is not in the path. I changed that line to:
grep '^hosts' /etc/nsswitch.conf 2>/dev/null|grep dns >/dev/null 2>&1 && command resolvectl status >/dev/null 2>&1
but I'm not sure that is correct. It works for me, though.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: vpnc-scripts 0.1~git20210402-1 [modified: usr/share/
ProcVersionSign
Uname: Linux 6.5.0-14-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckR
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 25 15:53:09 2024
InstallationDate: Installed on 2023-01-16 (374 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1)
PackageArchitec
ProcEnviron:
TERM=xterm-
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: vpnc-scripts
UpgradeStatus: No upgrade log present (probably fresh install)
There has been a lot of churn in the vpnc-scripts repository around this.
This problem would be fixed by 4a1bfb81be3dfa5 c886cdd589886f6 0b424c12e4 in https:/ /gitlab. com/openconnect /vpnc-scripts
There are later changes, too.