© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
The kde bug reported in this thread indicates that downgrading to previous bluez is the sole workaround known not to depend on gnome tools, but it also indicates that the workaround will not work with the forthcoming kde 4.2.
Is there any chance that by the end of January kde 4.2 fixes this in the right way by adding updated bluez support to solid?
Otherwise may ubuntu developers kindly propose that kde 4.2 is delayed until this bluetooth issue is solved?
Please do not give the (wrong) feeling that new stuff and eyecandy is continuously being added without first solving pending regressions and known bugs.