1. 18 Feb, 2013 4 commits
  2. 15 Feb, 2013 4 commits
  3. 14 Feb, 2013 8 commits
  4. 13 Feb, 2013 5 commits
  5. 12 Feb, 2013 9 commits
  6. 11 Feb, 2013 8 commits
    • Dan Williams's avatar
      settings: load keyfile plugin even if no plugins are given · e5f8b426
      Dan Williams authored
      If no config file was specified, and if no other plugins were given
      on the command-line, the keyfile plugin would not be loaded.  This
      meant no connections would be read, and no connections could be
      created either.
      
      Always load the keyfile plugin.
      e5f8b426
    • Dan Williams's avatar
      wifi: don't warn on unknown nl80211 ciphers · 6cba496a
      Dan Williams authored
      6cba496a
    • Dan Williams's avatar
      core: fix duplicating (not removing) active connections · aa5013cf
      Dan Williams authored
      This is a regression introduced by reworked active connections tracking:
      7258dd27 core: add the NM_ACTIVE_CONNECTION_STATE_DEACTIVATED state
      59420add core: track active connections directly in the manager
      
      Because nm-manager.c:active_connection_state_changed() postpones active
      connection removal to an idle handler (to be able to receive last property
      change notifications), we also need to ensure that NM_ACTIVE_CONNECTION_STATE_DEACTIVATED
      state is not changed again in the meantime in nm-activation-request.c:device_state_changed().
      After the NMActRequest was deactivated (which is a terminal state) it was still
      listening to state changes of its child NMDevice which could be starting a
      new activation request.  Thus the new activation's NMDevice state would cause
      the old activation request's state to change from DEACTIVATED.  To fix this
      stop listening to the child NMDevice when DEACTIVATED becuase there's no point
      to doing so anyway.
      
      Reproducer:
      Just activate already active connection by clicking it in nm-applet or
      run 'nmcli con up id <connnection name>' several times, and then check
      active connections with 'nmcli c s'.
      aa5013cf
    • Dan Williams's avatar
      Revert "core: fix duplicating (not removing) active connections" · 527cbf19
      Dan Williams authored
      This reverts commit df796527.
      
      We found the real problem.
      527cbf19
    • Dan Winship's avatar
      core: add NM_WIFI_DEVICE_CAP_ADHOC · fc700e92
      Dan Winship authored
      Some wireless devices don't support Ad-Hoc mode. Expose this fact in
      the wireless capabilities so that clients can disable the hot-spot
      option if neither CAP_ADHOC nor CAP_AP is available.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=692869
      fc700e92
    • Jiří Klimeš's avatar
      core: fix duplicating (not removing) active connections · df796527
      Jiří Klimeš authored
      This is a regression introduced by reworked active connections tracking:
      7258dd27 core: add the NM_ACTIVE_CONNECTION_STATE_DEACTIVATED state
      59420add core: track active connections directly in the manager
      
      Because nm-manager.c:active_connection_state_changed() postpones active
      connection removal to an idle handler (to be able to receive last property
      change notifications), we also need to ensure that NM_ACTIVE_CONNECTION_STATE_DEACTIVATED
      state is not changed again in the meantime in nm-activation-request.c:device_state_changed().
      
      Reproducer:
      Just activate already active connection by clicking it in nm-applet or
      run 'nmcli con up id <connnection name>' several times, and then check
      active connections with 'nmcli c s'.
      df796527
    • Jiří Klimeš's avatar
    • Jiří Klimeš's avatar
      d9c1fb17
  7. 09 Feb, 2013 2 commits