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 693172 - cli: report error on 'nmcli switch wifi on'
cli: report error on 'nmcli switch wifi on'
Status: RESOLVED OBSOLETE
Product: NetworkManager
Classification: Platform
Component: nmcli
git master
Other Linux
: Normal normal
: ---
Assigned To: Jiri Klimes
NetworkManager maintainer(s)
Depends on:
Blocks: tracker-nmcli
 
 
Reported: 2013-02-04 23:29 UTC by Pavel Simerda
Modified: 2020-11-12 14:26 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Pavel Simerda 2013-02-04 23:29:20 UTC 
Using the 'cli-enhance' branch, I'm using 'nmcli' to try to enable wireless when hard rfkill is active.

See:

fedora ~ # nmcli switch
REQUIRED: (null)
NETWORKING    WIFI-HW         WIFI       MOBILE-HW       MOBILE    
enabled       disabled        disabled   enabled         disabled  
fedora ~ # nmcli switch wifi on && echo ok
ok
fedora ~ # nmcli switch
REQUIRED: (null)
NETWORKING    WIFI-HW         WIFI       MOBILE-HW       MOBILE    
enabled       disabled        disabled   enabled         disabled  
fedora ~ # rfkill list
0: tpacpi_bluetooth_sw: Bluetooth
        Soft blocked: yes
        Hard blocked: yes
1: phy0: Wireless LAN
        Soft blocked: yes
        Hard blocked: yes

Expected behavior:

nmcli should write an error message to stderr and return non-zero status.

Actual behavior:

nmcli behaves as if the action was successful.
Comment 1 Dan Winship 2013-05-02 15:59:35 UTC 
NM bugzilla reorganization... sorry for the bug spam.
Comment 2 André Klapper 2020-11-12 14:26:31 UTC 
bugzilla.gnome.org is being shut down in favor of a GitLab instance. 
We are closing all old bug reports and feature requests in GNOME Bugzilla which have not seen updates for a long time.

If you still use NetworkManager and if you still see this bug / want this feature in a recent and supported version of NetworkManager, then please feel free to report it at https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/

Thank you for creating this report and we are sorry it could not be implemented (workforce and time is unfortunately limited).