Re: WLAN disabled by state file

2011-03-08 Thread Andrey Borzenkov
On Mon, Mar 7, 2011 at 8:02 PM, Ozan Çağlayan wrote: > On 07.03.2011 19:01, Dan Williams wrote: > >> That message can only come from a user applet property set request from >> D-Bus. > > Actually this came to my mind right after posting the e-mail. It is the > new KDE4 applet. Should I blame it fo

Re: WLAN disabled by state file

2011-03-07 Thread Dan Williams
On Mon, 2011-03-07 at 19:02 +0200, Ozan Çağlayan wrote: > On 07.03.2011 19:01, Dan Williams wrote: > > > That message can only come from a user applet property set request from > > D-Bus. > > Actually this came to my mind right after posting the e-mail. It is the > new KDE4 applet. Should I blame

Re: WLAN disabled by state file

2011-03-07 Thread Ozan Çağlayan
On 07.03.2011 19:01, Dan Williams wrote: > That message can only come from a user applet property set request from > D-Bus. Actually this came to my mind right after posting the e-mail. It is the new KDE4 applet. Should I blame it for this problem? Ozan Caglayan -- Pardus Linux http://www.pard

Re: WLAN disabled by state file

2011-03-07 Thread Dan Williams
On Sun, 2011-03-06 at 18:03 +0200, Ozan Çağlayan wrote: > On 05.03.2011 17:31, Dan Williams wrote: > > > Need a bit more debug here; the --log-level=debug logs would be useful > > for starters. > > > > Dan > > Ok, the logs are attached. (This is the new NM 0.8.3.997) Is this also with nm-applet

Re: WLAN disabled by state file

2011-03-06 Thread Ozan Çağlayan
On 05.03.2011 17:31, Dan Williams wrote: > Need a bit more debug here; the --log-level=debug logs would be useful > for starters. > > Dan Ok, the logs are attached. (This is the new NM 0.8.3.997) Thanks, -- Pardus Linux http://www.pardus.org.tr/eng After pressing the rfkill button on laptop:

Re: WLAN disabled by state file

2011-03-05 Thread Dan Williams
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

Re: WLAN disabled by state file

2011-03-05 Thread Ozan Çağlayan
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 r

Re: WLAN disabled by state file

2011-02-09 Thread Ozan Çağlayan
On 09.02.2011 18:40, Dan Williams wrote: In current NM 0.8.x git, if you uncheck "Enable Wireless" from the menu, NM writes that to the state file. That will then be in-force until you re-check "Enable Wireless", even across reboots. This takes precedence over rfkill because it was an explici

Re: WLAN disabled by state file

2011-02-09 Thread Dan Williams
On Thu, 2011-02-03 at 13:00 +0200, Ozan Çağlayan wrote: > Hi, > > I have bug reports about some inconsistencies caused by the state file and > rfkill > interactions like when the user kills the radio and then re-enables it, the > WLAN can't be enabled > unless the state file is edited manually a

Re: WLAN disabled by state file

2011-02-07 Thread José Queiroz
2011/2/7 Ozan Çağlayan > On 03.02.2011 13:00, Ozan Çağlayan wrote: > >> Hi, >> > > And there's also another bug that I can reproduce: > > 1. Connect using WiFi > 2. Soft block WiFi (result: sw_enabled=0, hw_enabled=1) > 3. state file is updated to WirelessEnabled=false > 4. Unblock wifi (result:

Re: WLAN disabled by state file

2011-02-07 Thread Ozan Çağlayan
On 03.02.2011 13:00, Ozan Çağlayan wrote: Hi, And there's also another bug that I can reproduce: 1. Connect using WiFi 2. Soft block WiFi (result: sw_enabled=0, hw_enabled=1) 3. state file is updated to WirelessEnabled=false 4. Unblock wifi (result: sw_enabled=1, hw_enabled=1) 5. state file is

WLAN disabled by state file

2011-02-03 Thread Ozan Çağlayan
Hi, I have bug reports about some inconsistencies caused by the state file and rfkill interactions like when the user kills the radio and then re-enables it, the WLAN can't be enabled unless the state file is edited manually as root, etc. I think that when the system is booted, NM should ignore