> Alright, but the bug report claims this issue has been fixed in Linux
> 2.6.29~rc3 and I am using 2.6.32-3. It doesn't work with 2.6.30-8 from
> testing either, but this kernel is out of question anyway,
> because /dev/rfkill has just been added in 2.6.31.
Update: I just tried with the linux-ima
Am Mittwoch, den 06.01.2010, 12:41 +0100 schrieb Andrea Veri:
> gonna try to build a copy for you somewhen :)
This would be highly appreciated! ;)
> looks to me like a kernel issue with the new btusb kernel module, I
> found out a bug report in Launchpad as well:
> https://bugs.launchpad.net/ubu
2010/1/6 Fabian Greffrath
> Am Mittwoch, den 06.01.2010, 00:20 +0100 schrieb Andrea Veri:
> > 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.
>
> I would love to try with a
Am Mittwoch, den 06.01.2010, 00:20 +0100 schrieb Andrea Veri:
> 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.
I would love to try with a 2.27.x Debian package, but couldn't fin
2010/1/5 Fabian Greffrath
> Update: I tried at home with all different combinations of bluez
> packages (the current ones from Debian unstable and the ones from the
> Debian backports) and gnome-bluetooth (also the current ones from Debian
> unstable and the current ones from Ubuntu) - both with
Update: I tried at home with all different combinations of bluez
packages (the current ones from Debian unstable and the ones from the
Debian backports) and gnome-bluetooth (also the current ones from Debian
unstable and the current ones from Ubuntu) - both with /dev/rfkill
permissions manually set
Am Samstag, den 19.12.2009, 00:43 +0100 schrieb Andrea Veri:
> 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.
Update: Today
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
I have an update on this bug.
Yesterday I tried to manually grant write access to the rfkill device
and activate Bluetooth via gnome-bluetooth:
$ sudo chmod 0777 /dev/rfkill
$ bluetooth-properties
** Message: adding killswitch idx 0 state 1
** Message: killswitch 0 is 1
** Message: killswitche
severity 552185 serious
thanks
Dear all,
since the last dist-upgrade the situation has worsened for me. I am
not even able to enable bluetooth via gnome-bluetooth anymore. To be
honest, I am not sure if maybe the bluez upgrade (4.42 -> 4.57) has
caused this issue, but since bluetooth doesn't
10 matches
Mail list logo
