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 665226 - Can't turn off wired connection from the network-indicator
Can't turn off wired connection from the network-indicator
Status: RESOLVED DUPLICATE of bug 665112
Product: gnome-shell
Classification: Core
Component: network-indicator
3.2.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2011-11-30 17:19 UTC by Volker Sobek (weld)
Modified: 2011-11-30 18:59 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Volker Sobek (weld) 2011-11-30 17:19:47 UTC
When I try to turn off the Wired connection from the indicator, nothing happens. nm-tool prints the same for eth0, whether the switch is on or off [1]. 

The switch for the wired connection in the control center's network panel DOES work and lets me turn on/off the connection.


GNOME Shell 3.2.1

[1]:

NetworkManager Tool

State: connected (global)

- Device: eth0  [Wired connection 1] -------------------------------------------
  Type:              Wired
  Driver:            e1000e
  State:             connected
  Default:           yes
  HW Address:        00:1A:6B:CD:68:CB

  Capabilities:
    Carrier Detect:  yes
    Speed:           100 Mb/s

  Wired Properties
    Carrier:         on

  IPv4 Settings:
    Address:         192.168.178.21
    Prefix:          24 (255.255.255.0)
    Gateway:         192.168.178.1

    DNS:             192.168.178.1
Comment 1 Volker Sobek (weld) 2011-11-30 17:23:32 UTC
Sorry, I selected the wrong shell version, it's GNOME Shell 3.2.1, like I wrote above and not 3.3.x.
Comment 2 Giovanni Campagna 2011-11-30 18:59:34 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 665112 ***