[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 172267] KDE bluetooth tray applet doesn't appear
From:       Giovanni Masucci <grifis87 () virgilio ! it>
Date:       2009-01-15 4:39:16
Message-ID: 20090115043916.2BFBD146BC () immanuel ! kde ! org
[Download RAW message or body]

http://bugs.kde.org/show_bug.cgi?id=172267


Giovanni Masucci grifis87 virgilio it changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |grifis87@virgilio.it




--- Comment #13 from Giovanni Masucci <grifis87 virgilio it>  2009-01-15 05:39:13 ---
(In reply to comment #8)
> To get kbluetooth4 work with bluez4 the solid-bluetooth api needs to be ported
> to support bluez4. I've already ported a lot of basic stuff, like the BT
> manager, adapter, device and input class. But thats all very experimental and
> nearly untested. The ported manager and the adapter class, seems to work, they
> are already used within the latest kbluetooth4 code. To get the input stuff
> also work, the security classes must be ported/implemented. And last but not
> least kbluetooth4 must be adapted to use the ported solid-bluetooth methods.
> Sadly i can not work fulltime on kdebluetooth stuff, so any available help to
> get solid-bluetooth and kbluetooth4 ported to bluez4 is very welcome.
> kbluetooth4 can be found in trunk/playground/network/kbluetooth4/
> For those who just want to use bluetooth under KDE: 1. downgrade your bluez
> packages and install the latest available bluez-libs-3.x and bluez-utils-3.x
> (should be 3.36) 2. use kbluetooth4 under KDE4 or kbluetooth under KDE3
> 

Tom I see you did some changes to the bluez backend in trunk on 14/01/2009 to
adapt it to bluez 4.x libs...are these commits necessary for the backend to
work with bluez4.x? In this case can you backport these changes and the ones
that will come to kde 4.2 branch so that when kbluetooth4 0.3 gets released kde
4.2 will be ready for it? I don't know if this breaks some rules (bluetooth
cannot considered a new feature after all) but right now it doesn't work
anymore even with bluez 3.x so what do we have to loose? :)
In case this is not possible (but I hope it is :) ), I think it would be better
to revert commits to the bluez3.x backend in 4.2 branch, so that 4.2 users can
at least stick with bluez 3.x libs from external repos or built from sources
and keep working with kbluetooth4 0.2 like in kde 4.1...


-- 
Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]