On Wed, 09 Dec 2009, Fabian Greffrath wrote: > Looks like it's a regression in bluez and not gnome-bluetooth's > fault. What do you think?
Well, the real problem here is that bluez lacks its own rfkill, so users are stuck when trying to enable / disable their bluetooth interfaces. While we could patch gnome-bluetooth to provide this kind of access, I am still trying to find out what's the best way to workaround this since the Ubuntu way has been rejected upstream. (I guess you know that giving rfkill access by default to normal users is not the best to do at the moment) Looking at the informations you just provide, the issue seems to be in bluez itself, I think that you should forward the results of your tests directly upstream so we can start having an idea of what's going on. Upstream's Mailing Lists details can be found at this page: http://www.bluez.org/development/lists/ please report back here if you have any update, so let's keep this bug as the main thread for this discussion. Thanks in advance, Andrea
signature.asc
Description: Digital signature
