Slack 12.1 KBluetooth crashes - BlueZ comms one-way only
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Slack 12.1 KBluetooth crashes - BlueZ comms one-way only
I had Bluetooth working fine on my laptop with Slack 12.0. After upgrading to 12.1 (everything else seems to be fine), KBluetooth crashes on startup and my laptop seems to be undiscoverable to most other BT devices (but not to my phone which finds it OK!). I cannot send files to the laptop even from the phone that can find it - when I try I get a "sending failed" message. I can send files from the laptop to other devices - the KDE OBEX push client seems to work fine and discovers other devices fine. "hcitool scan" also finds other devices.
The KBluetooth crash is described in various postings (not just Slackware by any means) but I have not found a fix for it anyplace. The non-discovery of my laptop by other devices may be unrelated and requires a fix in the hcid.conf file but I cannot see what that fix might be after looking at the man files.
I will post to KDE forums too, but have any Slackers had a similar problem? Found a solution?
I ran into exactly the same problem. The fix for me was to recompile KBluetooth with the Slackbuild script from Slackbuilds.org. I don't know what changed between 12.0 and 12.1, but it sure did hose KBluetooth.
Thanks - solved it. I was about to re-build KdeBluetooth anyway, but you reminded me to do the proper way - with a SlackBuild. All done and bluetooth file transfer working both into and out of the laptop. I did not realise that the KdeBluetooth package actually supplies the obex client.
I've got a big fail on this one - KDE Bluetooth with both the Slackbuild and a package from Slacky.eu. They crash big:
Code:
$ kbluetooth
kbluetooth: [KBluetooth::DBusSignal::DBusSignal(const QString&, const QString&, const QString&, DBusConnection*)] : org.bluez path: /org/bluez interface: org.bluez.Manager conn: 0x80da730
kbluetooth: [DBusMessage* KBluetooth::DBusSignal::newMessage(const QString&)] : org.bluez path: /org/bluez mInterfacE: org.bluez.Manager method: ListAdapters
kbluetooth: libkbluetooth: getStringList(): A security policy in place prevents this sender from sending this message to this recipient, see message bus configuration file (rejected message had interface "org.bluez.Manager" member "ListAdapters" error name "(unset)" destination "org.bluez")
kbluetooth: [QValueList<QString> KBluetooth::Manager::listAdapters()] 0
kbluetooth: [DBusMessage* KBluetooth::DBusSignal::newMessage(const QString&)] : org.bluez path: /org/bluez mInterfacE: org.bluez.Manager method: ListAdapters
kbluetooth: libkbluetooth: getStringList(): A security policy in place prevents this sender from sending this message to this recipient, see message bus configuration file (rejected message had interface "org.bluez.Manager" member "ListAdapters" error name "(unset)" destination "org.bluez")
kbluetooth: [KBluetooth::DBusSignal::DBusSignal(const QString&, const QString&, const QString&, DBusConnection*)] : org.bluez path: /org/bluez interface: org.bluez.Security conn: 0x80da730
kbluetooth: [DBusMessage* KBluetooth::DBusSignal::newMessage(const QString&)] : org.bluez path: /org/bluez mInterfacE: org.bluez.Security method: RegisterDefaultPasskeyAgent
kbluetooth: libkbluetooth: setString(RegisterDefaultPasskeyAgent): A security policy in place prevents this sender from sending this message to this recipient, see message bus configuration file (rejected message had interface "org.bluez.Security" member "RegisterDefaultPasskeyAgent" error name "(unset)" destination "org.bluez")
kbluetooth: [KBluetooth::DBusSignal::DBusSignal(const QString&, const QString&, const QString&, DBusConnection*)] : org.bluez path: /org/bluez interface: org.bluez.Security conn: 0x80da730
kbluetooth: [DBusMessage* KBluetooth::DBusSignal::newMessage(const QString&)] : org.bluez path: /org/bluez mInterfacE: org.bluez.Security method: RegisterDefaultAuthorizationAgent
kbluetooth: libkbluetooth: setString(RegisterDefaultAuthorizationAgent): A security policy in place prevents this sender from sending this message to this recipient, see message bus configuration file (rejected message had interface "org.bluez.Security" member "RegisterDefaultAuthorizationAgent" error name "(unset)" destination "org.bluez")
kbluetooth: [DBusMessage* KBluetooth::DBusSignal::newMessage(const QString&)] : org.bluez path: /org/bluez mInterfacE: org.bluez.Manager method: ListAdapters
kbluetooth: libkbluetooth: getStringList(): A security policy in place prevents this sender from sending this message to this recipient, see message bus configuration file (rejected message had interface "org.bluez.Manager" member "ListAdapters" error name "(unset)" destination "org.bluez")
kbluetooth: [QValueList<QString> KBluetooth::Manager::listAdapters()] 0
kbluetooth: [DBusMessage* KBluetooth::DBusSignal::newMessage(const QString&)] : org.bluez path: /org/bluez mInterfacE: org.bluez.Manager method: ListAdapters
kbluetooth: libkbluetooth: getStringList(): A security policy in place prevents this sender from sending this message to this recipient, see message bus configuration file (rejected message had interface "org.bluez.Manager" member "ListAdapters" error name "(unset)" destination "org.bluez")
kbluetooth: [DBusMessage* KBluetooth::DBusSignal::newMessage(const QString&)] : org.bluez path: /org/bluez mInterfacE: org.bluez.Manager method: ListAdapters
kbluetooth: libkbluetooth: getStringList(): A security policy in place prevents this sender from sending this message to this recipient, see message bus configuration file (rejected message had interface "org.bluez.Manager" member "ListAdapters" error name "(unset)" destination "org.bluez")
kbluetooth: [QValueList<QString> KBluetooth::Manager::listAdapters()] 0
kbluetooth: [DBusMessage* KBluetooth::DBusSignal::newMessage(const QString&)] : org.bluez path: /org/bluez mInterfacE: org.bluez.Manager method: ListAdapters
kbluetooth: libkbluetooth: getStringList(): A security policy in place prevents this sender from sending this message to this recipient, see message bus configuration file (rejected message had interface "org.bluez.Manager" member "ListAdapters" error name "(unset)" destination "org.bluez")
Still, it gives me a Bluetooth system tray icon, but with the apps greyed out. When I run Kbluemon, I get something similar:
Code:
$ kbluemon
mainDEBUG
kbluemon: [KBluetooth::DBusSignal::DBusSignal(const QString&, const QString&, const QString&, DBusConnection*)] : org.bluez path: /org/bluez interface: org.bluez.Manager conn: 0x8107298
kbluemon: [DBusMessage* KBluetooth::DBusSignal::newMessage(const QString&)] : org.bluez path: /org/bluez mInterfacE: org.bluez.Manager method: DefaultAdapter
kbluemon: libkbluetooth: getString(DefaultAdapter): A security policy in place prevents this sender from sending this message to this recipient, see message bus configuration file (rejected message had interface "org.bluez.Manager" member "DefaultAdapter" error name "(unset)" destination "org.bluez")
kbluemon: [KBluetooth::DBusSignal::DBusSignal(const QString&, const QString&, const QString&, DBusConnection*)] : org.bluez path: interface: org.bluez.Adapter conn: 0x8107298
kbluemon: Adding match failed: org.freedesktop.DBus.Error.MatchRuleInvalid: Path '' is invalid
kbluemon:
kbluemon: [DBusMessage* KBluetooth::DBusSignal::newMessage(const QString&)] : org.bluez path: mInterfacE: org.bluez.Adapter method: IsPeriodicDiscovery
process 4986: arguments to dbus_message_new_method_call() were incorrect, assertion "_dbus_check_is_valid_path (path)" failed in file dbus-message.c line 1074.
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 'kbluemon' crashing...
ERROR: Communication problem with kbluemon, it probably crashed.
You might want to start a new thread on this one to get more exposure. I haven't upgraded to 12.2 yet so I'm not going to be much use. However, it sort of looks that those errors are being caused by HAL. If you recently upgraded, you may want to make sure you re-read the CHANGES AND HINTS.txt and UPGRADE.txt because I think there were some special precautions you had to take with HAL.
I agree with Hangdog that you might start a new thread. For the record I have never got KBluetooth working 100% with Slack 12.1 (despite a posting in this thread which says it was OK once I got the Slackbuild installed. I have now failed to get it working on two PCs with Slack 12.1 - a laptop and a desktop, the latter after a 100% clean install following complete re-build of the PC. On both my machines KBluetooth starts but shows no bluetooth contacts in its main konqueror window. If I send a file to either of these PCs via Bluetooth a KDE window pops up just fine and allows me to save the file - so BT contacts are made - it is just the display of devices in the KBluetooth window that fails.
I was hoping that an upgrade to 12.1 might fix it and it still might for me I guess.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.