failed to add/activate wifi connection after netplan intalled_resolved

[Rolf Bruge]

message recipient disconnected from message bus without replying

lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu Mantic Minotaur (development branch)
Release: 23.10
Codename: mantic

hi libasyncns0:amd64 0.8-6build3 amd64 Asynchronous name service query library
hi libasyncns0:i386 0.8-6build3 i386 Asynchronous name service query library

Expected wifi connection as anticipated with 0.8-6build2.

Wifi connection failure notice when selecting network connection after update to 0.8-6build3.

Restore from backup with system upgrade excluding above problem packages does not produce wifi connection problem.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: libasyncns0 0.8-6build2
Uname: Linux 6.5.0-rc1 x86_64
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: MATE
Date: Fri Aug 11 16:39:25 2023
InstallationDate: Installed on 2016-08-04 (2563 days ago)
InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Alpha amd64 (20160727.1)
SourcePackage: libasyncns
UpgradeStatus: No upgrade log present (probably fresh install)

[Rolf Bruge (rolfbruge)]

problem packages are version:

libasyncns0:amd64 0.8-6build3 amd64
libasyncns0:i386 0.8-6build3 i386

not libasyncns0 0.8-6build2

[Rolf Bruge (rolfbruge)]

Issue was not resolved by switching to iwd from wpasupplicant.

Necessary to downgrade packages. See link below.

failed to add/activate connection
https://ubuntuforums.org/showthread.php?t=2490136&p=14155360#post14155360

[Rolf Bruge (rolfbruge)]

Issue persists with failure to migrate connections to netplan during installation. All connections fail to migrate and display terminal message referencing message recipient was disconnected from message bus without replying.

Issue persists as of September 10, 2023 with the following packages:

ii netbase 6.4 all Basic TCP/IP networking system
ii netplan-generator 0.107-4 amd64 YAML network configuration abstraction systemd-generator
ii netplan.io 0.107-4 amd64 YAML network configuration abstraction for various backends
ii network-manager 1.44.0-1ubuntu2 amd64 network management framework (daemon and userspace tools)
hi network-manager-gnome 1.30.0-2ubuntu1 amd64 network management framework (GNOME frontend)
hi network-manager-pptp 1.2.12-1 amd64 network management framework (PPTP plugin core)
hi networkd-dispatcher 2.2.3-1 all Dispatcher service for systemd-networkd connection status changes
ii openvpn 2.6.5-0ubuntu1 amd64 virtual private network daemon
ii python-netifaces 0.10.4-1ubuntu6 amd64 portable network interface information - Python 2.x
ii python3-netifaces:amd64 0.11.0-2build1 amd64 portable network interface information - Python 3.x
ii python3-netplan 0.107-4 amd64 YAML network configuration abstraction Python bindings
ii dirmngr 2.2.40-1.1ubuntu1 amd64 GNU privacy guard - network certificate management service
ii glib-networking:amd64 2.76.1-2 amd64 network-related giomodules for GLib
ii glib-networking:i386 2.76.1-2 i386 network-related giomodules for GLib
ii glib-networking-common 2.76.1-2 all network-related giomodules for GLib - data files
ii glib-networking-services 2.76.1-2 amd64 network-related giomodules for GLib - D-Bus services

[Rolf Bruge (rolfbruge)]

This bug persists as described in comment dated 2023-09-10.

Issue persists with failure to migrate connections to netplan during installation. All connections fail to migrate and display terminal message referencing message recipient was disconnected from message bus without replying.

Apparent failure to write to and utilize /etc/netplan when making a new connection.

It is remarkable that after all this time apparently nothing has been done regarding this bug.

[Rolf Bruge (rolfbruge)]

Interestingly enough, the following information was recenly encountered regarding using netplan:

Change your /etc/netplan/01-netcfg.yaml to the following code (and only this)... using sudo -H gedit /etc/netplan/01-netcfg.yaml...

network:
  version: 2
  renderer: NetworkManager

Then, in terminal...

sudo netplan generate # generate config files

sudo netplan apply # apply configuration

note this message appeared but apparently did not apply to desktop configuration:
Cannot call Open vSwitch: ovsdb-server.service is not running.

reboot # reboot the computer

Then use the standard Network Manager GUI to establish a wired/wireless connection.

Note that sudo netplan generate would not execute if .yaml files in /etc/netplan contained a reference to 'random' generated MAC.

Note that sudo netplan would not execute if file permissions in /etc/netplan were too lenieent.

used chown to configure root:root and chmod at 600

It would appear that a routine apt upgrade from network-manager to network-manager/netplan is not making necessary changes/creating needed file structure.

This appears to be a bug, because only manual intervention appears to have enabled netplan to work without error messages and connection failures.

This should be addressed.