This is taken care of in Intrepid now. We have 1.8.
** Changed in: bluez-gnome (Ubuntu)
Status: New = Fix Released
--
[needs-packaging] bluez-gnome-1.4
https://bugs.launchpad.net/bugs/273865
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Intrepid targets bluez 3.x and so bluez-gnome 0.2x;
bluez-gnome 1.x will be targeted for new ubuntu release.
--
[needs-packaging] bluez-gnome-1.4
https://bugs.launchpad.net/bugs/273865
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Any chance that could be re-considered? At least I have this bug reported
upstream that the developers claim is fixed on 1.x
http://bugzilla.gnome.org/show_bug.cgi?id=531424
I don't think this one really entitles much risk given that is already accepted
by kernel. I'd probably be wrong so
BlueZ 4.x has too much changes and now we're are in Feature Freeze, so
it is a no-no for Intrepid.
I'm closing the bug as INVALID for now.
Regards
--
[needs-packaging] bluez-gnome-1.4
https://bugs.launchpad.net/bugs/273865
You received this bug notification because you are a member of Ubuntu
