snappy-hwe-snaps

NetworkManager v265 set ethernet handler not correct

Bug #1766190 reported by Tony Kurz
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
snappy-hwe-snaps
New
Undecided
Unassigned

Bug Description

Attached journalctl. networkmanager v265 : 1.2.2-15

The previous version: 1.2.2-14 is working fine.

Also

00-nm-render.yaml exist.

snap get network-manager ethernet.enable is false

Autoconnect plug from network-manager:network-setup-control is not working.

I have to run manually or by a script:

snap set network-manager ethernet.enable=true

Revision history for this message
Tony Kurz (ubuntupicore) wrote :
Revision history for this message
Tony Kurz (ubuntupicore) wrote :

more information:

ubuntupicore@localhost:~$ nmcli d
DEVICE TYPE STATE CONNECTION
wlan0 wifi disconnected --
eth0 ethernet unmanaged --
lo loopback unmanaged --
ubuntupicore@localhost:~$ snap connect network-manager:
network-setup-control wpa
ubuntupicore@localhost:~$ snap connect network-manager:network-setup-control
ubuntupicore@localhost:~$ snap get network-manager ethernet.enable
false
ubuntupicore@localhost:~$ snap set network-manager ethernet.enable=true
ubuntupicore@localhost:~$ snap get network-manager ethernet.enable
true
ubuntupicore@localhost:~$ ls /etc/netplan/
00-default-nm-renderer.yaml 00-snapd-config.yaml
ubuntupicore@localhost:~$ nmcli d
DEVICE TYPE STATE CONNECTION
eth0 ethernet connected Wired connection 1
wlan0 wifi disconnected --
lo loopback unmanaged --

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.