You are not logged in.

Dear visitor, welcome to KDE-Forum.org. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

1

Wednesday, December 19th 2007, 4:26pm

kde-bluetooth not knowing the location of the dbus socket

Hello,

I'm running debian lenny system. I installed kde-bluetooth in hope of getting easy-to-configure bluetooth filesharing with my mobile phone (nokia 6630). However when I tried to start kbluetooth it stated that it could not start because it didn't managed to connect to dbus.

Well, I figured out that it actually thinks that dbus socket is located at '/usr/local/var/run/dbus/system_bus_socket'

In order to get the program to start I created symlink: '/usr/local/var/run -> /var/run'
Well, it did manage to get kbluetooth to start but when I tried to look for bluetooth devices I got numerous of errors stating that dbus location was wrong.

Quoted


1.
Launched ok, pid = 16925
2.
Launched ok, pid = 16927
3.
process 16928: arguments to dbus_message_new_method_call() were incorrect, assertion "_dbus_check_is_valid_path (path)" failed in file dbus-message.c line 1074.
4.
This is normally a bug in some application using the D-Bus library.
5.
D-Bus not built with -rdynamic so unable to print a backtrace
6.
kioslave: ####### CRASH ###### protocol = kio_bluetooth pid = 16928 signal = 6
7.
process 16930: arguments to dbus_message_new_method_call() were incorrect, assertion "_dbus_check_is_valid_path (path)" failed in file dbus-message.c line 1074.
8.
This is normally a bug in some application using the D-Bus library.
9.
D-Bus not built with -rdynamic so unable to print a backtrace
10.
kioslave: ####### CRASH ###### protocol = kio_bluetooth pid = 16930 signal = 6


So what I want to do is the configure kbluetooth to know that dbus socket is located in '/var/run/dbus/system_bus_socket'. How do I do that ?

ps.
I remember compiling kdelibs to avoid arts depency so I reinstalled it with 'apt-get --reinstall install kdelibs'. Even so problem kept occuring.

toad

Trainee

Posts: 66

Location: capital of beer

  • Send private message

2

Wednesday, December 19th 2007, 5:22pm

Hi,

I have Etch and my bluetooth worked out of the box. Have you had a look at the kbluetoothrc file? Every KDE programme has an rc file in which basic parameters are configured... - just a thought
running on Debian Etch

3

Wednesday, December 19th 2007, 6:36pm

kbluetoothrc doesn't seem to contain anything useful. Only some gui settings.

edit:
I search through files in ~/.kde/share/ and /etc/kde3 with grep but none of them seems to contain "/usr/local/var/run/"

edit:

it appears that also gnome-applet thinks it is at /usr/local/var/run ... there is something wrong now...

edit:
Solved!

I must have had bluez-utils compiled because after purging everything bluetooth related and dbus. I manage to get it to work! I also searched through system for bluetooth related stuff and it appeared that I had something installed in totally wrong place indicating incorrect install.

This post has been edited 4 times, last edit by "Hoxzer" (Dec 20th 2007, 1:37pm)