Version: (using KDE 4.1.2) OS: Linux Installed from: Fedora RPMs (this might be related to Bug 168536, but I am not sure, therefore I file this new bug) I am using the latest Rawhide Fedora packages of KDE (kdelibs-4.1.2-2.fc10.i386), and have kdebluetooth-0.2-3.fc10.i386 installed. kernel-2.6.27-0.391.rc8.git7.fc10.i686, dbus-1.2.3-2.fc10.i386, dbus-qt-0.70-4.fc9.i386. When i start "kbluetooth4", I expected to get a system tray applet of some sort, but nothing appears, nothing is printed in the console. If I start "kbluetooth4-devicemanager" the following is printed in the console: process 3338: arguments to dbus_message_new_method_call() were incorrect, assertion "path != NULL" failed in file dbus-message.c line 1070. This is normally a bug in some application using the D-Bus library. D-Bus not built with -rdynamic so unable to print a backtrace KCrash: Application 'kbluetooth4-devicemanager' crashing... sock_file=/home/gronslet/.kde/socket-x1/kdeinit4__0 I have also installed the debug-info packages, providing the following backtrace: Application: KBluetooth4 - The KDE4 Bluetooth Framework (kbluetooth4-devicemanager), signal SIGABRT [Thread debugging using libthread_db enabled] [New Thread 0xb7f79770 (LWP 3338)] [KCrash handler] #6 0x00110416 in __kernel_vsyscall () #7 0x0072b740 in raise (sig=<value optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #8 0x0072d108 in abort () at abort.c:88 #9 0x00b919b5 in ?? () from /lib/libdbus-1.so.3 #10 0x00b8d3c9 in ?? () from /lib/libdbus-1.so.3 #11 0x00b80f1e in dbus_message_new_method_call () from /lib/libdbus-1.so.3 #12 0x00370874 in q_dbus_message_new_method_call () at ./qdbus_symbols_p.h:234 #13 QDBusMessagePrivate::toDBusMessage (message=<value optimized out>) at qdbusmessage.cpp:107 #14 0x0036c6fb in QDBusConnectionPrivate::sendWithReply ( this=<value optimized out>, message=<value optimized out>, sendMode=<value optimized out>, timeout=<value optimized out>) at qdbusintegrator.cpp:1659 #15 0x0036d653 in QDBusConnectionPrivate::findMetaObject ( this=<value optimized out>, service=<value optimized out>, path=<value optimized out>, interface=<value optimized out>, error=<value optimized out>) at qdbusintegrator.cpp:1988 #16 0x00379b3f in QDBusInterfacePrivate (this=<value optimized out>, serv=<value optimized out>, p=<value optimized out>, iface=<value optimized out>, con=<value optimized out>) at qdbusinterface.cpp:56 #17 0x00379c3f in QDBusInterface (this=<value optimized out>, service=<value optimized out>, path=<value optimized out>, interface=<value optimized out>, connection=<value optimized out>, parent= ) at qdbusinterface.cpp:117 #18 0x0059c07a in BluezBluetoothInterfacePrivate () at /usr/src/debug/kdebase-workspace-4.1.2/solid/bluez/bluez-bluetoothinterface.cpp:40 #19 BluezBluetoothInterface (this=0x83ad778, objectPath=@0xbf89d454) at /usr/src/debug/kdebase-workspace-4.1.2/solid/bluez/bluez-bluetoothinterface.cpp:49 #20 0x00596414 in BluezBluetoothManager::createInterface (this=0x83aa948, ubi=@0xbf89d454) at /usr/src/debug/kdebase-workspace-4.1.2/solid/bluez/bluez-bluetoothmanager.cpp:116 #21 0x0040dabe in Solid::Control::BluetoothManagerPrivate::findRegisteredBluetoothInterface (this=<value optimized out>, ubi=<value optimized out>) at /usr/src/debug/kdebase-workspace-4.1.2/libs/solid/control/bluetoothmanager.cpp:326 #22 0x0040deaa in Solid::Control::BluetoothManager::findBluetoothInterface ( this=<value optimized out>, ubi=<value optimized out>) at /usr/src/debug/kdebase-workspace-4.1.2/libs/solid/control/bluetoothmanager.cpp:144 #23 0x0040afdb in BluetoothInterface (this=) at /usr/src/debug/kdebase-workspace-4.1.2/libs/solid/control/bluetoothinterface.cpp:64 #24 0x0805037f in DeviceMan (this=0xbf89d4b4, parent=0x0) at /usr/src/debug/kdebluetooth4-0.2/src/device-manager/devicemanager.cpp:43 #25 0x0804c7ea in main (argc=1, argv=0xbf89d684) at /usr/src/debug/kdebluetooth4-0.2/src/device-manager/main.cpp:67
Confirmed. The problem is, that kdebluetooth doesn't support bluez4 atm. See here also https://bugs.launchpad.net/ubuntu/+source/kdebase-workspace/+bug/280997 (btw great that Ubuntu failed to send this upstream, big *grrrr*).
Set priority to high since bluetooth-support is essential.
@dgollub Is there anything I can help with to get this done asap? As far as I did note from reading at http://bluetooth.kmobiletools.org and http://kde-apps.org/content/show.php/kdebluetooth4?content=84761 the plan is to integrate bluez4-support into solid. Any more hints where I can start with to help to progress here? Probably it's already in the svn somewhere? :)
I am also getting this problem in a fresh install of Fedora 10. I'm using the standard repo (not development), which is serving KDE 4.1.3; $ kbluetooth4 -v Qt: 4.4.3 KDE: 4.1.3 (KDE 4.1.3) KBluetooth4 - The KDE4 Bluetooth Framework: 0.1 ...even though the package is labelled as 0.2-3.fc10. I seem to remember that this worked fine in Fedora 9, but that was an upgraded install since Fedora 7.
Hmm could I just downgrade bluez to get it working for now?
*** Bug 177421 has been marked as a duplicate of this bug. ***
(In reply to comment #3) > @dgollub > Is there anything I can help with to get this done asap? As far as I did note > from reading at http://bluetooth.kmobiletools.org and > http://kde-apps.org/content/show.php/kdebluetooth4?content=84761 the plan is to > integrate bluez4-support into solid. Any more hints where I can start with to > help to progress here? Probably it's already in the svn somewhere? :) > Tom Patzig started looking into porting/writing a new solid-bluetooth backend. Unfortunately he is in middle of his final-exams and can't put much time in this effort. Myself is also lacking any spare time in providing a quick fix for this issue. So any is more then appreciated in introduced/porting solid-bluetooth backend for BlueZ 4.x. But i highly recommend to contact Tom first to continue his latest effort - IIRC he used to have some KDE svn playground repo. (In reply to comment #5) > Hmm could I just downgrade bluez to get it working for now? > Yes. The first solid-bluetooth backend was written against the BlueZ 3.x D-Bus API.
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
*** Bug 178389 has been marked as a duplicate of this bug. ***
(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 > On opensuse11.1 with kde4.1.3 downgrading to bluez 3.36 (as mentioned here) kbluetooth4 worked perfectly.
Any updates on the porting?
> On opensuse11.1 with kde4.1.3 downgrading to bluez 3.36 (as mentioned here) > kbluetooth4 worked perfectly. As there are changes in Solid-API kbluetooth4 for KDE 4.1 does not work any longer in KDE 4.2 so downgrading to bluez-3 is not a valid option any longer :-/ Its a pitty. Bye Thorsten
(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...
Now I don't know if this helps but a few months ago Ubuntu's Mario Limonciello started a porting effort as well. My guess is that he and Tom have been in contact but in case no one here is aware of it, his code is available on https://code.edge.launchpad.net/~superm1/kdebase/bluez-4.x *fingerscrossedtoseethisfixedin4.2* Best, Niels
yeah *fingerscrossedtoseethisfixedin4.2* too... I've voted for..
From what I read on the Ubuntu bug report, this won't be fixed for 4.2. Conversely, 4.2 will aggravate the situation by making even the bluez 3 workaround unfeasible. Can someone confirm? Wouldn't it be possible to delay 4.2 until this is fixed? I believe that many would appreciate to see a release done when it is ready. Also please note that uncertainty wrt this bug is possibly worse than the bug itself. How important is it considered? What priority is given to it? Is there some commitment to fix it for 4.2.x or for 4.3 or for 4.4? How does it come that there is no mention at all to this on the kde 4.2 / 4.2 / 4.3 feature plan documents? Any bit of light would be highly appreciated.
SVN commit 912019 by tpatzig: - missing icons - updated TODO, ChangLog for v0.3 release -------------------------------------------------- I think this maybe is coming to a resolution. Anyway I've just tried compiling kbluetooth4 with kde 4.2rc1 and it fails...don't know if it's my configuration fault or because kde 4.2rc1 misses the latest changes in the bluez backend... anyway I personally want to thank Tom for trying to fix this situation. His work is much appreciated
mmm...builds fine with latest kdebluetooth svn and 4.2rc1...and it seems to work :)
not on branch here: lass Solid::Control::BluetoothInterface' has no member named 'findBluetoothRemoteDeviceUBI' and so on...
After a hard last week, I released kdebluetooth4-0.3 today. This version is no feature release. Kdebluetooth4 provides now full bluez4 support. Therefore a lot of work and api change had to be done in solid-bluetooth. Means: kdebluetooth4-0.3 needs the latest solid-bluetooth (kdebase4-workspace) stuff to compile and run. I've patched the openSUSE kdebase4-workspace packages from KDE4.1 and KDE4.2 to support the latest solid-bluetooth changes. If someone needs these patches for other distro packages, let me know. Kdebluetooth4-0.3 also needs the latest bluez and obex-data-server package. All kdebluetooth4 features (known from version 0.2) worked fine on my machine. The online/offline Mode (enable and disable your BT adapter) is really enhanced and should work fine now. Due to a bug in the current bluez package, KBlueLock is temporarly disabled. I ask everyone to test this new kdebluetooth4 version. Problems, issues and other questions are also answered in #kdebluetooth on freenode. Please let me know if I can close this bug ... because the tray applet now appears properly ;) Thanks for testing.
*** Bug 179224 has been marked as a duplicate of this bug. ***
Thanks Tom!
> If someone needs kdebase-workspace patches for other distro packages, let me > know. Yes please. Either here, privately, or kde-packagers list, other other public location would suffice.
Thanks tom...no issues for now...(testing with opensuse packages). Could your patches to solid be backported to the 4.2 branch before the tag? If I understand correctly bluetooth support is broken in vanilla 4.2 with either bluez 3.x and 4.x...so I think a backport cannot make things worse, can it? ps: you are on my personal heros list. :D
Really huge thanks tom!
Huge thanks!!! I really hope that the strategy suggested by Giovanni can be applied!
Awesome, but we need this definately in official kde4.2!
*** Bug 181361 has been marked as a duplicate of this bug. ***
*** Bug 180297 has been marked as a duplicate of this bug. ***
Thanks Tom, thanks to you a lot more people will be able to use KDE 4.2, we are all grateful.
How can I test it on Fedora 10, Tom? Thanks for the excellent job you are doing!
I'll do my best to release 0.3 RPMs during the weekend. - Gilboa
Hi, could the fix make it in the just released 4.2? - Sergio
As far as I can see it didn't make into Fedora Rawhide, they still have 0.2.3 (KDE 4.2 is available in Rawhide).
Created attachment 30864 [details] solid-bluetooth diff from trunk to 4.1 branch
Created attachment 30865 [details] solid-bluetooth diff from trunk to 4.2 branch
Because of some delayed demands, i attached the patches from solid-bluetooth trunk to 4.1 and 4.2 branches.
Thanks for porting Tom :-) Is there any time frame when obex-browsing (kio-bluetooth) will be ported? In KDE 4.2 I have only uni-directional (outgoing) file transfer and have to use the obextools for geting data from a remote device. Bye Thorsten
(In reply to comment #38) > Thanks for porting Tom :-) > Is there any time frame when obex-browsing (kio-bluetooth) will be ported? gpothier is working on that. Just stay patient ...