Re: WLAN disabled by state file

[Dan Williams <dcbw redhat com>]

On Sat, 2011-03-05 at 15:07 +0200, Ozan Çağlayan wrote:
> On 09.02.2011 19:50, Ozan Çağlayan wrote:
> 
> > I think there are multiple issues in here. The one that I've mentioned
> > in the original thread and you've commented about may be triggered by
> > the bug that I've replied.
> > 
> > So with NM 0.8.2 on my Toshiba Portege R700 (iwlagn, exposing only a
> > soft rfkill which is correctly turning on/off on keypress), when I
> > sw-kill the radio, this is correctly detected by NM. The "Enable
> > Wireless" gets unchecked and WirelessEnabled=false is written to the
> > state file.

If WirelessEnabled=false gets written as a result of the rfkill, that's
wrong and is a bug.  Can you post some logs from this happening?  Better
yet, stop NM, run it with "--no-daemon --log-level=debug" and lets get
some verbose output here if we can.

Basically, WirelessEnabled should be the *user* preference, and should
be independent of whatever happens with rfkill.  But having either or
both of rfkill or WirelessEnabled off causes wireless to be off.

> > But when I unblock, NM detects this to some point (looking at the
> > debugged outputs and the code) but doesn't update the state file and
> > doesn't enable the wireless networking. So one should explicitly check
> > the "enable wireless" every time after unblocking the rfkill.
> > 
> > I think this should be fixed. I'd like to debug more but I'm really
> > getting lost in the glib/gobject mechanisms and NM code which contains a
> > lot of abstraction/callback stuff really hard to follow :(
> > 
> > 
> 
> Ping? Any idea before 0.8.4 gets released?

Need a bit more debug here; the --log-level=debug logs would be useful
for starters.

Dan