After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 685634 - Active connection stays permanently ACTIVATING
Active connection stays permanently ACTIVATING
Status: RESOLVED DUPLICATE of bug 685581
Product: NetworkManager
Classification: Platform
Component: general
git master
Other Linux
: Normal normal
: ---
Assigned To: NetworkManager maintainer(s)
NetworkManager maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2012-10-06 23:44 UTC by Giovanni Campagna
Modified: 2012-10-07 15:29 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Giovanni Campagna 2012-10-06 23:44:03 UTC 
Read it yourself:

gdbus introspect --system --dest org.freedesktop.NetworkManager --object-path /org/freedesktop/NetworkManager/ActiveConnection/1 --only-properties 
node /org/freedesktop/NetworkManager/ActiveConnection/1 {
  interface org.freedesktop.NetworkManager.Connection.Active {
    properties:
      readonly o Master = '/';
      readonly b Vpn = false;
      readonly b Default6 = false;
      readonly b Default = true;
      readonly u State = 1;
      readonly ao Devices = ['/org/freedesktop/NetworkManager/Devices/1'];
      readonly s Uuid = 'ec117e08-6e79-4588-8713-5e0231a235a0';
      readonly o SpecificObject = '/org/freedesktop/NetworkManager/AccessPoint/7';
      readonly o Connection = '/org/freedesktop/NetworkManager/Settings/3';
  };
};

But the connection is perfectly active, and

$ nmcli dev status
DEVICE     TYPE              STATE  
wlan0      802-11-wireless   connected
em1        802-3-ethernet    unavailable

$ nmcli nm status
RUNNING         STATE           WIFI-HARDWARE   WIFI       WWAN-HARDWARE   WWAN
running         connected       enabled         enabled    enabled         disabled

This may be the cause of bug 676285 in the UI.
It happened with NetworkManager-0.9.7.0-3.git20121004.fc18.x86_64. In case it matters, NM was just live updated, restarted and reconnected.
Comment 1 Dan Winship 2012-10-07 11:42:05 UTC 
Not the same as 676285. This was a new bug which is fixed in git master and in the latest f18 package (-4, built last night)

*** This bug has been marked as a duplicate of bug 685581 ***
Comment 2 Giovanni Campagna 2012-10-07 12:45:44 UTC 
I'm not sure it's the same as bug 685581: that one is about NMDevice::state-changed, while this is about NMActiveConnection::state, and happens even if I query the property directly (via gdbus) instead of watching it change.
Comment 3 Dan Winship 2012-10-07 15:29:36 UTC 
Yup, NMActiveConnection:state on the daemon side gets set from a signal handler for NMDevice::state-changed, so it fails when that signal gets lost. I see:

      readonly u State = 2;

with the new NM.