desktop-packages team mailing list archive

Thread
Date

[Bug 996939] Re: After resume from suspend, NM should activate the most recently used (rather than some other "Connect automatically") connection

To: desktop-packages@xxxxxxxxxxxxxxxxxxx
From: "Oliver R." <996939@xxxxxxxxxxxxxxxxxx>
Date: Sat, 23 Jan 2016 12:01:53 -0000
Reply-to: Bug 996939 <996939@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

The "bug" (rather: feature request, wishlist) is still present in my
fully updated version von 12.04.

-- 
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/996939

Title:
  After resume from suspend, NM should activate the most recently used
  (rather than some other "Connect automatically") connection

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  I have two wired connections: one with a static IP (home) and one with
  DHCP (work).  The static connection is my default, the "automatically
  connect" box is checked.  After resume from suspend/hibernate
  NetworkManager always establishes the default connection, even if the
  DHCP connection was active before.  This means that, at work, I have
  to switch the connections after every suspend/resume.

  I would be desirable that NetworkManager re-establishes the last
  connection - even if this is different from the default one.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: network-manager 0.9.4.0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic-pae 3.2.14
  Uname: Linux 3.2.0-24-generic-pae i686
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: i386
  CRDA: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden
  Date: Wed May  9 08:46:49 2012
  InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
  IpRoute:
   default via 192.168.1.1 dev eth0  proto static 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.104  metric 1
  IwConfig:
   lo        no wireless extensions.
   
   eth0      no wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2012-04-30T18:00:42.019049
  nmcli-con:
   NAME                      UUID                                   TYPE              TIMESTAMP    TIMESTAMP-REAL                     AUTOCONNECT   READONLY   DBUS-PATH                                 
   DHCP                      f109de6e-4ef4-418b-ab9e-2ec100c48cf0   802-3-ethernet    1336545917   Mi 09 Mai 2012 08:45:17 CEST       no            no         /org/freedesktop/NetworkManager/Settings/1
   Feste IP                  b5138b0c-e3c1-432f-bd1b-df7cd4596a77   802-3-ethernet    1336546112   Mi 09 Mai 2012 08:48:32 CEST       yes           no         /org/freedesktop/NetworkManager/Settings/0
  nmcli-dev:
   DEVICE     TYPE              STATE         DBUS-PATH                                  
   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.4.0    connected       enabled       enabled         enabled    enabled         enabled

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