[Bug 390743] Re: Wrong killswitch status from hal

2010-08-01 Thread Fabio Marconi
Thank you for taking the time to report this bug and helping to make Ubuntu better. Is this bug reproducible with the latest Lucid packages ? Tanks in advance. ** Changed in: ubuntu Status: New = Incomplete -- Wrong killswitch status from hal https://bugs.launchpad.net/bugs/390743 You

[Bug 390743] Re: Wrong killswitch status from hal

2010-08-01 Thread JoLa
Bug is not reproducible. -- Wrong killswitch status from hal https://bugs.launchpad.net/bugs/390743 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com

[Bug 390743] Re: Wrong killswitch status from hal

2010-08-01 Thread Fabio Marconi
Thanks for the reply In accord with reporter's reply I mark as Invalid. :)Fabio ** Changed in: ubuntu Status: Incomplete = Invalid -- Wrong killswitch status from hal https://bugs.launchpad.net/bugs/390743 You received this bug notification because you are a member of Ubuntu Bugs, which

[Bug 390743] Re: Wrong killswitch status from hal

2009-07-03 Thread Simos Xenitellis
Have a look at https://bugs.edge.launchpad.net/ubuntu/+source/hal/+bug/394663 I think that report describes the source of the problem, which is that the tool that says whether the killswitch is on or off, reports always that rfkill is on (no Wireless). The value we get from dbus apparently is