<br><br><div class="gmail_quote">2010/1/5 Fabian Greffrath <span dir="ltr"><<a href="mailto:fabian@greffrath.com">fabian@greffrath.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Update: I tried at home with all different combinations of bluez<br>
packages (the current ones from Debian unstable and the ones from the<br>
Debian backports) and gnome-bluetooth (also the current ones from Debian<br>
unstable and the current ones from Ubuntu) - both with /dev/rfkill<br>
permissions manually set to 777 and left untouched - and *nothing*<br>
works.<font color="#888888"><br></font></blockquote><div><br></div><div><br></div><div>I don't think this issue is bluez-related, since it appeared for the very first time when we upgraded to gnome-bluetooth's 2.28.x series.</div>
<div><br></div><div>I gave a look at gnome-bluetooth's git logs and I found out some interesting pieces of code you might want to have a look at:</div><div><br></div><div><a href="http://git.gnome.org/browse/gnome-bluetooth/commit/?id=822c0ba3d02183cbac571dcc01f1b234d355c851">http://git.gnome.org/browse/gnome-bluetooth/commit/?id=822c0ba3d02183cbac571dcc01f1b234d355c851</a></div>
<div>and</div><div><a href="http://git.gnome.org/browse/gnome-bluetooth/commit/?id=3d2fb9c86dabc35193228948bcb0e6813412f9d5">http://git.gnome.org/browse/gnome-bluetooth/commit/?id=3d2fb9c86dabc35193228948bcb0e6813412f9d5</a></div>
<div><br></div><div>this means that every g-bluetooth's release *after* the 2.27.9 one will have this issue, so downgrading to a release which is before that one would fix this issue.</div><div><br></div><div>Did you try the Ubuntu package with bad results as well? they added the udev rule that should fix this rfkill issue, so it looks to me a bit strange that nothing works even with it.</div>
<div> </div></div><br>