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 624479 - NM activates previously disabled wifi option on suspend resume
NM activates previously disabled wifi option on suspend resume
Status: RESOLVED FIXED
Product: NetworkManager
Classification: Platform
Component: general
0.8.x
Other Linux
: Normal minor
: ---
Assigned To: Dan Williams
Dan Williams
: 634416 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2010-07-15 18:15 UTC by donpiero
Modified: 2016-03-11 17:42 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description donpiero 2010-07-15 18:15:28 UTC
Right click on the panel applet and uncheck the wifi option. (I want to standby wifi capability when connecting through eth). Suspend then resume your pc. Wifi option is now checked and your computer is eventually connected to your home wifi LAN if NM was set to automatically connect.

I'm using Ubuntu 10.04 AMD64 on an ASUS A7K.

Thank you.
Comment 1 Jiri Klimes 2010-07-20 13:45:21 UTC
There were some changes regarding the issue some time ago.

What version of NM do you use?
Could you paste /var/log/daemon.log file?
Comment 2 Dan Williams 2010-09-01 22:09:19 UTC
Fixed; the issue was that the "Enable Wireless" state was nominally tied to rfkill state, which would override the state file.  Thus on reboot since rfkill was not blocking wifi, even if the state file said "off" NM would re-enable wifi since rfkill said wifi was on.  With the following commit, the user preference stays enforced regardless of the rfkill state.

e86ef05d84749c5a15d7bcf30f78056ca205489c (master)
935db4c3064abeb270595e7d2bfa6398c1b196bb (0.8.x)
Comment 3 donpiero 2010-09-02 09:16:58 UTC
Great! Thank you
Comment 4 Dan Williams 2010-11-10 20:27:58 UTC
*** Bug 634416 has been marked as a duplicate of this bug. ***