"Activation of network connection failed" popup shows incessantly

Bug #1767322 reported by Jacob Zimmermann
240
This bug affects 49 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Undecided
Unassigned
network-manager (Ubuntu)
Confirmed
Undecided
ANDRE LUIZ DE PINHO CAVALCANTE

Bug Description

All network connections work normally, however the popup "Activation of network connection failed" keeps showing.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: network-manager 1.10.6-2ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17
Uname: Linux 4.15.0-20-lowlatency x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 27 20:04:56 2018
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2018-04-03 (24 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180402)
IpRoute:
 default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600
 169.254.0.0/16 dev virbr1 scope link metric 1000 linkdown
 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.128 metric 600
 192.168.100.0/24 dev virbr1 proto kernel scope link src 192.168.100.1 linkdown
 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-nm:
 RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN
 running 1.10.6 connected started full enabled enabled enabled enabled enabled

Revision history for this message
Jacob Zimmermann (jacob) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in network-manager (Ubuntu):
status: New → Confirmed
Revision history for this message
Sebastien Bacher (seb128) wrote :

The log shows that DHCP requests timeout, are you sure the wifi you are trying to connect to is working? It looks like an infrastructure issue rather than an Ubuntu bug

Revision history for this message
Gede Suartana (gsuartana) wrote :

The WiFi is off, and I used the Ethernet connection "everything OK". It's still popup shows incessantly Activation of network connection failed.

Revision history for this message
Jacob Zimmermann (jacob) wrote :

My WiFi is working perfectly but I'm still getting these messages

Revision history for this message
mat (mat-garreau) wrote :

Just for your information, I have the same issue on my laptop (HP ZBook G3) since I upgrade my OS to 18.04.

Revision history for this message
Saurabh (codename0x) wrote :

Same issue on my Lenovo G50-80 running Ubuntu 18.04. Please let me know if there's any other information I can post that would help rectify this.

Revision history for this message
Filippo Callegaro (filippocalle) wrote :

Same issue on my Dell XPS 12 9Q33 after upgrading to Ubuntu 18.04.

Revision history for this message
João Biscoito (santanades) wrote :

Same issue here, my ethernet does not work!! Please fix ASAP!

Revision history for this message
Wm Wofford (wofford) wrote :

shiba satellite here same issue.... infact all my v18 do this I believe I seen same issue a previous releases years and years ago though...

Revision history for this message
Chris Burgess (chris-giantrobot) wrote :

I am seeing this issue as well.

I have two networks that are both configured to join a VPN, and when both networks (wifi and wired) are activated simultaneously, I see a message:

    Aug 21 15:45:58 example NetworkManager[1196]: <warn> [1534823158.7630] policy: secondary connection 'Example (12345678-1234-1234-1234-1234567890ab)' auto-activation failed: (6) Connection 'Example' is already active

So - the fix for me is to disable (manually, currently) the wifi when my laptop is docked; this seems to allow the VPN to connect on the (sole remaining) network connection.

Posting in the hope this might help others, and to follow along with this issue :)

Revision history for this message
BitBurners.com (lasse-penttinen) wrote :

I am also experiencing random yet frequent network error notifications of HP Elitebook G3.

00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection I219-V (rev 21)
 Subsystem: Hewlett-Packard Company Ethernet Connection I219-V
 Kernel driver in use: e1000e
 Kernel modules: e1000e
01:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a)
 Subsystem: Intel Corporation Dual Band Wireless-AC 8260
 Kernel driver in use: iwlwifi
 Kernel modules: iwlwifi

Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1767322

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Manfred Mager (frediiii) wrote :
Download full text (4.5 KiB)

I had the same problem and just found out that it was caused by a USB network interface that probably has been added when I plugged in a USB network device some time ago. The device has not been connected for months, yet apparently it's active in network manager, trying to get DHCP leases, which of course will fail.

Removing the USB connection profile from network manager solved the problem for me.

Sylog output example before removing connection profile:

Aug 31 07:59:43 p4t-nb-199 dhclient[31345]: DHCPDISCOVER on enp0s20f0u3c2 to 255.255.255.255 port 67 interval 5 (xid=0x5dc07171)
Aug 31 07:59:48 p4t-nb-199 dhclient[31345]: DHCPDISCOVER on enp0s20f0u3c2 to 255.255.255.255 port 67 interval 13 (xid=0x5dc07171)
Aug 31 08:00:01 p4t-nb-199 dhclient[31345]: DHCPDISCOVER on enp0s20f0u3c2 to 255.255.255.255 port 67 interval 16 (xid=0x5dc07171)
Aug 31 08:00:17 p4t-nb-199 dhclient[31345]: DHCPDISCOVER on enp0s20f0u3c2 to 255.255.255.255 port 67 interval 13 (xid=0x5dc07171)
Aug 31 08:00:24 p4t-nb-199 NetworkManager[1026]: <warn> [1535695224.9894] dhcp4 (enp0s20f0u3c2): request timed out
Aug 31 08:00:24 p4t-nb-199 NetworkManager[1026]: <info> [1535695224.9895] dhcp4 (enp0s20f0u3c2): state changed unknown -> timeout
Aug 31 08:00:25 p4t-nb-199 NetworkManager[1026]: <info> [1535695225.0064] dhcp4 (enp0s20f0u3c2): canceled DHCP transaction, DHCP client pid 31345
Aug 31 08:00:25 p4t-nb-199 NetworkManager[1026]: <info> [1535695225.0066] dhcp4 (enp0s20f0u3c2): state changed timeout -> done
Aug 31 08:00:25 p4t-nb-199 NetworkManager[1026]: <info> [1535695225.0083] device (enp0s20f0u3c2): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')
Aug 31 08:00:25 p4t-nb-199 NetworkManager[1026]: <warn> [1535695225.0122] device (enp0s20f0u3c2): Activation: failed for connection 'Wired connection 1'
Aug 31 08:00:25 p4t-nb-199 NetworkManager[1026]: <info> [1535695225.0160] device (enp0s20f0u3c2): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Aug 31 08:00:25 p4t-nb-199 avahi-daemon[1009]: Withdrawing address record for fe80::dc1a:366d:4591:9ef8 on enp0s20f0u3c2.
Aug 31 08:00:25 p4t-nb-199 avahi-daemon[1009]: Leaving mDNS multicast group on interface enp0s20f0u3c2.IPv6 with address fe80::dc1a:366d:4591:9ef8.
Aug 31 08:00:25 p4t-nb-199 systemd-timesyncd[793]: Network configuration changed, trying to establish connection.
Aug 31 08:00:25 p4t-nb-199 avahi-daemon[1009]: Interface enp0s20f0u3c2.IPv6 no longer relevant for mDNS.
Aug 31 08:00:25 p4t-nb-199 NetworkManager[1026]: <info> [1535695225.0415] policy: auto-activating connection 'Wired connection 1'
Aug 31 08:00:25 p4t-nb-199 NetworkManager[1026]: <info> [1535695225.0441] device (enp0s20f0u3c2): Activation: starting connection 'Wired connection 1' (469a98cb-89f1-384c-bae1-f72617a41bff)
Aug 31 08:00:25 p4t-nb-199 NetworkManager[1026]: <info> [1535695225.0446] device (enp0s20f0u3c2): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Aug 31 08:00:25 p4t-nb-199 NetworkManager[1026]: <info> [1535695225.0457] device (enp0s20f0u3c2): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
A...

Read more...

Revision history for this message
Fredrik Wredenberg (kimab-vl) wrote :

I think you're on to something Manfred. I removed my bluetooth connection and that solved the problem.

Revision history for this message
Akash Sharma (akasharma03) wrote :

I have the same issue. Other wifi networks connect immediately but one. When I first installed Ubuntu 18.04 it worked completely fine for a couple of days but now it doesn't. Please help.

Revision history for this message
Frank Bicknell (fbicknel) wrote : apport information
Download full text (3.9 KiB)

ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: sbicknel 1590 F.... pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2018-07-22 (40 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
IpRoute:
 default via 192.168.2.12 dev wlp3s0 proto dhcp metric 600
 169.254.0.0/16 dev wlp3s0 scope link metric 1000
 192.168.2.0/24 dev wlp3s0 proto kernel scope link src 192.168.2.203 metric 600
MachineType: ASUSTeK Computer Inc. K53SV
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
Package: network-manager 1.10.6-2ubuntu1
PackageArchitecture: amd64
ProcEnviron:
 TERM=screen
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB:
 0 inteldrmfb
 1 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=9d6809b8-6df1-4e23-8eaa-abb32b394780 ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-33-generic N/A
 linux-backports-modules-4.15.0-33-generic N/A
 linux-firmware 1.173.1
Tags: bionic
Uname: Linux 4.15.0-33-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: sudo syslog
WifiSyslog:

_MarkForUpload: True
dmi.bios.date: 11/11/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: K53SV.320
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: K53SV
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK53SV.320:bd11/11/2011:svnASUSTeKComputerInc.:pnK53SV:pvr1.0:rvnASUSTeKComputerInc.:rnK53SV:rvr1.0:cvnASUSTeKComputerInc.:ct9:cvr1.0:
dmi.product.family: K
dmi.product.name: K53SV
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.
nmcli-con:
 NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE
 ASUS a6db843d-8462-4491-a7de-a19d004e7cff wifi 1535804999 Sat 01 Sep 2018 08:29:59 AM EDT yes 0 no /org/freedesktop/NetworkManager/Settings/1 yes wlp3s0 activated /org/freedesktop/NetworkManager/ActiveConnection/254 --
 Wired connection 1 8b2109b1-944f-31da-9409-b8165e9059e4 ethernet 1535391957 Mon 27 Aug 2018 01:45:57 PM EDT yes 4294966297 no /org/freedesktop/NetworkManager/Settings/2 no -- -- -- --
nmcli-dev:
 DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID ...

Read more...

tags: added: apport-collected
Revision history for this message
Frank Bicknell (fbicknel) wrote : AlsaInfo.txt

apport information

Revision history for this message
Frank Bicknell (fbicknel) wrote : CRDA.txt

apport information

Revision history for this message
Frank Bicknell (fbicknel) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Frank Bicknell (fbicknel) wrote : Dependencies.txt

apport information

Revision history for this message
Frank Bicknell (fbicknel) wrote : IpAddr.txt

apport information

Revision history for this message
Frank Bicknell (fbicknel) wrote : IwConfig.txt

apport information

Revision history for this message
Frank Bicknell (fbicknel) wrote : Lspci.txt

apport information

Revision history for this message
Frank Bicknell (fbicknel) wrote : Lsusb.txt

apport information

Revision history for this message
Frank Bicknell (fbicknel) wrote : NetDevice.enp5s0.txt

apport information

Revision history for this message
Frank Bicknell (fbicknel) wrote : NetDevice.lo.txt

apport information

Revision history for this message
Frank Bicknell (fbicknel) wrote : NetDevice.wlp3s0.txt

apport information

Revision history for this message
Frank Bicknell (fbicknel) wrote : NetworkManager.conf.txt

apport information

Revision history for this message
Frank Bicknell (fbicknel) wrote : PciNetwork.txt

apport information

Revision history for this message
Frank Bicknell (fbicknel) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Frank Bicknell (fbicknel) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Frank Bicknell (fbicknel) wrote : ProcModules.txt

apport information

Revision history for this message
Frank Bicknell (fbicknel) wrote : PulseList.txt

apport information

Revision history for this message
Frank Bicknell (fbicknel) wrote : RfKill.txt

apport information

Revision history for this message
Frank Bicknell (fbicknel) wrote : UdevDb.txt

apport information

Revision history for this message
Frank Bicknell (fbicknel) wrote :

re: my apport information just uploaded: I am using wireless as my primary network connection. If I turn off the wired ethernet connection, the nagging message stops popping up.

Revision history for this message
ANDRE LUIZ DE PINHO CAVALCANTE (andreluizpinho) wrote :

My wireless connections works fine in Windows, but in Ubuntu it does't even connect and the message of error is as above: "activation of network connection failed". I am using the version 18.04.01.

Changed in network-manager (Ubuntu):
assignee: nobody → ANDRE LUIZ DE PINHO CAVALCANTE (andreluizpinho)
Anup Khanal (khanalanup)
Changed in network-manager (Ubuntu):
status: Confirmed → Incomplete
status: Incomplete → Confirmed
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Joseph (joewa6) wrote :

My network works fine. I am on a wired network connection. However, whenever I try to connect using VPN I get the "Activation of network connection failed" error message.

Brad Figg (brad-figg)
tags: added: cscc
Revision history for this message
Ghost (jpgottech) wrote :

Oddly i have had the same issue and I today i was getting annoyed so i went to wifi and switched from my 5G to 2.4 and it has been solid since. I will update if anything changes. Can finally not have to run a constant ping to keep it alive. on 5G when running a constant ping that would prevent the issue from happening

Revision history for this message
Pushpendra Kumar (pushpi-gangwar) wrote :
Download full text (3.5 KiB)

I am facing same issue while re-connecting to my TunnelBear VPN. TunnelBear VPN uses open-vpn service. I have configured VPN as per instructions by TunnelBear. And it works fine when connect first time, but after that when choose "Turn Off" from Netowrok-Manager then choose "Connect" again, then I see this same error. See snapshot from syslog:
Dec 17 20:45:25 KUMAR-PC NetworkManager[902]: <info> [1576611925.5171] vpn-connection[0x5568a73e41c0,d79431f3-7dda-41cb-b74b-e7b71ed48592,"TunnelBear India",0]: VPN plugin: state changed: starting (3)
Dec 17 20:45:25 KUMAR-PC NetworkManager[902]: <info> [1576611925.5172] vpn-connection[0x5568a73e41c0,d79431f3-7dda-41cb-b74b-e7b71ed48592,"TunnelBear India",0]: VPN connection: (ConnectInteractive) reply received
Dec 17 20:45:25 KUMAR-PC nm-openvpn[6237]: WARNING: --keysize is DEPRECATED and will be removed in OpenVPN 2.6
Dec 17 20:45:25 KUMAR-PC nm-openvpn[6237]: OpenVPN 2.4.4 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on May 14 2019
Dec 17 20:45:25 KUMAR-PC nm-openvpn[6237]: library versions: OpenSSL 1.1.1 11 Sep 2018, LZO 2.08
Dec 17 20:45:25 KUMAR-PC nm-openvpn[6237]: WARNING: --ns-cert-type is DEPRECATED. Use --remote-cert-tls instead.
Dec 17 20:45:25 KUMAR-PC nm-openvpn[6237]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Dec 17 20:45:25 KUMAR-PC nm-openvpn[6237]: TCP/UDP: Preserving recently used remote address: [AF_INET]103.228.153.233:443
Dec 17 20:45:25 KUMAR-PC nm-openvpn[6237]: UDP link local: (not bound)
Dec 17 20:45:25 KUMAR-PC nm-openvpn[6237]: UDP link remote: [AF_INET]103.228.153.233:443
Dec 17 20:45:25 KUMAR-PC nm-openvpn[6237]: NOTE: chroot will be delayed because of --client, --pull, or --up-delay
Dec 17 20:45:25 KUMAR-PC nm-openvpn[6237]: NOTE: UID/GID downgrade will be delayed because of --client, --pull, or --up-delay
Dec 17 20:45:27 KUMAR-PC nm-openvpn[6237]: [9563/server] Peer Connection Initiated with [AF_INET]103.228.153.233:443
Dec 17 20:45:28 KUMAR-PC nm-openvpn[6237]: Option 'explicit-exit-notify' in [PUSH-OPTIONS]:3 is ignored by previous <connection> blocks
Dec 17 20:45:28 KUMAR-PC nm-openvpn[6237]: Note: option tun-ipv6 is ignored because modern operating systems do not need special IPv6 tun handling anymore.
Dec 17 20:45:28 KUMAR-PC nm-openvpn[6237]: ERROR: Cannot ioctl TUNSETIFF tun0: Device or resource busy (errno=16)
Dec 17 20:45:28 KUMAR-PC nm-openvpn[6237]: Exiting due to fatal error
Dec 17 20:45:28 KUMAR-PC NetworkManager[902]: <warn> [1576611928.9900] vpn-connection[0x5568a73e41c0,d79431f3-7dda-41cb-b74b-e7b71ed48592,"TunnelBear India",0]: VPN plugin: failed: connect-failed (1)
Dec 17 20:45:28 KUMAR-PC NetworkManager[902]: <warn> [1576611928.9901] vpn-connection[0x5568a73e41c0,d79431f3-7dda-41cb-b74b-e7b71ed48592,"TunnelBear India",0]: VPN plugin: failed: connect-failed (1)
Dec 17 20:45:28 KUMAR-PC NetworkManager[902]: <info> [1576611928.9902] vpn-connection[0x5568a73e41c0,d79431f3-7dda-41cb-b74b-e7b71ed48592,"TunnelBear India",0]: VPN plugin: state changed: stopping (5)
Dec 17 20:45:28 KUMAR-PC NetworkManager[902]: <info> [1576611928.9903] vpn-connection[...

Read more...

To post a comment you must log in.