← Back to team overview

desktop-packages team mailing list archive

[Bug 921166] [NEW] nmcli always need restarting network-manager service for reconnect again

 

Public bug reported:

i have network-manager with version 0.9.2.0+git201112151936.6b31828-0ubuntu1 installed. 
nmcli was command-line tool for controlling NetworkManager included with network-manager package. i used this tool to connect to internet with my modem.

for first connect, with $nmcli con up id 'Some ID' , nothing wrong with this, and get some connection to the world, but if this connection get disconnected, nmcli con up always fails for bringing up the connection with message like this 
    Error: No suitable device found: no device found for connection 'Some ID'.

for some time, i found some solution for this problem, ie by always restarting network-manager service's
and then nmcli con up could bring up this connection.

I think this a serious bug for network-manager or nmcli tool.

Thanks

** Affects: network-manager (Ubuntu)
     Importance: Undecided
         Status: New

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

Title:
  nmcli always need restarting network-manager service for reconnect
  again

Status in “network-manager” package in Ubuntu:
  New

Bug description:
  i have network-manager with version 0.9.2.0+git201112151936.6b31828-0ubuntu1 installed. 
  nmcli was command-line tool for controlling NetworkManager included with network-manager package. i used this tool to connect to internet with my modem.

  for first connect, with $nmcli con up id 'Some ID' , nothing wrong with this, and get some connection to the world, but if this connection get disconnected, nmcli con up always fails for bringing up the connection with message like this 
      Error: No suitable device found: no device found for connection 'Some ID'.

  for some time, i found some solution for this problem, ie by always restarting network-manager service's
  and then nmcli con up could bring up this connection.

  I think this a serious bug for network-manager or nmcli tool.

  Thanks

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


Follow ups

References