LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 05-20-2008, 04:19 AM   #1
bogzab
Member
 
Registered: Mar 2006
Location: Dyserth, Wales
Distribution: Slackware 14.0, Slackware 14.1, Slackware-current
Posts: 306

Rep: Reputation: 33
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?

Thanks
 
Old 05-20-2008, 07:29 AM   #2
Hangdog42
LQ Veteran
 
Registered: Feb 2003
Location: Maryland
Distribution: Slackware
Posts: 7,803
Blog Entries: 1

Rep: Reputation: 422Reputation: 422Reputation: 422Reputation: 422Reputation: 422
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.
 
Old 05-20-2008, 02:03 PM   #3
bogzab
Member
 
Registered: Mar 2006
Location: Dyserth, Wales
Distribution: Slackware 14.0, Slackware 14.1, Slackware-current
Posts: 306

Original Poster
Rep: Reputation: 33
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.
 
Old 12-22-2008, 04:02 PM   #4
mjjzf
Member
 
Registered: Feb 2004
Location: Valby, Denmark / Citizen of the Web
Distribution: Slackware 14.1
Posts: 879

Rep: Reputation: 39
Unhappy

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.
This also yields a crash dialog.
Any ideas?
 
Old 12-23-2008, 12:51 PM   #5
Hangdog42
LQ Veteran
 
Registered: Feb 2003
Location: Maryland
Distribution: Slackware
Posts: 7,803
Blog Entries: 1

Rep: Reputation: 422Reputation: 422Reputation: 422Reputation: 422Reputation: 422
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.
 
Old 12-24-2008, 01:35 AM   #6
bogzab
Member
 
Registered: Mar 2006
Location: Dyserth, Wales
Distribution: Slackware 14.0, Slackware 14.1, Slackware-current
Posts: 306

Original Poster
Rep: Reputation: 33
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.
 
Old 12-25-2008, 04:00 AM   #7
lucmove
Senior Member
 
Registered: Aug 2005
Location: Brazil
Distribution: Debian
Posts: 1,432

Rep: Reputation: 110Reputation: 110
Uh? What? Bluetooth working on Slackware? What are on Earth these people talking about?
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Kbluetooth init problem marco18 Linux - Software 0 05-15-2008 09:08 AM
kbluetooth doesn't find my bluetooth dongle biiiep Ubuntu 1 11-17-2007 04:04 PM
Bluetooth Pairing problems in Slackware12 with KBluetooth gopi.d Slackware 1 11-08-2007 04:16 AM
kdetv crashes with Slack 10.1. egag Slackware 1 02-12-2005 09:09 AM
Mplayer crashes with Xorg (Slack 10) OdieQ Slackware 5 07-07-2004 08:17 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 02:52 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration