Network Manager Applet has duplicate entry changing IPv4 Method

Bug #1402094 reported by Christopher M. Peñalver on 2014-12-12
24
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Network Manager Applet
New
Medium
network-manager-applet (Ubuntu)
Medium
Unassigned

Bug Description

1) lsb_release -rd
Description: Ubuntu Vivid Vervet (development branch)
Release: 15.04

2) apt-cache policy network-manager-gnome
network-manager-gnome:
  Installed: 0.9.8.8-0ubuntu4.3
  Candidate: 0.9.8.8-0ubuntu4.3
  Version table:
 *** 0.9.8.8-0ubuntu4.3 0
        500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
        100 /var/lib/dpkg/status
     0.9.8.8-0ubuntu4 0
        500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

3) What is expected to happen in a new Vivid virtualbox guest is one clicks in vbox File > Preferences > Network > Host-only Networks > click plus icon to Add host-only network > IPv4 Address: 192.168.56.1 > IPv4 Network Mask: 255.255.255.0 > IPv6 Address: fe80:0000:0000:0000:0800:27ff:fe00:0000 > IPv6 Network Mask Length: 64 > tab DHCP Server > uncheck Enable Server > OK > highlight Vivid guest > Settings > Network > tab Adapter 1 > check Enable Network Adapter > Attached to: Host-only Adapter (leave defaults) > tab Adapter 2 > check Enable Network Adapter > Attached to: NAT (leave all other settings as default) > OK.

Start the Vivd guest and login > top right of screen secondary click Network Manager icon in the taskbar > Settings... > highlight WIred Connection 1 > Edit > tab IPv4 Settings > button Add > Address 192.168.56.3 > Netmask 255.255.255.0 > Gateway 192.168.56.1 > Save > click on the Network Manager icon in the taskbar and there should only be one entry for each interface.

4) What happens instead is there are two entries for Wired Connection 2, one that's connected, one that's disconnected, as per the attached screenshot:
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1402094/+attachment/4279934/+files/screenshot.png

If one were to reverse the order of the adapters in vbox, one would see two entries for Wired Connection 2 in Network Connections.

This is a regression as this was not reproducible in Precise 12.04.5.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: network-manager-gnome 0.9.8.8-0ubuntu8
ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
Uname: Linux 3.16.0-25-generic x86_64
ApportVersion: 2.14.7-0ubuntu10
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Dec 12 16:39:39 2014
ExecutablePath: /usr/bin/nm-connection-editor
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2014-12-10 (2 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141209)
IpRoute:
 default via 10.0.2.2 dev eth0 proto static
 10.0.2.0/24 dev eth0 proto kernel scope link src 10.0.2.15 metric 1
 192.168.56.0/24 dev eth1 proto kernel scope link src 192.168.56.3 metric 1
IwConfig:
 eth0 no wireless extensions.

 eth1 no wireless extensions.

 lo no wireless extensions.
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RfKill:

SourcePackage: network-manager-applet
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con:
 NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH
 Wired connection 2 335f383e-4a02-4acc-b424-00d174797339 802-3-ethernet 1418423923 Fri 12 Dec 2014 04:38:43 PM CST yes no /org/freedesktop/NetworkManager/Settings/2
 Wired connection 1 902a26d4-64b3-460d-97c8-0bfb9a57bf3a 802-3-ethernet 1418423923 Fri 12 Dec 2014 04:38:43 PM CST yes no /org/freedesktop/NetworkManager/Settings/0
nmcli-dev:
 DEVICE TYPE STATE DBUS-PATH
 eth1 802-3-ethernet connected /org/freedesktop/NetworkManager/Devices/1
 eth0 802-3-ethernet connected /org/freedesktop/NetworkManager/Devices/0
nmcli-nm:
 RUNNING VERSION STATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN
 running 0.9.8.8 connected enabled enabled enabled enabled disabled

description: updated
summary: - Network Connections has duplicate entry changing IPv4 Method
+ Network Manager Applet has duplicate entry changing IPv4 Method
Changed in network-manager-applet:
importance: Unknown → Medium
status: Unknown → New
tags: added: regression-release
description: updated
description: updated
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1402094

tags: added: iso-testing
Anthony (g-anthony) wrote :

Is there any way that I can make networkmanager to assign some unique names or device derrived name instead of `Auto Ethernet` so that we can avoid the names conflict?

After I've upgraded to Ubuntu Vivid which uses systemd(though I'm not sure if it's directly related or it's just a bug / regression of network-manager) both of my mobile broadband devices get the "Auth Ethernet" name and are unable to get connected simultaneously.

I can temporarry fix it using `nmcli con add type ethernet con-name my-office ifname ens3` but I would rather like to have network-manager handle this automatically (i.e. assign a random / unique conn name).

Use case:

I have two broadband USB devices and I need to connect to both of them. The issue is that NetworkManager displays them both as `Auto Ethernet` (duplicate in the network manager applet) and when I try to connect to the second network it errors out ``(32) Connection 'Auto Ethernet' is already active on enp0s20u``.
  When I try to "edit" the connections it displays only one `Auto Ethernet` connection.

 `/etc/NetworkManager/system-connections` also lists only one `Auto Ethernet`

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

Duplicates of this bug

Other bug subscribers

Remote bug watches

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