← Back to team overview

desktop-packages team mailing list archive

[Bug 1434986] Re: Not working network connection after boot

 

Any news?

This is very annoying and clearly a regression. I understand this might
be annoying to fix, but as asked, @jhe created the bug in the Gnome
Bugtracker and there is zero activity on this bug. Only on user on CC
and no comment. How can we raise awareness if you think this is an
upstream bug?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1434986

Title:
  Not working network connection after boot

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Directly after boot the network connections are not working. I am
  connected and have an IP address, but I cannot establish a connection
  with any Internet server.

  I have the impression it is related to thee DNS lookup, which waits
  forever for a result.

  Cycling the connection (disconnect->reconnect) seems to fix the
  problem for some time.

  I am reporting this against network-manager, but I am not sure if it is directly in network manager or if it is systemd related.
  With 14.10 everything worked perfectly.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu11
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Mar 22 12:38:26 2015
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-01-30 (50 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  IpRoute:
   default via 192.168.1.1 dev eth0  proto static  metric 1024 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.26 
   192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.29
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (3 days ago)
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2015-02-16T00:14:50.662693
  nmcli-dev:
   DEVICE  TYPE      STATE      DBUS-PATH                                  CONNECTION                 CON-UUID                              CON-PATH                                           
   eth0    ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  Kabelnetzwerkverbindung 1  4a581685-6002-4401-a993-49aa649667eb  /org/freedesktop/NetworkManager/ActiveConnection/4 
   wlan0   wifi      connected  /org/freedesktop/NetworkManager/Devices/1  4A616E7320574C414E         f45aa3a7-fb44-41b7-a02a-ea9720d79414  /org/freedesktop/NetworkManager/ActiveConnection/3 
   lo      loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/0  --                         --                                    --
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1434986/+subscriptions


References