Description: KBluetooth is a program which aims to provide a complete application for the usage of bluetooth within KDE.
This is a continuation of kde-bluetooth, but with a very different philosophy, we're going to focus first in the user needs, which means implement everything that a bluetooth application should have.
Once we have it finished and the user has almost all his needs fulfilled, we'll change our focus to develop/improve the current KDE bluetooth support, so a lot of solid movement is expected.Last changelog:
Version 0.4.2 ===================================== * Fix speed calculation when receiving and sending filesI * Pairing request are accepted also when clicking on Trust button * Important dialogs are modal, so they're not hidden by other applications * Fix a crash that happens when the sender device disconnects before the file transfer is accepted
Version 0.4.1 ===================================== * Fix a crash when receiving files
Version 0.4 ===================================== * Kbluetooth can connect to an already know device without have to remove/create it again. * Fix quite a lot dbus related crashes. * The receive directory is now configurable with an interface. * The receive dialog allows you to configure where the file will be saved. * Add devices to a \"white list\" to auto accept files comming from these devices (uses KWallet so is secure). * Send to allow to select more than one file to be send. * Fix some issues while receiving more than one file in the same execution. * Integration with nepomuk (this was done before, but not announced). * Nepomuk is optional at build time. * Compatible with kde 4.3 or greater * i18n should be fixed now, let\'s go to translate!
Hi!
Thanks for a nice app.
I am unable to compile with the new kde sc 4.6:
kbluetooth-0.4.2/src/adapterwidget.h:28:46: fatal error: solid/control/bluetoothinterface.h: No such file or directory
compilation terminated.
I'm on archlinux and using the pkgbuild from aur to build
The first time I run Kbluetooth a window pops up with the title "Choose Folder" completely skipping the part what this folder is supposed to be for (recieved files, serials, connection data, what?!) :D It could be useful telling users what this is.
But nice work anyway, cheers!
Kubuntu 10.04 LTS, KBluetooth is 0.4.
I have a Rocketfish universal Bluetooth adapter (RF-MRBTAD, Broadcom based), it connects with a lot of stuff when KBluetooth stays running.
For other reasons I have disabled KWallet (I cannot trust and will not and cannot rely upon anything but myself to store sensitive data such as passwords), and Nepomuk is totally UNWANTED on my system.
Sorry to see the wholesale dependence on these programs. Maybe my deconfiguration of these programs is why KBluetooth will crash on random user interactions? That said, keep in mind that I will not allow them back just to help KBluetooth - they really shouldn't be critical to an application reading and writing configuration files.
FWIW, the multiple file dialog is checked but usually KBluetooth will only allow single files to be transferred. Only ONCE has KBluetooth allowed me a multi file transfer. Nothing changed on the source device of the files, only KBluetooth changes because after it crashes some configuration data is missing.
Hi,
kbluetooth is one of the best kde-apps ;) But I'm really missing the audio-feature.
Is it already in current svn? Is there any time for release of 0.5?
I just downloaded the archive and extracted it. How can I compile it? There is no configure or make file.
Maybe there is help in the readme-file, but there is no readme-file.
So I searched the linked project-website for help and found: nothing!
Ok, I am just a normal, stupid user, but I asked myself: why it is so hard to write an installation-how-to and publish it on the website of this project?
Can anybody tell me that?
Take it easy men, we're not here to serve you keep it in mind.
There is no "install" because advanced users usually know how to deal with cmake, and normal users wait until they distribution packs the software.
To build it just do:
cmake ./ -CMAKE_INSTALL_PREFIX=(your prefix here)
And then:
make install
Cya
What a pity, it really sounds like a good App,- but also "keep in mind": first of all, we are "users". All we need is something we can "use".
I dont know where any header files or compiler binaries have to be or wich Prefix this cmake order really needs for don't running in trouble with my other bluetooth installations.
Such a high risk prevents me from making any experiments with it..
As i said: what a pity.
This nice piece of work and all the time it needed, was only made for some kind of "advanced linux users".
Hi!
pch@pch:~/Bin/kbluetooth-0.4$ kbluetooth
kbluetooth(5305)/kdeui (KNotification) KStatusNotifierItemDBus::KStatusNotifierItemDBus: service is "org.kde.StatusNotifierItem-5305-1"
kbluetooth(5305)/kdeui (KNotification) KStatusNotifierItemPrivate::registerToDaemon: Registering a client interface to the KStatusNotifierWatcher
kbluetooth(5305) KBlueTray::initMenu: Enabling obex server
kbluetooth(5305)/kdecore (KSycoca) KSycocaPrivate::openDatabase: Trying to open ksycoca from "/var/tmp/kdecache-pch/ksycoca4"
kbluetooth(5305)/kdecore (KLibrary) kde4Factory: The library "/usr/lib/kde4/solid_bluez.so" does not offer a qt_plugin_instance function.
kbluetooth(5305) Solid::Control::ManagerBasePrivate::loadBackend: Backend loaded: "BlueZ"
kbluetooth(5305) Solid::Control::BluetoothManager::buildDeviceList: UBI List ("/org/bluez/5293/hci0")
kbluetooth(5305) Solid::Control::BluetoothManagerPrivate::findRegisteredBluetoothInterface: findRegisteredBluetoothInterface "/org/bluez/5293/hci0"
kbluetooth(5305) Solid::Control::BluetoothManagerPrivate::findRegisteredBluetoothInterface: Creating New Interface "/org/bluez/5293/hci0"
kbluetooth(5305) Solid::Control::BluetoothManagerPrivate::findRegisteredBluetoothInterface: Calling Backend to Creating New Interface "/org/bluez/5293/hci0"
kbluetooth(5305) Solid::Control::BluetoothManagerPrivate::findRegisteredBluetoothInterface: BackendIface created
kbluetooth(5305) BluezBluetoothManager::defaultInterface: Calling Backend Default Interface
QDBusObjectPath: invalid path ""
kbluetooth(5305) KBlueTray::onlineMode: online Mode
kbluetooth(5305) Solid::Control::BluetoothManager::buildDeviceList: UBI List ("/org/bluez/5293/hci0")
kbluetooth(5305) Solid::Control::BluetoothManagerPrivate::findRegisteredBluetoothInterface: findRegisteredBluetoothInterface "/org/bluez/5293/hci0"
kbluetooth(5305) KBlueTray::onlineMode: adapter size 1
kbluetooth(5305) BluezBluetoothManager::defaultInterface: Calling Backend Default Interface
QDBusObjectPath: invalid path ""
kbluetooth(5305) Solid::Control::BluetoothManagerPrivate::findRegisteredBluetoothInterface: findRegisteredBluetoothInterface ""
kbluetooth(5305) Solid::Control::BluetoothManagerPrivate::findRegisteredBluetoothInterface: Creating New Interface ""
kbluetooth(5305) Solid::Control::BluetoothManagerPrivate::findRegisteredBluetoothInterface: Calling Backend to Creating New Interface ""
process 5305: arguments to dbus_message_new_method_call() were incorrect, assertion "_dbus_check_is_valid_path (path)" failed in file dbus-message.c line 1078.
This is normally a bug in some application using the D-Bus library.
process 5305: arguments to dbus_message_iter_init_append() were incorrect, assertion "message != NULL" failed in file dbus-message.c line 2077.
This is normally a bug in some application using the D-Bus library.
QDBusConnection: error: could not send message to service "org.bluez" path "" interface "org.freedesktop.DBus.Introspectable" member "Introspect":
kbluetooth(5305) Solid::Control::BluetoothManagerPrivate::findRegisteredBluetoothInterface: BackendIface created
kbluetooth(5305) KBlueTray::onlineMode: Adapter found ""
AGENT registered !
kbluetooth(5305) KBlueTray::updateTooltip: Updating Tooltip
kbluetooth(5305) ObexServer::ObexServer: ""
kbluetooth(5305) ObexServer::ObexServer: (QVariant(QString, "") , QVariant(QString, "opp") , QVariant(bool, false) )
kbluetooth(5305) ObexServer::ObexServer: CallWithCallback
kbluetooth(5305) ObexServer::serverCreatedError: Error creating Bluetooth Server: "Invalid Bluetooth address"
Bus 005 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
pch
I uninstalled all software mentioned on
http://wiki.archlinux.org/index.php/Bluetooth
and then reinstalled them, and that seamed to what fixed kbluetooth for me.
Although I have a feeling that it may have been just the purging and reinstall of Blueman, along with messing with Blueman some, that may have fixed kbluetooth, and
that it may have been Blueman that broke kbluetooth in the first place, but I don't know for sure.
this was one of the messages I got when kbluetooth wasn't working:
kbluetooth(4412)/kdecore (KLibrary) kde4Factory: The library "/usr/lib/kde4/solid_bluez.so" does not offer a qt_plugin_instance function.
Hi!
pch@pch:~/Bin/kbluetooth-0.4$ kbluetooth
kbluetooth(5305)/kdeui (KNotification) KStatusNotifierItemDBus::KStatusNotifierItemDBus: service is "org.kde.StatusNotifierItem-5305-1"
kbluetooth(5305)/kdeui (KNotification) KStatusNotifierItemPrivate::registerToDaemon: Registering a client interface to the KStatusNotifierWatcher
kbluetooth(5305) KBlueTray::initMenu: Enabling obex server
kbluetooth(5305)/kdecore (KSycoca) KSycocaPrivate::openDatabase: Trying to open ksycoca from "/var/tmp/kdecache-pch/ksycoca4"
kbluetooth(5305)/kdecore (KLibrary) kde4Factory: The library "/usr/lib/kde4/solid_bluez.so" does not offer a qt_plugin_instance function.
kbluetooth(5305) Solid::Control::ManagerBasePrivate::loadBackend: Backend loaded: "BlueZ"
kbluetooth(5305) Solid::Control::BluetoothManager::buildDeviceList: UBI List ("/org/bluez/5293/hci0")
kbluetooth(5305) Solid::Control::BluetoothManagerPrivate::findRegisteredBluetoothInterface: findRegisteredBluetoothInterface "/org/bluez/5293/hci0"
kbluetooth(5305) Solid::Control::BluetoothManagerPrivate::findRegisteredBluetoothInterface: Creating New Interface "/org/bluez/5293/hci0"
kbluetooth(5305) Solid::Control::BluetoothManagerPrivate::findRegisteredBluetoothInterface: Calling Backend to Creating New Interface "/org/bluez/5293/hci0"
kbluetooth(5305) Solid::Control::BluetoothManagerPrivate::findRegisteredBluetoothInterface: BackendIface created
kbluetooth(5305) BluezBluetoothManager::defaultInterface: Calling Backend Default Interface
QDBusObjectPath: invalid path ""
kbluetooth(5305) KBlueTray::onlineMode: online Mode
kbluetooth(5305) Solid::Control::BluetoothManager::buildDeviceList: UBI List ("/org/bluez/5293/hci0")
kbluetooth(5305) Solid::Control::BluetoothManagerPrivate::findRegisteredBluetoothInterface: findRegisteredBluetoothInterface "/org/bluez/5293/hci0"
kbluetooth(5305) KBlueTray::onlineMode: adapter size 1
kbluetooth(5305) BluezBluetoothManager::defaultInterface: Calling Backend Default Interface
QDBusObjectPath: invalid path ""
kbluetooth(5305) Solid::Control::BluetoothManagerPrivate::findRegisteredBluetoothInterface: findRegisteredBluetoothInterface ""
kbluetooth(5305) Solid::Control::BluetoothManagerPrivate::findRegisteredBluetoothInterface: Creating New Interface ""
kbluetooth(5305) Solid::Control::BluetoothManagerPrivate::findRegisteredBluetoothInterface: Calling Backend to Creating New Interface ""
process 5305: arguments to dbus_message_new_method_call() were incorrect, assertion "_dbus_check_is_valid_path (path)" failed in file dbus-message.c line 1078.
This is normally a bug in some application using the D-Bus library.
process 5305: arguments to dbus_message_iter_init_append() were incorrect, assertion "message != NULL" failed in file dbus-message.c line 2077.
This is normally a bug in some application using the D-Bus library.
QDBusConnection: error: could not send message to service "org.bluez" path "" interface "org.freedesktop.DBus.Introspectable" member "Introspect":
kbluetooth(5305) Solid::Control::BluetoothManagerPrivate::findRegisteredBluetoothInterface: BackendIface created
kbluetooth(5305) KBlueTray::onlineMode: Adapter found ""
AGENT registered !
kbluetooth(5305) KBlueTray::updateTooltip: Updating Tooltip
kbluetooth(5305) ObexServer::ObexServer: ""
kbluetooth(5305) ObexServer::ObexServer: (QVariant(QString, "") , QVariant(QString, "opp") , QVariant(bool, false) )
kbluetooth(5305) ObexServer::ObexServer: CallWithCallback
kbluetooth(5305) ObexServer::serverCreatedError: Error creating Bluetooth Server: "Invalid Bluetooth address"
Bus 005 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
pch
Is it in SVN? I can't find it. I hope this message is related to "Crash after receiving file". For now I build kbluetooth for Fedora Rawhide only, I don't want to ship it in F11/12 without this fix.
Thanks
Jaroslav
Version 0.4
Using KDE Development Platform 4.3.95 (KDE 4.3.95 (KDE 4.4 RC2))
just compiled.
Crashes after receiving a jpg file from my Nokia 5800 mobile.
The phone is set as trusted.
I compiled this release on my Mandriva 2010.0 x86-64 and KDE 4.3.2.
Pairing between my Nokia 5300 XpressMusic and Pc has correct, but I can send/receive only one (or more) files in one shot, like previous version.
For sending/receiving other contents I must close kbluetooth and re-launch it everytime.
If helpfull, this is my usb dongle bluetooth:
Bus 005 Device 002: ID 1131:1001 Integrated System Solution Corp. KY-BT100 Bluetooth Adapter
Regards
https://bugs.kde.org/show_bug.cgi?id=208398
kbluetooth finds my bluetooth mouse, but fails to add it with message "Sorry your Bluetooth Device does not support input Service". Blueman successfully adds mouse.
Is there any way how to add option "sent through bluetooth" to the kde dialog / actions? Or can you add option to the kbluetooth
kbluetooth --send <file> <phone>
the same like blueman can do with blueman-sendto.
Hi
ERROR:dbus.connection:Exception in handler for D-Bus signal:
Traceback (most recent call last):
File "/usr/lib/pymodules/python2.6/dbus/connection.py", line 214, in maybe_handle_message
self._handler(*args, **kwargs)
File "/usr/bin/kblueplugd", line 41, in slotAdapterAdded
print "bt dev added:", device, "# of devices:", len(manager.ListAdapters())
File "/usr/lib/pymodules/python2.6/dbus/proxies.py", line 140, in __call__
**keywords)
File "/usr/lib/pymodules/python2.6/dbus/connection.py", line 620, in call_blocking
message, timeout)
DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name :1.24 was not provided by any .service files
my bluetooth dongle:
Bus 005 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
I am trying to compile RC2 on my 64bit gentoo box, but i always get this error:
Linking CXX executable kbluetooth
/usr/lib/gcc/x86_64-pc-linux-gnu/4.4.2/../../../../x86_64-pc-linux-gnu/bin/ld: cannot find -lKDE4Workspace__solidcontrol
collect2: ld returned 1 exit status
make[2]: *** [src/kbluetooth] Error 1
make[1]: *** [src/CMakeFiles/kbluetooth.dir/all] Error 2
make: *** [all] Error 2
Ratings & Comments
58 Comments
Hi! Thanks for a nice app. I am unable to compile with the new kde sc 4.6: kbluetooth-0.4.2/src/adapterwidget.h:28:46: fatal error: solid/control/bluetoothinterface.h: No such file or directory compilation terminated. I'm on archlinux and using the pkgbuild from aur to build
The first time I run Kbluetooth a window pops up with the title "Choose Folder" completely skipping the part what this folder is supposed to be for (recieved files, serials, connection data, what?!) :D It could be useful telling users what this is. But nice work anyway, cheers!
Kubuntu 10.04 LTS, KBluetooth is 0.4. I have a Rocketfish universal Bluetooth adapter (RF-MRBTAD, Broadcom based), it connects with a lot of stuff when KBluetooth stays running. For other reasons I have disabled KWallet (I cannot trust and will not and cannot rely upon anything but myself to store sensitive data such as passwords), and Nepomuk is totally UNWANTED on my system. Sorry to see the wholesale dependence on these programs. Maybe my deconfiguration of these programs is why KBluetooth will crash on random user interactions? That said, keep in mind that I will not allow them back just to help KBluetooth - they really shouldn't be critical to an application reading and writing configuration files. FWIW, the multiple file dialog is checked but usually KBluetooth will only allow single files to be transferred. Only ONCE has KBluetooth allowed me a multi file transfer. Nothing changed on the source device of the files, only KBluetooth changes because after it crashes some configuration data is missing.
Hi, kbluetooth is one of the best kde-apps ;) But I'm really missing the audio-feature. Is it already in current svn? Is there any time for release of 0.5?
Hi, is there a way to only start the kbluetooth applet (from the system tray) when there is a hardware or the hardware is turn on?
I just downloaded the archive and extracted it. How can I compile it? There is no configure or make file. Maybe there is help in the readme-file, but there is no readme-file. So I searched the linked project-website for help and found: nothing! Ok, I am just a normal, stupid user, but I asked myself: why it is so hard to write an installation-how-to and publish it on the website of this project? Can anybody tell me that?
Take it easy men, we're not here to serve you keep it in mind. There is no "install" because advanced users usually know how to deal with cmake, and normal users wait until they distribution packs the software. To build it just do: cmake ./ -CMAKE_INSTALL_PREFIX=(your prefix here) And then: make install Cya
What a pity, it really sounds like a good App,- but also "keep in mind": first of all, we are "users". All we need is something we can "use". I dont know where any header files or compiler binaries have to be or wich Prefix this cmake order really needs for don't running in trouble with my other bluetooth installations. Such a high risk prevents me from making any experiments with it.. As i said: what a pity. This nice piece of work and all the time it needed, was only made for some kind of "advanced linux users".
I've compiled latest source code on my Mandriva 2010.0 x86-64 and kbluetooth works well, finally. Good job.
Hi. The version info just states 0.4 Would be nice to see if it's 0.4.1 or 0.4.2...
Hi! pch@pch:~/Bin/kbluetooth-0.4$ kbluetooth kbluetooth(5305)/kdeui (KNotification) KStatusNotifierItemDBus::KStatusNotifierItemDBus: service is "org.kde.StatusNotifierItem-5305-1" kbluetooth(5305)/kdeui (KNotification) KStatusNotifierItemPrivate::registerToDaemon: Registering a client interface to the KStatusNotifierWatcher kbluetooth(5305) KBlueTray::initMenu: Enabling obex server kbluetooth(5305)/kdecore (KSycoca) KSycocaPrivate::openDatabase: Trying to open ksycoca from "/var/tmp/kdecache-pch/ksycoca4" kbluetooth(5305)/kdecore (KLibrary) kde4Factory: The library "/usr/lib/kde4/solid_bluez.so" does not offer a qt_plugin_instance function. kbluetooth(5305) Solid::Control::ManagerBasePrivate::loadBackend: Backend loaded: "BlueZ" kbluetooth(5305) Solid::Control::BluetoothManager::buildDeviceList: UBI List ("/org/bluez/5293/hci0") kbluetooth(5305) Solid::Control::BluetoothManagerPrivate::findRegisteredBluetoothInterface: findRegisteredBluetoothInterface "/org/bluez/5293/hci0" kbluetooth(5305) Solid::Control::BluetoothManagerPrivate::findRegisteredBluetoothInterface: Creating New Interface "/org/bluez/5293/hci0" kbluetooth(5305) Solid::Control::BluetoothManagerPrivate::findRegisteredBluetoothInterface: Calling Backend to Creating New Interface "/org/bluez/5293/hci0" kbluetooth(5305) Solid::Control::BluetoothManagerPrivate::findRegisteredBluetoothInterface: BackendIface created kbluetooth(5305) BluezBluetoothManager::defaultInterface: Calling Backend Default Interface QDBusObjectPath: invalid path "" kbluetooth(5305) KBlueTray::onlineMode: online Mode kbluetooth(5305) Solid::Control::BluetoothManager::buildDeviceList: UBI List ("/org/bluez/5293/hci0") kbluetooth(5305) Solid::Control::BluetoothManagerPrivate::findRegisteredBluetoothInterface: findRegisteredBluetoothInterface "/org/bluez/5293/hci0" kbluetooth(5305) KBlueTray::onlineMode: adapter size 1 kbluetooth(5305) BluezBluetoothManager::defaultInterface: Calling Backend Default Interface QDBusObjectPath: invalid path "" kbluetooth(5305) Solid::Control::BluetoothManagerPrivate::findRegisteredBluetoothInterface: findRegisteredBluetoothInterface "" kbluetooth(5305) Solid::Control::BluetoothManagerPrivate::findRegisteredBluetoothInterface: Creating New Interface "" kbluetooth(5305) Solid::Control::BluetoothManagerPrivate::findRegisteredBluetoothInterface: Calling Backend to Creating New Interface "" process 5305: arguments to dbus_message_new_method_call() were incorrect, assertion "_dbus_check_is_valid_path (path)" failed in file dbus-message.c line 1078. This is normally a bug in some application using the D-Bus library. process 5305: arguments to dbus_message_iter_init_append() were incorrect, assertion "message != NULL" failed in file dbus-message.c line 2077. This is normally a bug in some application using the D-Bus library. QDBusConnection: error: could not send message to service "org.bluez" path "" interface "org.freedesktop.DBus.Introspectable" member "Introspect": kbluetooth(5305) Solid::Control::BluetoothManagerPrivate::findRegisteredBluetoothInterface: BackendIface created kbluetooth(5305) KBlueTray::onlineMode: Adapter found "" AGENT registered ! kbluetooth(5305) KBlueTray::updateTooltip: Updating Tooltip kbluetooth(5305) ObexServer::ObexServer: "" kbluetooth(5305) ObexServer::ObexServer: (QVariant(QString, "") , QVariant(QString, "opp") , QVariant(bool, false) ) kbluetooth(5305) ObexServer::ObexServer: CallWithCallback kbluetooth(5305) ObexServer::serverCreatedError: Error creating Bluetooth Server: "Invalid Bluetooth address" Bus 005 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) pch
Please, report a bug with all the required information (your distro and so on), kde-apps is not a bugtracker :/
I uninstalled all software mentioned on http://wiki.archlinux.org/index.php/Bluetooth and then reinstalled them, and that seamed to what fixed kbluetooth for me. Although I have a feeling that it may have been just the purging and reinstall of Blueman, along with messing with Blueman some, that may have fixed kbluetooth, and that it may have been Blueman that broke kbluetooth in the first place, but I don't know for sure. this was one of the messages I got when kbluetooth wasn't working: kbluetooth(4412)/kdecore (KLibrary) kde4Factory: The library "/usr/lib/kde4/solid_bluez.so" does not offer a qt_plugin_instance function.
Hi! pch@pch:~/Bin/kbluetooth-0.4$ kbluetooth kbluetooth(5305)/kdeui (KNotification) KStatusNotifierItemDBus::KStatusNotifierItemDBus: service is "org.kde.StatusNotifierItem-5305-1" kbluetooth(5305)/kdeui (KNotification) KStatusNotifierItemPrivate::registerToDaemon: Registering a client interface to the KStatusNotifierWatcher kbluetooth(5305) KBlueTray::initMenu: Enabling obex server kbluetooth(5305)/kdecore (KSycoca) KSycocaPrivate::openDatabase: Trying to open ksycoca from "/var/tmp/kdecache-pch/ksycoca4" kbluetooth(5305)/kdecore (KLibrary) kde4Factory: The library "/usr/lib/kde4/solid_bluez.so" does not offer a qt_plugin_instance function. kbluetooth(5305) Solid::Control::ManagerBasePrivate::loadBackend: Backend loaded: "BlueZ" kbluetooth(5305) Solid::Control::BluetoothManager::buildDeviceList: UBI List ("/org/bluez/5293/hci0") kbluetooth(5305) Solid::Control::BluetoothManagerPrivate::findRegisteredBluetoothInterface: findRegisteredBluetoothInterface "/org/bluez/5293/hci0" kbluetooth(5305) Solid::Control::BluetoothManagerPrivate::findRegisteredBluetoothInterface: Creating New Interface "/org/bluez/5293/hci0" kbluetooth(5305) Solid::Control::BluetoothManagerPrivate::findRegisteredBluetoothInterface: Calling Backend to Creating New Interface "/org/bluez/5293/hci0" kbluetooth(5305) Solid::Control::BluetoothManagerPrivate::findRegisteredBluetoothInterface: BackendIface created kbluetooth(5305) BluezBluetoothManager::defaultInterface: Calling Backend Default Interface QDBusObjectPath: invalid path "" kbluetooth(5305) KBlueTray::onlineMode: online Mode kbluetooth(5305) Solid::Control::BluetoothManager::buildDeviceList: UBI List ("/org/bluez/5293/hci0") kbluetooth(5305) Solid::Control::BluetoothManagerPrivate::findRegisteredBluetoothInterface: findRegisteredBluetoothInterface "/org/bluez/5293/hci0" kbluetooth(5305) KBlueTray::onlineMode: adapter size 1 kbluetooth(5305) BluezBluetoothManager::defaultInterface: Calling Backend Default Interface QDBusObjectPath: invalid path "" kbluetooth(5305) Solid::Control::BluetoothManagerPrivate::findRegisteredBluetoothInterface: findRegisteredBluetoothInterface "" kbluetooth(5305) Solid::Control::BluetoothManagerPrivate::findRegisteredBluetoothInterface: Creating New Interface "" kbluetooth(5305) Solid::Control::BluetoothManagerPrivate::findRegisteredBluetoothInterface: Calling Backend to Creating New Interface "" process 5305: arguments to dbus_message_new_method_call() were incorrect, assertion "_dbus_check_is_valid_path (path)" failed in file dbus-message.c line 1078. This is normally a bug in some application using the D-Bus library. process 5305: arguments to dbus_message_iter_init_append() were incorrect, assertion "message != NULL" failed in file dbus-message.c line 2077. This is normally a bug in some application using the D-Bus library. QDBusConnection: error: could not send message to service "org.bluez" path "" interface "org.freedesktop.DBus.Introspectable" member "Introspect": kbluetooth(5305) Solid::Control::BluetoothManagerPrivate::findRegisteredBluetoothInterface: BackendIface created kbluetooth(5305) KBlueTray::onlineMode: Adapter found "" AGENT registered ! kbluetooth(5305) KBlueTray::updateTooltip: Updating Tooltip kbluetooth(5305) ObexServer::ObexServer: "" kbluetooth(5305) ObexServer::ObexServer: (QVariant(QString, "") , QVariant(QString, "opp") , QVariant(bool, false) ) kbluetooth(5305) ObexServer::ObexServer: CallWithCallback kbluetooth(5305) ObexServer::serverCreatedError: Error creating Bluetooth Server: "Invalid Bluetooth address" Bus 005 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) pch
Ups, crash fixed, let me do some test before do another crash-release.
Is it in SVN? I can't find it. I hope this message is related to "Crash after receiving file". For now I build kbluetooth for Fedora Rawhide only, I don't want to ship it in F11/12 without this fix. Thanks Jaroslav
Version 0.4 Using KDE Development Platform 4.3.95 (KDE 4.3.95 (KDE 4.4 RC2)) just compiled. Crashes after receiving a jpg file from my Nokia 5800 mobile. The phone is set as trusted.
I compiled this release on my Mandriva 2010.0 x86-64 and KDE 4.3.2. Pairing between my Nokia 5300 XpressMusic and Pc has correct, but I can send/receive only one (or more) files in one shot, like previous version. For sending/receiving other contents I must close kbluetooth and re-launch it everytime. If helpfull, this is my usb dongle bluetooth: Bus 005 Device 002: ID 1131:1001 Integrated System Solution Corp. KY-BT100 Bluetooth Adapter Regards
https://bugs.kde.org/show_bug.cgi?id=208398 kbluetooth finds my bluetooth mouse, but fails to add it with message "Sorry your Bluetooth Device does not support input Service". Blueman successfully adds mouse.
Is there any way how to add option "sent through bluetooth" to the kde dialog / actions? Or can you add option to the kbluetooth kbluetooth --send <file> <phone> the same like blueman can do with blueman-sendto.
What's the sollution for the kio_obex issue?
There is no solution, at the moment no kio_obex exists :(
Hi ERROR:dbus.connection:Exception in handler for D-Bus signal: Traceback (most recent call last): File "/usr/lib/pymodules/python2.6/dbus/connection.py", line 214, in maybe_handle_message self._handler(*args, **kwargs) File "/usr/bin/kblueplugd", line 41, in slotAdapterAdded print "bt dev added:", device, "# of devices:", len(manager.ListAdapters()) File "/usr/lib/pymodules/python2.6/dbus/proxies.py", line 140, in __call__ **keywords) File "/usr/lib/pymodules/python2.6/dbus/connection.py", line 620, in call_blocking message, timeout) DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name :1.24 was not provided by any .service files my bluetooth dongle: Bus 005 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
I am trying to compile RC2 on my 64bit gentoo box, but i always get this error: Linking CXX executable kbluetooth /usr/lib/gcc/x86_64-pc-linux-gnu/4.4.2/../../../../x86_64-pc-linux-gnu/bin/ld: cannot find -lKDE4Workspace__solidcontrol collect2: ld returned 1 exit status make[2]: *** [src/kbluetooth] Error 1 make[1]: *** [src/CMakeFiles/kbluetooth.dir/all] Error 2 make: *** [all] Error 2
Same problem on Gentoo x86