LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Software (https://www.linuxquestions.org/questions/linux-software-2/)
-   -   Can't pair PC with mobile using bluetooth, suspecting dbus problem. (https://www.linuxquestions.org/questions/linux-software-2/cant-pair-pc-with-mobile-using-bluetooth-suspecting-dbus-problem-536611/)

kummiliim 03-11-2007 03:24 PM

Can't pair PC with mobile using bluetooth, suspecting dbus problem.
 
I already whined a little in this thread but I originally made the thread for a different problem, also this doesn't seem to be slackware specific.

So my objective is to get bluetooth working between my Slackware 11.0 and my SonyEricsson W810i so I could sync my contacts, todos and appointments between SonyEricsson and Kontact. So far I've reached a point where my USB bluetooth dongle works, I can ping my phone, I can even use obex push but I can't pair the phone with pc which seems to be needed by KMobileTools. So here's what I've done so far and what doesn't work.

I downloaded and compiled from source the following programs in that order:

dbus-1.0.2
bluez-libs-3.9
bluez-utils-3.9
openobex-1.3
kdebluetooth-1.0_beta2
kmobiletools-0.5_beta1

So far so good. So I started configuring stuff. First I activated my dongle with
Code:

hciconfig hci0 up
Listed all available devices with
Code:

hcitool scan
Changed /etc/bluetooth/hcid.conf and /etc/bluetooth/rfcomm.conf and made a little script in the same directory called pin.sh that is executable and outputs PIN:0000 as echo, referenced it from hcid.conf as pin_helper and though that all was ready. I could ping my phone, I could bind it with rfcomm, I could see it's services with sdp or from kde with KBluetooth, I could acess Obexpush from there too.

I couldn't connect to my phone with rfcomm connect or hcitool cc nor access any other services (All these resulted in the phone wanting to pair, I could enter pin from phone but nothing happened in pc and pairing timed out). I also couldn't pair with KDE Pairing Wizard. It found my phone but when looking for available services it froze and had to be killed.

So i started testing stuff and found out that when running hcid with option -n that should keep it from forking and running in backround, I get the error
Code:

hcid[2226]: Bluetooth HCI daemon
hcid[2226]: Enabling debug information
hcid[2226]: Can't connect to system message bus: Failed to connect to socket /usr/local/var/run/dbus/system_bus_socket: No such file or directory
hcid[2226]: Unable to get on D-Bus

Only similar case I could find was this.

Is it even possible that dbus is the problem here or is there something else. I would be really grateful if someone could at least lead me in the right direction. I'm getting pretty tired already and I'm not sure I included everything in this post that was necessary, if you need to know more about something feel free to ask.

almatic 03-12-2007 09:31 AM

what's the output of hciconfig ?

kummiliim 03-12-2007 01:24 PM

I'm not in linux right now but it listed the dongle (hci0) it's MAC address and all the options (all of them I've tried to change without any gain: auth, encrypt, secmgr, pscan and iscan as I remember it). If needed I'll check for sure in a few.

almatic 03-12-2007 02:13 PM

Quote:

Originally Posted by kummiliim
all of them I've tried to change without any gain: auth, encrypt, secmgr, pscan and iscan as I remember it

that's why I was asking for it. I had a similar problem which was caused by hcid consistently ignoring some options in the hcid.conf. I had to add them manually every time before pairing something. Older versions of bluez worked fine, so I downgraded which fixed my problem.

However, since you have already verified that, your problem is obviously not related to mine.

kummiliim 03-13-2007 12:14 PM

Thanks for trying anyway. Which of these options are necessary for pairing then?

almatic 03-13-2007 02:23 PM

Hi,

I paired in the other direction, I connected from the phone to bluez and for that you need pscan and iscan enabled. Those would be ignored from hcid.conf. After I added them manually they would randomly be removed again when bluez made inquiries for other devices. That's why I downgraded.

I have no idea what causes your problem, sorry. Maybe you can narrow down the problem by checking your syslog for other error messages of hcid.

Try cat /var/log/syslog | grep hcid. If everything is fine, then it's very likely that dbus is the problem. Maybe reinstalling dbus helps.

kummiliim 03-14-2007 10:58 AM

The log was clean. If I try to pair with the PC with only pscan and iscan then the phone looks for the PC forever until I kill the connection. If I enable auth it times out instead. I've reinstalled dbus and all the other components including Slackware itself too many times already. I guess I'll try older versions of things then.
God I need some sleep, I have to get it running by Friday though. Seriously, if you have any idea what to try, even if you don't have a clue about anything, still post it. I'm pretty much willing to try everything now.

kummiliim 03-18-2007 04:14 PM

It can't be dbus problem. Only logical things to blame are the dongle or my own stupidity.

I took a clean old IBM computer, installed slack 11 on it. Compiled a custom 2.6.16.43 kernel. Then I installed dbus 1.0.2, bluez-libs 3.9 and bluez-utils 3.9. That's the point where all should work as I've gotten to understand it but no, everything's the same. I can scan and see the mobile. I just can't pair with it. It's starting to drive me a little crazy. Is there some very important installation step that I'm missing or what?

The dongle actually can't be the problem since IT WORKS but I just can't pair. Has to be my own fault somehow, just don't understand what I'm doig wrong.

almatic 03-18-2007 04:32 PM

Quote:

Originally Posted by kummiliim
made a little script in the same directory called pin.sh that is executable and outputs PIN:0000 as echo, referenced it from hcid.conf as pin_helper

ok, just out of curiousity I have tried this now (I normally use kbluepin as pinhelper) and it works flawlessly, except for one detail. The line "pin_helper" is not accepted in my version (3.7.1), I have to register the pin helper manually via the passkey-agent binary. Like this:

passkey-agent --default /etc/bluetooth/pin.sh

Maybe try this and see if this has any impact. If not maybe do a test install of another distribution and see if it works there. If not try another dongle and make sure that your dongle is actually not the problem.

I myself have 2 epox dongles and 1 msi class 1 dongle and the same phone as you, all works perfect including kmobiletools.

kummiliim 03-19-2007 04:08 AM

Now that you mention it, I think I remember that in some point I saw "pin_helper not reconized" or the like somewhere. Will try right now...

edit: Actually, what is this "passkey-agent". If it's some program then I didn't get it with bluez libs nor utils. Or sould it go to the hcid.conf?

Oh one more thing almatic. If everything works for you, could you try restarting hcid with
Code:

hcid -ndsf /etc/bluetooth/hcid.conf
or wherever your config is and show the output. If you get similar dbus error that way then I'll know for sure that that's not the problem.

My output:
Code:

root@SERVER:/etc/bluetooth# hcid -ndsf /etc/bluetooth/hcid.conf
hcid[2182]: Bluetooth HCI daemon
hcid[2182]: Enabling debug information
hcid[2182]: Unknown option 'pin_helper' line 25
hcid[2182]: syntax error line 25
hcid[2182]: Can't connect to system message bus: Failed to connect to socket /usr/local/var/run/dbus/system_bus_socket: No such file or directory
hcid[2182]: Unable to get on D-Bus

edit2: Found passkey agent from bluez-utils source directory, didn't seem to get installed anywhere. Will try...

edit3:
Code:

root@SERVER:/usr/src/bluez-utils-3.9/daemon# passkey-agent --default /etc/bluetooth/pin.sh
-bash: passkey-agent: command not found

It surely had to get installed somewhere but slocate only finds:
Code:

root@SERVER:/usr/src/bluez-utils-3.9/daemon# slocate passkey-agent
/usr/src/bluez-utils-3.9/daemon/passkey-agent.c
/usr/src/bluez-utils-3.9/daemon/.deps/passkey-agent.Po
/usr/src/bluez-utils-3.9/daemon/passkey-agent.o
/usr/src/bluez-utils-3.9/daemon/passkey-agent

(I used updatedb, yes)

Otherwise it seems, that this really is the problem. Googling for passkey-agent I found some similar pairing problems that all started working after using it. So now I only have to find it :rolleyes: .

kummiliim 03-20-2007 05:01 AM

Finally got the passkey-agent executed but it didn't help. I was almost sure that this was the problem, don't know what to try anymore.

Actually I just realized that lsusb lists the dongle as "Broadcom corp." But it's A-link. I thought that A-Link adapters are made by Broadcom or something, if that isn't so then that might be the problem. I'm going to try to figure that out now.

edit: I just noticed that passkay-agent gave the error: "Can't get on system bus". That's still dbus, no?

kummiliim 03-21-2007 12:24 PM

I'm really sorry for the constant bumping but I'm really a bit desperate. Could anyone try the buetooth setup on their system using only the exact same software as I? I would really like to know what that all is about.

arunjr 03-23-2007 09:43 AM

yeah me too on ur side... trying with a sony Ericsson k750i from past two weeks.
i didnt see any error in my syslogs.
file transfer from notebook to phone is smooth.
but when i am trying to pair, thats it.... phone ask for pin, after that no reply from notebook. :confused:
am quite tired of this. i am reading all the posts which google shows me regarding this problem. but still couldn't fix it. becoz of this i am using openSuse10.2 for connecting to internet.

kummiliim 03-23-2007 10:27 AM

Something new here. Found /usr/local/etc/rc.d/rc.messagebus and started it with
Code:

/usr/local/etc/rc.d/rc.messagebus start
Now the errors are a bit different:

hcid:
Code:

root@SERVER:~# hcid -nsd
hcid[2188]: Bluetooth HCI daemon
hcid[2188]: Enabling debug information
hcid[2188]: Could not become the primary owner of org.bluez
hcid[2188]: Unable to get on D-Bus

passkey-agent:
Code:

root@SERVER:~# /usr/src/bluez-utils-3.9/daemon/passkey-agent --default 0000
Can't register passkey agent
The name org.bluez was not provided by any .service files

I'm currently trying to understand how dbus works but I still think I did something wrong, it should work from default install.

Quote:

Originally Posted by arunjr
yeah me too on ur side... trying with a sony Ericsson k750i from past two weeks.
i didnt see any error in my syslogs.
file transfer from notebook to phone is smooth.
but when i am trying to pair, thats it.... phone ask for pin, after that no reply from notebook. :confused:
am quite tired of this. i am reading all the posts which google shows me regarding this problem. but still couldn't fix it. becoz of this i am using openSuse10.2 for connecting to internet.

Do you also get a messagebus error when running hcid -nsd or passkey-agent?

ran404 03-23-2007 04:33 PM

maybe your bluetooth settings are messed up?

try clear all the files in /var/lib/bluetooth, then restart dbus and hcid.

as far as i can tell, the /etc/bluetooth/hcid.conf becomes useless after the first run, as all persistent settings are stored under /var/lib/blueooth/[btaddr]

kummiliim 03-24-2007 05:05 AM

Quote:

Originally Posted by ran404
maybe your bluetooth settings are messed up?

try clear all the files in /var/lib/bluetooth, then restart dbus and hcid.

as far as i can tell, the /etc/bluetooth/hcid.conf becomes useless after the first run, as all persistent settings are stored under /var/lib/blueooth/[btaddr]

I've tried
Code:

hcid -f /etc/bluetooth/hcid.conf
which should force these settings to be used. I'll still try it regarding to dbus.

edit: No files in /var/lib/bluetooth

edit2: Today is probably the last day I'll be able to work with this problem. I'm going to reinstall Slackware on the box and when installing bluetooth I'll be using a different version of d-bus. Let's see if that'll work.

kummiliim 03-27-2007 11:07 AM

Alright progress.

Reinstalled everything.

After slackware came dbus. This time I used options
Code:

--localstatedir=/var
--sysconfdir=/etc

when configuring. Before that was /usr/local/var and /usr/local/etc or something. Then I installed bluez-libs and bluez-utils. Dbus works now. Hcid doesn't give any more message bus errors but I still can't pair. First of all hcid gives syntax error to pin_helper in hcid.conf and doesn't read that. Then I still couldn't install passkey-agent to use that as a pin changer. It still sits in <bluez-utils src dir>/daemon uncompiled.

Is there a way to make it work without passkey-agent, if no how do I compile it (didn't find any settings in bluez-utils config)? What is wrong with pin_helper? If I can get answers to these questions It'll probably finally work.

almatic 03-27-2007 11:40 AM

hello :)

I queried my packages and found this:

Code:

tequila:/# dpkg-query -L bluez-utils | grep passkey-agent
/usr/share/doc/bluez-utils/examples/passkey-agent.c.gz
tequila:/# dpkg-query -L kdebluetooth | grep passkey-agent
/usr/bin/passkey-agent

so you may want to try installing kdebluetooth. Though it appears quite stupid to not put this tool into blues-utils ...

kummiliim 03-27-2007 12:00 PM

Allright thanks, will try.
edit: Damn, just remembered that the computer that I'm trying to use bluetooth on doesn't have KDE : D. Is there really no other way?

almatic 03-27-2007 12:14 PM

there is no other way that I'm aware of, sorry. Also kdebluetooth seems to be the only package which contains passkey-agent (at least in debian packages, see below).

http://tinyurl.com/2ldrjz

almatic 03-27-2007 12:32 PM

I might have been too fast. I went to the /usr/share/doc/bluez-utils/examples/ directory of my bluez-utils package, where the code of passkey agent is, and it also contains a Makefile to compile that code.
Look if you find a separate Makefile for the passkey-agent in your bluez-utils source directory. The .c-file is there for a reason.

kummiliim 03-27-2007 01:27 PM

Code:

root@SERVER:/usr/src/bluez-utils-3.9/daemon# ls
Makefile    adapter.c  auth-agent*  bluetooth.conf  database.h  echo.service  manager.c  passkey-agent*  service.c  system.h
Makefile.am  adapter.h  auth-agent.c  bluetoothd*    database.o  main.c        manager.h  passkey-agent.c  service.h
Makefile.in  adapter.o  auth-agent.o  database.c      echo.c      main.o        manager.o  passkey-agent.o  service.o

That might be a little silly but I can't use the ./configure in that folder so I don't know how I'm supposed to compile it. As much as I understand configuring in the main source folder makes a makefile to ./daemon too. Make alone doesn't work.
Code:

root@SERVER:/usr/src/bluez-utils-3.9/daemon# make
make: Nothing to be done for `all'.

Also if it should prove neccesary, the Makefile in daemon
Code:

root@SERVER:/usr/src/bluez-utils-3.9/daemon# cat Makefile
# Makefile.in generated by automake 1.9.6 from Makefile.am.
# daemon/Makefile.  Generated from Makefile.in by configure.

# Copyright (C) 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002,
# 2003, 2004, 2005  Free Software Foundation, Inc.
# This Makefile.in is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
# with or without modifications, as long as this notice is preserved.

# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY, to the extent permitted by law; without
# even the implied warranty of MERCHANTABILITY or FITNESS FOR A
# PARTICULAR PURPOSE.




srcdir = .
top_srcdir = ..

pkgdatadir = $(datadir)/bluez-utils
pkglibdir = $(libdir)/bluez-utils
pkgincludedir = $(includedir)/bluez-utils
top_builddir = ..
am__cd = CDPATH="$${ZSH_VERSION+.}$(PATH_SEPARATOR)" && cd
INSTALL = /usr/bin/ginstall -c
install_sh_DATA = $(install_sh) -c -m 644
install_sh_PROGRAM = $(install_sh) -c
install_sh_SCRIPT = $(install_sh) -c
INSTALL_HEADER = $(INSTALL_DATA)
transform = $(program_transform_name)
NORMAL_INSTALL = :
PRE_INSTALL = :
POST_INSTALL = :
NORMAL_UNINSTALL = :
PRE_UNINSTALL = :
POST_UNINSTALL = :
build_triplet = i686-pc-linux-gnu
host_triplet = i686-pc-linux-gnu
#service_PROGRAMS = bluetoothd-service-echo$(EXEEXT)
noinst_PROGRAMS = bluetoothd$(EXEEXT) passkey-agent$(EXEEXT) \
        auth-agent$(EXEEXT)
am__append_1 = -lexpat
subdir = daemon
DIST_COMMON = $(srcdir)/Makefile.am $(srcdir)/Makefile.in
ACLOCAL_M4 = $(top_srcdir)/aclocal.m4
am__aclocal_m4_deps = $(top_srcdir)/acinclude.m4 \
        $(top_srcdir)/configure.in
am__configure_deps = $(am__aclocal_m4_deps) $(CONFIGURE_DEPENDENCIES) \
        $(ACLOCAL_M4)
mkinstalldirs = $(install_sh) -d
CONFIG_HEADER = $(top_builddir)/config.h
CONFIG_CLEAN_FILES =
am__installdirs = "$(DESTDIR)$(servicedir)" "$(DESTDIR)$(confdir)" \
        "$(DESTDIR)$(dbusdir)"
servicePROGRAMS_INSTALL = $(INSTALL_PROGRAM)
PROGRAMS = $(noinst_PROGRAMS) $(service_PROGRAMS)
am_auth_agent_OBJECTS = auth-agent.$(OBJEXT)
auth_agent_OBJECTS = $(am_auth_agent_OBJECTS)
auth_agent_DEPENDENCIES =
am_bluetoothd_OBJECTS = main.$(OBJEXT) manager.$(OBJEXT) \
        database.$(OBJEXT) adapter.$(OBJEXT) service.$(OBJEXT)
bluetoothd_OBJECTS = $(am_bluetoothd_OBJECTS)
am__DEPENDENCIES_1 =
bluetoothd_DEPENDENCIES = $(top_builddir)/common/libhelper.a \
        $(top_builddir)/sdpd/libsdpserver.a $(am__DEPENDENCIES_1)
am__bluetoothd_service_echo_SOURCES_DIST = echo.c
#am_bluetoothd_service_echo_OBJECTS = echo.$(OBJEXT)
bluetoothd_service_echo_OBJECTS =  \
        $(am_bluetoothd_service_echo_OBJECTS)
#bluetoothd_service_echo_DEPENDENCIES =  \
#      $(top_builddir)/common/libhelper.a
am_passkey_agent_OBJECTS = passkey-agent.$(OBJEXT)
passkey_agent_OBJECTS = $(am_passkey_agent_OBJECTS)
passkey_agent_DEPENDENCIES =
DEFAULT_INCLUDES = -I. -I$(srcdir) -I$(top_builddir)
depcomp = $(SHELL) $(top_srcdir)/depcomp
am__depfiles_maybe = depfiles
COMPILE = $(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(AM_CPPFLAGS) \
        $(CPPFLAGS) $(AM_CFLAGS) $(CFLAGS)
LTCOMPILE = $(LIBTOOL) --tag=CC --mode=compile $(CC) $(DEFS) \
        $(DEFAULT_INCLUDES) $(INCLUDES) $(AM_CPPFLAGS) $(CPPFLAGS) \
        $(AM_CFLAGS) $(CFLAGS)
CCLD = $(CC)
LINK = $(LIBTOOL) --tag=CC --mode=link $(CCLD) $(AM_CFLAGS) $(CFLAGS) \
        $(AM_LDFLAGS) $(LDFLAGS) -o $@
SOURCES = $(auth_agent_SOURCES) $(bluetoothd_SOURCES) \
        $(bluetoothd_service_echo_SOURCES) $(passkey_agent_SOURCES)
DIST_SOURCES = $(auth_agent_SOURCES) $(bluetoothd_SOURCES) \
        $(am__bluetoothd_service_echo_SOURCES_DIST) \
        $(passkey_agent_SOURCES)
am__vpath_adj_setup = srcdirstrip=`echo "$(srcdir)" | sed 's|.|.|g'`;
am__vpath_adj = case $$p in \
    $(srcdir)/*) f=`echo "$$p" | sed "s|^$$srcdirstrip/||"`;; \
    *) f=$$p;; \
  esac;
am__strip_dir = `echo $$p | sed -e 's|^.*/||'`;
confDATA_INSTALL = $(INSTALL_DATA)
dbusDATA_INSTALL = $(INSTALL_DATA)
DATA = $(conf_DATA) $(dbus_DATA)
ETAGS = etags
CTAGS = ctags
DISTFILES = $(DIST_COMMON) $(DIST_SOURCES) $(TEXINFOS) $(EXTRA_DIST)
ACLOCAL = ${SHELL} /usr/src/bluez-utils-3.9/missing --run aclocal-1.9
AMDEP_FALSE = #
AMDEP_TRUE =
AMTAR = ${SHELL} /usr/src/bluez-utils-3.9/missing --run tar
AR = ar
AUTOCONF = ${SHELL} /usr/src/bluez-utils-3.9/missing --run autoconf
AUTOHEADER = ${SHELL} /usr/src/bluez-utils-3.9/missing --run autoheader
AUTOMAKE = ${SHELL} /usr/src/bluez-utils-3.9/missing --run automake-1.9
AVCTRL_FALSE =
AVCTRL_TRUE = #
AWK = gawk
BCCMD_FALSE =
BCCMD_TRUE = #
BLUEZ_CFLAGS = -I/usr/local/include
BLUEZ_LIBS = -L/usr/local/lib -lbluetooth
CC = gcc
CCDEPMODE = depmode=gcc3
CFLAGS = -Wall -O2 -D_FORTIFY_SOURCE=2
CONFIGFILES_FALSE = #
CONFIGFILES_TRUE =
CPP = gcc -E
CPPFLAGS =
CUPS_FALSE =
CUPS_TRUE = #
CYGPATH_W = echo
DBUS_CFLAGS = -I/usr/local/include/dbus-1.0 -I/usr/local/lib/dbus-1.0/include
DBUS_GLIB_CFLAGS =
DBUS_GLIB_LIBS =
DBUS_LIBS = -L/usr/local/lib -ldbus-1
DEFS = -DHAVE_CONFIG_H
DEPDIR = .deps
DFUTOOL_FALSE =
DFUTOOL_TRUE = #
ECHO = echo
ECHOSERVICE_FALSE =
ECHOSERVICE_TRUE = #
ECHO_C =
ECHO_N = -n
ECHO_T =
EGREP = grep -E
EXEEXT =
EXPAT_FALSE = #
EXPAT_TRUE =
GLIB_CFLAGS = -I$(top_srcdir)/eglib
GLIB_FALSE =
GLIB_LIBS = $(top_builddir)/eglib/libeglib.la
GLIB_TRUE = #
HCID_FALSE = #
HCID_TRUE =
HID2HCI_FALSE = #
HID2HCI_TRUE =
HIDD_FALSE = #
HIDD_TRUE =
INITSCRIPTS_FALSE =
INITSCRIPTS_TRUE = #
INOTIFY_FALSE =
INOTIFY_TRUE = #
INPUTSERVICE_FALSE =
INPUTSERVICE_TRUE = #
INSTALL_DATA = ${INSTALL} -m 644
INSTALL_PROGRAM = ${INSTALL}
INSTALL_SCRIPT = ${INSTALL}
INSTALL_STRIP_PROGRAM = ${SHELL} $(install_sh) -c -s
LDFLAGS =
LEX = flex
LEXLIB = -lfl
LEX_OUTPUT_ROOT = lex.yy
LIBOBJS =
LIBS =
LIBTOOL = $(SHELL) $(top_builddir)/libtool
LN_S = ln -s
LTLIBOBJS =
MAINT = #
MAINTAINER_MODE_FALSE =
MAINTAINER_MODE_TRUE = #
MAKEINFO = ${SHELL} /usr/src/bluez-utils-3.9/missing --run makeinfo
OBEX_FALSE =
OBEX_TRUE = #
OBJEXT = o
OPENOBEX_CFLAGS =
OPENOBEX_LIBS =
OPENSYNC_CFLAGS =
OPENSYNC_LIBS =
PACKAGE = bluez-utils
PACKAGE_BUGREPORT =
PACKAGE_NAME =
PACKAGE_STRING =
PACKAGE_TARNAME =
PACKAGE_VERSION =
PATH_SEPARATOR = :
PCMCIARULES_FALSE =
PCMCIARULES_TRUE = #
PKG_CONFIG = /usr/bin/pkg-config
RANLIB = ranlib
SDPD_FALSE = #
SDPD_TRUE =
SED = /usr/bin/sed
SET_MAKE =
SHELL = /bin/sh
STRIP = strip
SYNCSERVICE_FALSE =
SYNCSERVICE_TRUE = #
TEST_FALSE =
TEST_TRUE = #
USB_CFLAGS =
USB_FALSE = #
USB_LIBS = -lusb
USB_TRUE =
VERSION = 3.9
YACC = bison -y
ac_ct_AR = ar
ac_ct_CC = gcc
ac_ct_RANLIB = ranlib
ac_ct_STRIP = strip
ac_pt_PKG_CONFIG = /usr/bin/pkg-config
am__fastdepCC_FALSE = #
am__fastdepCC_TRUE =
am__include = include
am__leading_dot = .
am__quote =
am__tar = ${AMTAR} chof - "$$tardir"
am__untar = ${AMTAR} xf -
bindir = ${exec_prefix}/bin
build = i686-pc-linux-gnu
build_alias =
build_cpu = i686
build_os = linux-gnu
build_vendor = pc
datadir = ${prefix}/share
exec_prefix = ${prefix}
host = i686-pc-linux-gnu
host_alias =
host_cpu = i686
host_os = linux-gnu
host_vendor = pc
includedir = ${prefix}/include
infodir = ${prefix}/info
install_sh = /usr/src/bluez-utils-3.9/install-sh
libdir = /usr/local/lib
libexecdir = /lib
localstatedir = /var
mandir = ${prefix}/share/man
mkdir_p = mkdir -p --
oldincludedir = /usr/include
prefix = /usr/local
program_transform_name = s,x,x,
sbindir = ${exec_prefix}/sbin
sharedstatedir = ${prefix}/com
sysconfdir = /etc
target_alias =
#confdir = $(sysconfdir)/bluetooth
#conf_DATA = echo.service
#servicedir = $(libdir)/bluetooth
#bluetoothd_service_echo_SOURCES = echo.c
#bluetoothd_service_echo_LDADD = \
#      $(top_builddir)/common/libhelper.a \
#      $(top_builddir)/eglib/libeglib.la -L/usr/local/lib -ldbus-1  -L/usr/local/lib -lbluetooth

dbusdir = $(sysconfdir)/dbus-1/system.d
dbus_DATA = bluetooth.conf
bluetoothd_SOURCES = main.c system.h \
        manager.h manager.c database.h database.c \
        adapter.h adapter.c service.h service.c

bluetoothd_LDADD = $(top_builddir)/common/libhelper.a \
        $(top_builddir)/sdpd/libsdpserver.a $(top_builddir)/eglib/libeglib.la -L/usr/local/lib -ldbus-1  \
        -L/usr/local/lib -lbluetooth  $(am__append_1)
passkey_agent_SOURCES = passkey-agent.c
passkey_agent_LDADD = -L/usr/local/lib -ldbus-1
auth_agent_SOURCES = auth-agent.c
auth_agent_LDADD = -L/usr/local/lib -ldbus-1
AM_CFLAGS = -I/usr/local/include  -I/usr/local/include/dbus-1.0 -I/usr/local/lib/dbus-1.0/include  -I$(top_srcdir)/eglib
INCLUDES = -I$(top_srcdir)/common -I$(top_srcdir)/sdpd
EXTRA_DIST = bluetooth.conf echo.service
MAINTAINERCLEANFILES = Makefile.in
all: all-am

.SUFFIXES:
.SUFFIXES: .c .lo .o .obj
$(srcdir)/Makefile.in: # $(srcdir)/Makefile.am  $(am__configure_deps)
        @for dep in $?; do \
          case '$(am__configure_deps)' in \
            *$$dep*) \
              cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh \
                && exit 0; \
              exit 1;; \
          esac; \
        done; \
        echo ' cd $(top_srcdir) && $(AUTOMAKE) --gnu  daemon/Makefile'; \
        cd $(top_srcdir) && \
          $(AUTOMAKE) --gnu  daemon/Makefile
.PRECIOUS: Makefile
Makefile: $(srcdir)/Makefile.in $(top_builddir)/config.status
        @case '$?' in \
          *config.status*) \
            cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh;; \
          *) \
            echo ' cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@ $(am__depfiles_maybe)'; \
            cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@ $(am__depfiles_maybe);; \
        esac;

$(top_builddir)/config.status: $(top_srcdir)/configure $(CONFIG_STATUS_DEPENDENCIES)
        cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh

$(top_srcdir)/configure: # $(am__configure_deps)
        cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh
$(ACLOCAL_M4): # $(am__aclocal_m4_deps)
        cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh

clean-noinstPROGRAMS:
        @list='$(noinst_PROGRAMS)'; for p in $$list; do \
          f=`echo $$p|sed 's/$(EXEEXT)$$//'`; \
          echo " rm -f $$p $$f"; \
          rm -f $$p $$f ; \
        done
install-servicePROGRAMS: $(service_PROGRAMS)
        @$(NORMAL_INSTALL)
        test -z "$(servicedir)" || $(mkdir_p) "$(DESTDIR)$(servicedir)"
        @list='$(service_PROGRAMS)'; for p in $$list; do \
          p1=`echo $$p|sed 's/$(EXEEXT)$$//'`; \
          if test -f $$p \
            || test -f $$p1 \
          ; then \
            f=`echo "$$p1" | sed 's,^.*/,,;$(transform);s/$$/$(EXEEXT)/'`; \
          echo " $(INSTALL_PROGRAM_ENV) $(LIBTOOL) --mode=install $(servicePROGRAMS_INSTALL) '$$p' '$(DESTDIR)$(servicedir)/$$f'"; \
          $(INSTALL_PROGRAM_ENV) $(LIBTOOL) --mode=install $(servicePROGRAMS_INSTALL) "$$p" "$(DESTDIR)$(servicedir)/$$f" || exit 1; \
          else :; fi; \
        done

uninstall-servicePROGRAMS:
        @$(NORMAL_UNINSTALL)
        @list='$(service_PROGRAMS)'; for p in $$list; do \
          f=`echo "$$p" | sed 's,^.*/,,;s/$(EXEEXT)$$//;$(transform);s/$$/$(EXEEXT)/'`; \
          echo " rm -f '$(DESTDIR)$(servicedir)/$$f'"; \
          rm -f "$(DESTDIR)$(servicedir)/$$f"; \
        done

clean-servicePROGRAMS:
        @list='$(service_PROGRAMS)'; for p in $$list; do \
          f=`echo $$p|sed 's/$(EXEEXT)$$//'`; \
          echo " rm -f $$p $$f"; \
          rm -f $$p $$f ; \
        done
auth-agent$(EXEEXT): $(auth_agent_OBJECTS) $(auth_agent_DEPENDENCIES)
        @rm -f auth-agent$(EXEEXT)
        $(LINK) $(auth_agent_LDFLAGS) $(auth_agent_OBJECTS) $(auth_agent_LDADD) $(LIBS)
bluetoothd$(EXEEXT): $(bluetoothd_OBJECTS) $(bluetoothd_DEPENDENCIES)
        @rm -f bluetoothd$(EXEEXT)
        $(LINK) $(bluetoothd_LDFLAGS) $(bluetoothd_OBJECTS) $(bluetoothd_LDADD) $(LIBS)
bluetoothd-service-echo$(EXEEXT): $(bluetoothd_service_echo_OBJECTS) $(bluetoothd_service_echo_DEPENDENCIES)
        @rm -f bluetoothd-service-echo$(EXEEXT)
        $(LINK) $(bluetoothd_service_echo_LDFLAGS) $(bluetoothd_service_echo_OBJECTS) $(bluetoothd_service_echo_LDADD) $(LIBS)
passkey-agent$(EXEEXT): $(passkey_agent_OBJECTS) $(passkey_agent_DEPENDENCIES)
        @rm -f passkey-agent$(EXEEXT)
        $(LINK) $(passkey_agent_LDFLAGS) $(passkey_agent_OBJECTS) $(passkey_agent_LDADD) $(LIBS)

mostlyclean-compile:
        -rm -f *.$(OBJEXT)

distclean-compile:
        -rm -f *.tab.c

include ./$(DEPDIR)/adapter.Po
include ./$(DEPDIR)/auth-agent.Po
include ./$(DEPDIR)/database.Po
include ./$(DEPDIR)/echo.Po
include ./$(DEPDIR)/main.Po
include ./$(DEPDIR)/manager.Po
include ./$(DEPDIR)/passkey-agent.Po
include ./$(DEPDIR)/service.Po

.c.o:
        if $(COMPILE) -MT $@ -MD -MP -MF "$(DEPDIR)/$*.Tpo" -c -o $@ $<; \
        then mv -f "$(DEPDIR)/$*.Tpo" "$(DEPDIR)/$*.Po"; else rm -f "$(DEPDIR)/$*.Tpo"; exit 1; fi
#      source='$<' object='$@' libtool=no \
#      DEPDIR=$(DEPDIR) $(CCDEPMODE) $(depcomp) \
#      $(COMPILE) -c $<

.c.obj:
        if $(COMPILE) -MT $@ -MD -MP -MF "$(DEPDIR)/$*.Tpo" -c -o $@ `$(CYGPATH_W) '$<'`; \
        then mv -f "$(DEPDIR)/$*.Tpo" "$(DEPDIR)/$*.Po"; else rm -f "$(DEPDIR)/$*.Tpo"; exit 1; fi
#      source='$<' object='$@' libtool=no \
#      DEPDIR=$(DEPDIR) $(CCDEPMODE) $(depcomp) \
#      $(COMPILE) -c `$(CYGPATH_W) '$<'`

.c.lo:
        if $(LTCOMPILE) -MT $@ -MD -MP -MF "$(DEPDIR)/$*.Tpo" -c -o $@ $<; \
        then mv -f "$(DEPDIR)/$*.Tpo" "$(DEPDIR)/$*.Plo"; else rm -f "$(DEPDIR)/$*.Tpo"; exit 1; fi
#      source='$<' object='$@' libtool=yes \
#      DEPDIR=$(DEPDIR) $(CCDEPMODE) $(depcomp) \
#      $(LTCOMPILE) -c -o $@ $<

mostlyclean-libtool:
        -rm -f *.lo

clean-libtool:
        -rm -rf .libs _libs

distclean-libtool:
        -rm -f libtool
uninstall-info-am:
install-confDATA: $(conf_DATA)
        @$(NORMAL_INSTALL)
        test -z "$(confdir)" || $(mkdir_p) "$(DESTDIR)$(confdir)"
        @list='$(conf_DATA)'; for p in $$list; do \
          if test -f "$$p"; then d=; else d="$(srcdir)/"; fi; \
          f=$(am__strip_dir) \
          echo " $(confDATA_INSTALL) '$$d$$p' '$(DESTDIR)$(confdir)/$$f'"; \
          $(confDATA_INSTALL) "$$d$$p" "$(DESTDIR)$(confdir)/$$f"; \
        done

uninstall-confDATA:
        @$(NORMAL_UNINSTALL)
        @list='$(conf_DATA)'; for p in $$list; do \
          f=$(am__strip_dir) \
          echo " rm -f '$(DESTDIR)$(confdir)/$$f'"; \
          rm -f "$(DESTDIR)$(confdir)/$$f"; \
        done
install-dbusDATA: $(dbus_DATA)
        @$(NORMAL_INSTALL)
        test -z "$(dbusdir)" || $(mkdir_p) "$(DESTDIR)$(dbusdir)"
        @list='$(dbus_DATA)'; for p in $$list; do \
          if test -f "$$p"; then d=; else d="$(srcdir)/"; fi; \
          f=$(am__strip_dir) \
          echo " $(dbusDATA_INSTALL) '$$d$$p' '$(DESTDIR)$(dbusdir)/$$f'"; \
          $(dbusDATA_INSTALL) "$$d$$p" "$(DESTDIR)$(dbusdir)/$$f"; \
        done

uninstall-dbusDATA:
        @$(NORMAL_UNINSTALL)
        @list='$(dbus_DATA)'; for p in $$list; do \
          f=$(am__strip_dir) \
          echo " rm -f '$(DESTDIR)$(dbusdir)/$$f'"; \
          rm -f "$(DESTDIR)$(dbusdir)/$$f"; \
        done

ID: $(HEADERS) $(SOURCES) $(LISP) $(TAGS_FILES)
        list='$(SOURCES) $(HEADERS) $(LISP) $(TAGS_FILES)'; \
        unique=`for i in $$list; do \
            if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
          done | \
          $(AWK) '    { files[$$0] = 1; } \
              END { for (i in files) print i; }'`; \
        mkid -fID $$unique
tags: TAGS

TAGS:  $(HEADERS) $(SOURCES)  $(TAGS_DEPENDENCIES) \
                $(TAGS_FILES) $(LISP)
        tags=; \
        here=`pwd`; \
        list='$(SOURCES) $(HEADERS)  $(LISP) $(TAGS_FILES)'; \
        unique=`for i in $$list; do \
            if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
          done | \
          $(AWK) '    { files[$$0] = 1; } \
              END { for (i in files) print i; }'`; \
        if test -z "$(ETAGS_ARGS)$$tags$$unique"; then :; else \
          test -n "$$unique" || unique=$$empty_fix; \
          $(ETAGS) $(ETAGSFLAGS) $(AM_ETAGSFLAGS) $(ETAGS_ARGS) \
            $$tags $$unique; \
        fi
ctags: CTAGS
CTAGS:  $(HEADERS) $(SOURCES)  $(TAGS_DEPENDENCIES) \
                $(TAGS_FILES) $(LISP)
        tags=; \
        here=`pwd`; \
        list='$(SOURCES) $(HEADERS)  $(LISP) $(TAGS_FILES)'; \
        unique=`for i in $$list; do \
            if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
          done | \
          $(AWK) '    { files[$$0] = 1; } \
              END { for (i in files) print i; }'`; \
        test -z "$(CTAGS_ARGS)$$tags$$unique" \
          || $(CTAGS) $(CTAGSFLAGS) $(AM_CTAGSFLAGS) $(CTAGS_ARGS) \
            $$tags $$unique

GTAGS:
        here=`$(am__cd) $(top_builddir) && pwd` \
          && cd $(top_srcdir) \
          && gtags -i $(GTAGS_ARGS) $$here

distclean-tags:
        -rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags

distdir: $(DISTFILES)
        @srcdirstrip=`echo "$(srcdir)" | sed 's|.|.|g'`; \
        topsrcdirstrip=`echo "$(top_srcdir)" | sed 's|.|.|g'`; \
        list='$(DISTFILES)'; for file in $$list; do \
          case $$file in \
            $(srcdir)/*) file=`echo "$$file" | sed "s|^$$srcdirstrip/||"`;; \
            $(top_srcdir)/*) file=`echo "$$file" | sed "s|^$$topsrcdirstrip/|$(top_builddir)/|"`;; \
          esac; \
          if test -f $$file || test -d $$file; then d=.; else d=$(srcdir); fi; \
          dir=`echo "$$file" | sed -e 's,/[^/]*$$,,'`; \
          if test "$$dir" != "$$file" && test "$$dir" != "."; then \
            dir="/$$dir"; \
            $(mkdir_p) "$(distdir)$$dir"; \
          else \
            dir=''; \
          fi; \
          if test -d $$d/$$file; then \
            if test -d $(srcdir)/$$file && test $$d != $(srcdir); then \
              cp -pR $(srcdir)/$$file $(distdir)$$dir || exit 1; \
            fi; \
            cp -pR $$d/$$file $(distdir)$$dir || exit 1; \
          else \
            test -f $(distdir)/$$file \
            || cp -p $$d/$$file $(distdir)/$$file \
            || exit 1; \
          fi; \
        done
check-am: all-am
check: check-am
all-am: Makefile $(PROGRAMS) $(DATA)
installdirs:
        for dir in "$(DESTDIR)$(servicedir)" "$(DESTDIR)$(confdir)" "$(DESTDIR)$(dbusdir)"; do \
          test -z "$$dir" || $(mkdir_p) "$$dir"; \
        done
install: install-am
install-exec: install-exec-am
install-data: install-data-am
uninstall: uninstall-am

install-am: all-am
        @$(MAKE) $(AM_MAKEFLAGS) install-exec-am install-data-am

installcheck: installcheck-am
install-strip:
        $(MAKE) $(AM_MAKEFLAGS) INSTALL_PROGRAM="$(INSTALL_STRIP_PROGRAM)" \
          install_sh_PROGRAM="$(INSTALL_STRIP_PROGRAM)" INSTALL_STRIP_FLAG=-s \
          `test -z '$(STRIP)' || \
            echo "INSTALL_PROGRAM_ENV=STRIPPROG='$(STRIP)'"` install
mostlyclean-generic:

clean-generic:

distclean-generic:
        -test -z "$(CONFIG_CLEAN_FILES)" || rm -f $(CONFIG_CLEAN_FILES)

maintainer-clean-generic:
        @echo "This command is intended for maintainers to use"
        @echo "it deletes files that may require special tools to rebuild."
        -test -z "$(MAINTAINERCLEANFILES)" || rm -f $(MAINTAINERCLEANFILES)
clean: clean-am

clean-am: clean-generic clean-libtool clean-noinstPROGRAMS \
        clean-servicePROGRAMS mostlyclean-am

distclean: distclean-am
        -rm -rf ./$(DEPDIR)
        -rm -f Makefile
distclean-am: clean-am distclean-compile distclean-generic \
        distclean-libtool distclean-tags

dvi: dvi-am

dvi-am:

html: html-am

info: info-am

info-am:

install-data-am: install-confDATA install-dbusDATA \
        install-servicePROGRAMS

install-exec-am:

install-info: install-info-am

install-man:

installcheck-am:

maintainer-clean: maintainer-clean-am
        -rm -rf ./$(DEPDIR)
        -rm -f Makefile
maintainer-clean-am: distclean-am maintainer-clean-generic

mostlyclean: mostlyclean-am

mostlyclean-am: mostlyclean-compile mostlyclean-generic \
        mostlyclean-libtool

pdf: pdf-am

pdf-am:

ps: ps-am

ps-am:

uninstall-am: uninstall-confDATA uninstall-dbusDATA uninstall-info-am \
        uninstall-servicePROGRAMS

.PHONY: CTAGS GTAGS all all-am check check-am clean clean-generic \
        clean-libtool clean-noinstPROGRAMS clean-servicePROGRAMS ctags \
        distclean distclean-compile distclean-generic \
        distclean-libtool distclean-tags distdir dvi dvi-am html \
        html-am info info-am install install-am install-confDATA \
        install-data install-data-am install-dbusDATA install-exec \
        install-exec-am install-info install-info-am install-man \
        install-servicePROGRAMS install-strip installcheck \
        installcheck-am installdirs maintainer-clean \
        maintainer-clean-generic mostlyclean mostlyclean-compile \
        mostlyclean-generic mostlyclean-libtool pdf pdf-am ps ps-am \
        tags uninstall uninstall-am uninstall-confDATA \
        uninstall-dbusDATA uninstall-info-am uninstall-servicePROGRAMS

# Tell versions [3.59,3.63) of GNU make to not export all variables.
# Otherwise a system limit (for SysV at least) may be exceeded.
.NOEXPORT:

I'm rather new to linux :cool:

kummiliim 03-27-2007 01:31 PM

edit:
Quote:

Originally Posted by kummiliim
As much as I understand configuring in the main source folder makes a makefile to ./daemon too.

And it does:
Code:

root@SERVER:/usr/src/bluez-utils-3.9# ./configure | grep daemon
config.status: creating daemon/Makefile

edit2: Damn, accidental double-post. No way to delete here, is there?

almatic 03-27-2007 02:26 PM

there is already a binary in the directory you listed.

passkey-agent*

Copy that to /usr/bin

kummiliim 03-27-2007 02:31 PM

Yeah, I tried it earlier, but that one gave error as before:
Code:

root@SERVER:/usr/src/bluez-utils-3.9# /usr/src/bluez-utils-3.9/daemon/passkey-agent --default 0000
Can't register passkey agent
The name org.bluez was not provided by any .service files

Figured it was because it was uncompiled.
Should copying it to /usr/bin change anything? It basically just makes it a shortcut then, doesn't it?
Well trying anyway...
edit: And didn't change anything.

almatic 03-27-2007 02:54 PM

Quote:

Originally Posted by kummiliim
Figured it was because it was uncompiled.

no, it compiled correctly, this is the right file. I don't think this error has something to do with the passkey-agent file.
I suppose that it either needs some service, which is not installed (kdebluetoothd ?) or it's (again) a dbus problem.
I don't know it though ...

kummiliim 03-27-2007 02:57 PM

Thanks for your help nevertheless. D-bus does seem to be okay now. I'll deal with it tomorrow. Glad I made even that much progress today.

almatic 03-27-2007 03:16 PM

there is a file 'bluetoothd' in the same directory. Can you try to start thtat service and then again register the passkey agent. I cannot try because I don't seem to have bluetoothd ...

kummiliim 03-28-2007 10:15 AM

After starting bluetoothd with
Code:

root@SERVER:~# /usr/src/bluez-utils-3.9/daemon/bluetoothd start
the error has changed to:
Code:

root@SERVER:~# /usr/src/bluez-utils-3.9/daemon/passkey-agent --default 0000
Can't register passkey agent
Method "RegisterDefaultPasskeyAgent" with signature "s" on interface "org.bluez.Security" doesn't exist

I don't have much time to fool around with it now but I'll check it in couple of hours when I get home.

almatic 03-28-2007 12:13 PM

make sure that bluetoothd can parse its config-file (bluetooth.conf). Look if bluetoothd -h (or --help) gives you info, or look for a manpage for bluetoothd. Also take a look at bluetooth.conf. If you cannot find any info on bluetoothd, just try something like this:

/usr/src/bluez-utils-3.9/daemon/bluetoothd /usr/src/bluez-utils3.9/daemon/bluetooth.conf

kummiliim 03-28-2007 01:09 PM

Unfortunately didn't work out.

bluetoothd has following options:
Code:

root@SERVER:/usr/src/bluez-utils-3.9/daemon# /usr/src/bluez-utils-3.9/daemon/bluetoothd --help
bluetoothd - Bluetooth daemon ver 3.9

Usage:
        bluetoothd [options]

Options:
        --help        Display help
        --debug      Enable debug information
        --nodaemon    Run daemon in foreground

Code:

root@SERVER:/usr/src/bluez-utils-3.9/daemon# /usr/src/bluez-utils-3.9/daemon/bluetoothd --debug --nodaemon
bluetoothd[2179]: Bluetooth daemon ver 3.9
bluetoothd[2179]: Enabling debug information
bluetoothd[2179]: Could not become the primary owner of org.bluez

and
Code:

root@SERVER:/usr/src/bluez-utils-3.9/daemon# man -k bluetooth
bluetooth: nothing appropriate

also
Code:

root@SERVER:/usr/src/bluez-utils-3.9/daemon# /usr/src/bluez-utils-3.9/daemon/bluetoothd /usr/src/bluez-utils-3.9/daemon/bluetooth.conf
That just run it without any difference. passkey-agent still gives the same error.

I'll see what else I can try.

almatic 03-28-2007 02:16 PM

I guess you have already tried the option 'passkey "0000";' in the hcid.conf. This was default in my hcid.conf. This is my hcid.conf.

Code:

options {
        autoinit yes;
        security user;
        pairing multi;
        # passkey "1234";
}
device {
        name "tequila";
        class 0x100100;
        iscan enable; pscan enable;
        lm accept;
        lp hold,sniff,park;
        discovto 0;
}

If this also doesn't work I'd recommend that you subscribe to the bluez-users mailinglist and ask there, how pairing is supposed to work with no desktop environment installed.
I'm running out of ideas.

kummiliim 03-28-2007 02:22 PM

Yeah, my hcid is basically identical to yours:
Code:

root@SERVER:~# cat /etc/bluetooth/hcid.conf
#
# HCI daemon configuration file.
#

# HCId options
options {
        # Automatically initialize new devices
        autoinit yes;

        # Security Manager mode
        #  none - Security manager disabled
        #  auto - Use local PIN for incoming connections
        #  user - Always ask user for a PIN
        #
        security user;

        # Pairing mode
        #  none  - Pairing disabled
        #  multi - Allow pairing with already paired devices
        #  once  - Pair once and deny successive attempts
        pairing multi;

        # Default PIN code for incoming connections
        passkey "0000";
        #pin_helper /etc/bluetooth/pin.sh
}

# Default settings for HCI devices
device {
        # Local device name
        #  %d - device id
        #  %h - host name
        name "SERVER";

        # Local device class
        class 0x3e0100;

        # Default packet type
        #pkt_type DH1,DM1,HV1;

        # Inquiry and Page scan
        iscan enable; pscan enable;

        # Default link mode
        #  none  - no specific policy
        #  accept - always accept incoming connections
        #  master - become master on incoming connections,
        #            deny role switch on outgoing connections
        lm accept;

        # Default link policy
        #  none    - no specific policy
        #  rswitch - allow role switch
        #  hold    - allow hold mode
        #  sniff  - allow sniff mode
        #  park    - allow park mode
        lp rswitch,hold,sniff,park;
}

I'll try some more random stuff and then turn to the mailing list. Thanks a lot for all your help. Seriously appreciated.

edit: Also desktopless isn't really a problem. All was same on the other computer with kde installed. It's eighter some incompability in current slackware/kernel/bluez or I'm doing something very wrong.

kummiliim 04-06-2007 08:55 AM

It's been 6 days now without a response from the mailing list, so I figured I'll go for another bump. More specifically, I was comparing my actions with drkstr's howto. It might be a little outdated but I was wondering about the existance of rc.bluetooth. I didn't have anything like that in my system. From where exactly is it installed and is it also necessary in the current bluez version?

Also, when I get a little free time today or in couple of next days, I'll do a full system reinstall again documenting every single thing I do. Hopefully someone will have a little time to look over it and see, if anything's wrong there. Maybe even better, try to duplicate the problem.

kummiliim 04-21-2007 04:56 PM

So here goes, every single step:

I make sata.i, install.1, install.2 and network.dsk disks on this desktop computer, all downloaded from the local linux ftp and up to date.

Reboot server, insert disk, slack starts booting. I don't give any boot options just press enter, also through the two install disks. When I can finally log in as root, I do that and run
Code:

fdisk /dev/hda
I check the partition table with
Code:

p
and since I don't want to change anything, I leave it like that and use
Code:

w
to write the table.

It's as follows:
primary partitions:
hda1- /- 1GB
hda2- extended- 9GB
rest are logical inside hda2
hda5- swap- 512MB
hda6- /usr- 3GB
hda7- /home- 5.5GB

then I start configuring network since I'm going to use NFS install:
Code:

network
enter,enter and it finds eepro100
so
Code:

setup
I choose the keyboard layout, format hda5 as swap, hda1 as /, hda6 as /usr and /hda7 as /home
start installing from NFS
all the slackware packages are on this desktop computer, checked to be up to date
I select everything exept KDE related stuff, X window things and games.
Installs...
I use the 2.4.33.3 kernel from bootdisk, configure lilo to boot from /dev/hda1, disable most services exept ssh, CUPS, and some defaults, change root's password and complete the install, I don't remember if there was anything more intresting, I guess not.
So I reboot and take the monitor and keyboard back to my desktop computer. The server now runs only with power, network and printer connections + bluetooth dongle.

I ssh to server from my computer:

first, new kernel.
Code:

root@SERVER:~#wget ftp://ftp.kernel.org/pub/linux/kernel/v2.6/linux-2.6.20.7.tar.gz
root@SERVER:~# mkdir /usr/src/tar
root@SERVER:~# mv linux-2.6.20.7.tar.gz /usr/src/tar
root@SERVER:~# cd /usr/src/tar
root@SERVER:/usr/src/tar# tar -xzf linux-2.6.20.7.tar.gz
root@SERVER:/usr/src/tar# mv linux-2.6.20.7 ..
root@SERVER:/usr/src/tar# cd ..
root@SERVER:/usr/src# rm linux
root@SERVER:/usr/src# ln -s linux-2.6.20.7/ linux
root@SERVER:/usr/src# cd linux

I'm using the config from the previous install. I can't codequote it here, cause the message is too long to post then, if needed I'll post it later in two posts.

Code:

make oldconfig
make menuconfig

just to check that it's correct

good to go:
I modify lilo.conf to use old kernel too
Code:

root@SERVER:/usr/src/linux# cat /etc/lilo.conf
# Start LILO global section
boot = /dev/hda
prompt
timeout = 5
vga = normal
# End LILO global section

# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/hda1
label = Slack-2.6.20.7
read-only
# Linux bootable partition config ends

# Linux bootable partition config begins
image = /boot/vmlinuz.old
root = /dev/hda1
label = Slack-2.4.33.3
read-only
# Linux bootable partition config ends

Code:

make
make modules_install
make install

I fix all the links and stuff in /boot
Code:

root@SERVER:/boot# ls -l
total 4592
lrwxrwxrwx 1 root root      37 2007-04-21 20:36 README.initrd -> /usr/doc/mkinitrd-1.0.1/README.initrd
lrwxrwxrwx 1 root root      23 2007-04-21 21:23 System.map -> System.map-ide-2.6.20.7
-rw-r--r-- 1 root root  629105 2006-09-01 09:51 System.map-ide-2.4.33.3
-rw-r--r-- 1 root root  764029 2007-04-21 21:20 System.map-ide-2.6.20.7
lrwxrwxrwx 1 root root      23 2007-04-21 21:24 System.old -> System.map-ide-2.4.33.3
-rw-r--r-- 1 root root    512 2007-04-21 21:02 boot.0300
lrwxrwxrwx 1 root root      19 2007-04-21 21:24 config -> config-ide-2.6.20.7
-rw-r--r-- 1 root root  41810 2006-09-01 09:51 config-ide-2.4.33.3
-rw-r--r-- 1 root root  34939 2007-04-21 21:23 config-ide-2.6.20.7
lrwxrwxrwx 1 root root      19 2007-04-21 21:24 config.old -> config-ide-2.4.33.3
-rw-r--r-- 1 root root    5032 2006-08-08 08:34 diag1.img
-rw------- 1 root root  51712 2007-04-21 21:20 map
lrwxrwxrwx 1 root root      20 2007-04-21 21:24 vmlinuz -> vmlinuz-ide-2.6.20.7
-rw-r--r-- 1 root root 1313255 2006-09-01 09:51 vmlinuz-ide-2.4.33.3
-rw-r--r-- 1 root root 1818824 2007-04-21 21:20 vmlinuz-ide-2.6.20.7
lrwxrwxrwx 1 root root      20 2007-04-21 21:24 vmlinuz.old -> vmlinuz-ide-2.4.33.3

and reboot.
Code:

root@SERVER:/boot# reboot

Broadcast message from root (pts/0) (Sat Apr 21 21:28:39 2007):

The system is going down for reboot NOW!
root@SERVER:/boot# Connection to 192.168.1.2 closed by remote host.
Connection to 192.168.1.2 closed.
sander@SANDER:~$ ssh root@192.168.1.2
root@192.168.1.2's password:
Last login: Sat Apr 21 19:08:43 2007 from 192.168.1.3
Linux 2.6.20.7.
root@SERVER:~#

beautiful. So now the not so pretty part, I'll install bluez.

I use lynx to get latest dbus, bluez-utils and bluez-libs from their respective sites. That's dbus-1.0.2, bluez-libs-3.9 and bluez-utils-3.9. Alrighty:
Code:

root@SERVER:~# ls *.tar.gz
bluez-libs-3.9.tar.gz  bluez-utils-3.9.tar.gz  dbus-1.0.2.tar.gz
root@SERVER:~# mv *.tar.gz /usr/src/tar
root@SERVER:~# cd /usr/src/tar
root@SERVER:/usr/src/tar# tar -xzf dbus-1.0.2.tar.gz
root@SERVER:/usr/src/tar# tar -xzf bluez-libs-3.9.tar.gz
root@SERVER:/usr/src/tar# tar -xzf bluez-utils-3.9.tar.gz
root@SERVER:/usr/src/tar# mv dbus-1.0.2 ..
root@SERVER:/usr/src/tar# mv bluez-libs-3.9 ..
root@SERVER:/usr/src/tar# mv bluez-utils-3.9 ..
root@SERVER:/usr/src/tar# cd ../dbus-1.0.2/
root@SERVER:/usr/src/dbus-1.0.2#

I won't post all the ./configure,make and make install output but what I did was
Code:

./configure --prefix=/usr --localstatedir=/var --sysconfdir=/etc

       
Code:

       
D-Bus 1.0.2
                  ==============

        prefix:                   /usr
        exec_prefix:              ${prefix}
        libdir:                   /usr/lib
        bindir:                   /usr/bin
        sysconfdir:               /etc
        localstatedir:            /var
        datadir:                  /usr/share
        source code location:     .
        compiler:                 gcc
        cflags:                   -g -O2 -Wall -Wchar-subscripts -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wcast-align -Wfloat-equal -Wsign-compare -Wdeclaration-after-statement -fno-common -fPIC
        cppflags:
        cxxflags:                 -g -O2
        64-bit int:               long long
        32-bit int:               int
        16-bit int:               short
        Doxygen:                  /usr/bin/doxygen
        xmlto:                    no

        Maintainer mode:          no
        gcc coverage profiling:   no
        Building unit tests:      no
        Building verbose mode:    no
        Building assertions:      no
        Building checks:          yes
        Building SELinux support: no
        Building dnotify support: yes
        Building X11 code:        no
        Building Doxygen docs:    yes
        Building XML docs:        no
        Gettext libs (empty OK):
        Using XML parser:         expat
        Init scripts style:       slackware
        Abstract socket names:    yes
        System bus socket:        /var/run/dbus/system_bus_socket
        System bus address:       unix:path=/var/run/dbus/system_bus_socket
        System bus PID file:      /var/run/dbus/pid
        Session bus socket dir:   /tmp
        Console auth dir:         /var/run/console/
        Console owner file:       no
        Console owner file path:
        System bus user:          messagebus
        Session bus services dir: /usr/share/dbus-1/services
        'make check' socket dir:  /tmp


make
make install
ldconfig

next, bluez libraries:
Code:

root@SERVER:/usr/src/dbus-1.0.2# cd ../bluez-libs-3.9/
./configure --prefix=/usr
make
make install
ldconfig

and finally
Code:

root@SERVER:/usr/src/bluez-libs-3.9# cd ../bluez-utils-3.9/
./configure --prefix=/usr --mandir=/usr/share/man  --sysconfdir=/etc --localstatedir=/var --libexecdir=/lib
make
make install
ldconfig
updatedb

Done, let's get to it:

I configure hcid.conf like this:
Code:

root@SERVER:/etc/bluetooth# cat /etc/bluetooth/hcid.conf
#
# HCI daemon configuration file.
#

# HCId options
options {
        # Automatically initialize new devices
        autoinit yes;

        # Security Manager mode
        #  none - Security manager disabled
        #  auto - Use local PIN for incoming connections
        #  user - Always ask user for a PIN
        #
        security auto;

        # Pairing mode
        #  none  - Pairing disabled
        #  multi - Allow pairing with already paired devices
        #  once  - Pair once and deny successive attempts
        pairing multi;

        # Default PIN code for incoming connections
        passkey "2486";
}

# Default settings for HCI devices
device {
        # Local device name
        #  %d - device id
        #  %h - host name
        name "SERVER";

        # Local device class
        class 0x3e0100;

        # Default packet type
        #pkt_type DH1,DM1,HV1;

        # Inquiry and Page scan
        iscan enable; pscan enable;

        # Default link mode
        #  none  - no specific policy
        #  accept - always accept incoming connections
        #  master - become master on incoming connections,
        #            deny role switch on outgoing connections
        lm accept;

        # Default link policy
        #  none    - no specific policy
        #  rswitch - allow role switch
        #  hold    - allow hold mode
        #  sniff  - allow sniff mode
        #  park    - allow park mode
        lp rswitch,hold,sniff,park;
}

I'm really not sure of this step but I create a "messagebus" user for dbus with adduser
Code:

adduser messagebus
enter to everything else
I also give all rights of /var/run/dbus to it
Code:

root@SERVER:~# chown messagebus:users /var/run/dbus
root@SERVER:~# chmod u+rwx /var/run/dbus

No idea if that's even used.
so let's bring up the dongle
Code:

root@SERVER:~# hciconfig hci0 up
root@SERVER:~# hciconfig
hci0:  Type: USB
        BD Address: 00:02:72:02:27:63 ACL MTU: 1017:8 SCO MTU: 64:0
        UP RUNNING
        RX bytes:79 acl:0 sco:0 events:8 errors:0
        TX bytes:30 acl:0 sco:0 commands:8 errors:0

All the extra stuff isn't enabled for some reason so:
Code:

root@SERVER:~# hciconfig hci0 piscan auth secmgr encrypt
root@SERVER:~# hciconfig
hci0:  Type: USB
        BD Address: 00:02:72:02:27:63 ACL MTU: 1017:8 SCO MTU: 64:0
        UP RUNNING PSCAN ISCAN AUTH ENCRYPT SECMGR
        RX bytes:97 acl:0 sco:0 events:11 errors:0
        TX bytes:42 acl:0 sco:0 commands:11 errors:0

Looks better.
I use my cell now to look for available bluetooth devices. It finds BCM2045. Ah right, forgot to restart hcid:
Code:

hcid -f /etc/bluetooth/hcid.conf
Checking again with the cell. Still the same name. Oh yeah, I had to start dbus and stuff before. For checking I run:
Code:

root@SERVER:~# hcid -nsd
hcid[6314]: Bluetooth HCI daemon
hcid[6314]: Enabling debug information
hcid[6314]: Can't connect to system message bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
hcid[6314]: Unable to get on D-Bus

Yeah, that's it.
Code:

root@SERVER:~# /etc/rc.d/rc.messagebus start
Starting system message bus
root@SERVER:~# hcid -nsd
hcid[6320]: Bluetooth HCI daemon
hcid[6320]: Enabling debug information
hcid[6320]: HCI dev 0 registered
hcid[6320]: HCI dev 0 already up
hcid[6320]: Device hci0 has been added
hcid[6320]: Starting security manager 0
hcid[6320]: Device hci0 has been activated
hcid[6320]: Starting SDP server
hcid[6320]: Adding rec : 0x807e9e0
hcid[6320]: with handle : 0x1
hcid[6320]: Adding rec : 0x807ec68
hcid[6320]: with handle : 0x0

Way better. I repeat the
Code:

hcid -f /etc/bluetooth/hcid.conf
Third time is the charm, retrying with the cell. Oh great, now it doesn't find anything. Something's messed up.
Code:

root@SERVER:~# hcitool scan
Scanning ...
        00:16:B8:23:A8:51      W810i

hmm.
Code:

root@SERVER:~# hciconfig hci0 down
root@SERVER:~# hciconfig
hci0:  Type: USB
        BD Address: 00:02:72:02:27:63 ACL MTU: 1017:8 SCO MTU: 64:0
        DOWN
        RX bytes:1149 acl:0 sco:0 events:42 errors:0
        TX bytes:640 acl:0 sco:0 commands:32 errors:0

root@SERVER:~# hciconfig hci0 up
root@SERVER:~# hciconfig
hci0:  Type: USB
        BD Address: 00:02:72:02:27:63 ACL MTU: 1017:8 SCO MTU: 64:0
        UP RUNNING PSCAN
        RX bytes:1547 acl:0 sco:0 events:59 errors:0
        TX bytes:957 acl:0 sco:0 commands:49 errors:0

root@SERVER:~# hciconfig hci0 piscan secmgr auth encrypt
root@SERVER:~# hciconfig
hci0:  Type: USB
        BD Address: 00:02:72:02:27:63 ACL MTU: 1017:8 SCO MTU: 64:0
        UP RUNNING PSCAN ISCAN AUTH ENCRYPT SECMGR
        RX bytes:1572 acl:0 sco:0 events:63 errors:0
        TX bytes:972 acl:0 sco:0 commands:53 errors:0

Fourth time with the cell and it finds SERVER. Delicious.
Just for kicks I try to pair from cell once. The cell waits for about half a minute and asks to enter the pin. I enter 2486 as in hcid.conf, cell waits for another half a minute and reports pairing failed. Sounds familiar.

So what's next, let's mess with passkey agent a little.
Code:

root@SERVER:~# slocate passkey
/usr/src/bluez-utils-3.9/daemon/passkey-agent.c
/usr/src/bluez-utils-3.9/daemon/.deps/passkey-agent.Po
/usr/src/bluez-utils-3.9/daemon/passkey-agent.o
/usr/src/bluez-utils-3.9/daemon/passkey-agent
root@SERVER:~# cd /usr/src/bluez-utils-3.9/daemon/

so first
Code:

root@SERVER:/usr/src/bluez-utils-3.9/daemon# /usr/src/bluez-utils-3.9/daemon/passkey-agent --default 2486
Weird, it just stays running. That didn't happen before. Anyway now the cell can't find PC anymore.
Code:

root@SERVER:/usr/src/bluez-utils-3.9/daemon# hciconfig hci0 down;hciconfig hci0 up piscan auth encrypt secmgr
root@SERVER:/usr/src/bluez-utils-3.9/daemon# hciconfig
hci0:  Type: USB
        BD Address: 00:02:72:02:27:63 ACL MTU: 1017:8 SCO MTU: 64:0
        UP RUNNING PSCAN AUTH ENCRYPT SECMGR
        RX bytes:2100 acl:0 sco:0 events:96 errors:0
        TX bytes:1334 acl:0 sco:0 commands:79 errors:0

Didn't fix it, now I'm worried.
Code:

root@SERVER:/usr/src/bluez-utils-3.9/daemon# hcid -nsd
hcid[6372]: Bluetooth HCI daemon
hcid[6372]: Enabling debug information
hcid[6372]: Could not become the primary owner of org.bluez
hcid[6372]: Unable to get on D-Bus

Hmm, is it because it's already using dbus or is something wrong with it.
Code:

root@SERVER:/usr/src/bluez-utils-3.9/daemon# /etc/rc.d/rc.messagebus restart
Stopping system message bus
Starting system message bus
Failed to start message bus: The pid file "/var/run/dbus/pid" exists, if the message bus is not running, remove this file

Yah, forgot
Wait it isn't there. It had to delete it itself somehow, whatever.
Code:

root@SERVER:/usr/src/bluez-utils-3.9/daemon# /etc/rc.d/rc.messagebus restart
Stopping system message bus
dbus-daemon: no process killed
Starting system message bus

And only after
Code:

root@SERVER:/usr/src/bluez-utils-3.9/daemon# hcid -nsdf /etc/bluetooth/hcid.conf
hcid[6394]: Bluetooth HCI daemon
hcid[6394]: Enabling debug information
hcid[6394]: HCI dev 0 registered
hcid[6394]: HCI dev 0 already up
hcid[6394]: Device hci0 has been added
hcid[6394]: Starting security manager 0
hcid[6394]: Device hci0 has been activated
hcid[6394]: Starting SDP server
hcid[6394]: Adding rec : 0x807a290
hcid[6394]: with handle : 0x1
hcid[6394]: Adding rec : 0x807ec60
hcid[6394]: with handle : 0x0
hcid[6394]: Stopping SDP server
hcid[6394]: release_services
hcid[6394]: Unregister path: /org/bluez/hci0
hcid[6394]: Unregister path: /org/bluez
hcid[6394]: Exit
root@SERVER:/usr/src/bluez-utils-3.9/daemon# hciconfig hci0 down;hciconfig hci0 up piscan auth encrypt secmgr

the cell can see the pc again.
Whew, that was fun, why not try that again:
Code:

root@SERVER:/usr/src/bluez-utils-3.9/daemon# /usr/src/bluez-utils-3.9/daemon/passkey-agent --default 2486
Can't register passkey agent
The name org.bluez was not provided by any .service files

Hmm, that I remember. Wonder what made it remain working the previous time.
Code:

root@SERVER:/usr/src/bluez-utils-3.9/daemon# /usr/src/bluez-utils-3.9/daemon/bluetoothd --debug --nodaemon
bluetoothd[6408]: Bluetooth daemon ver 3.9
bluetoothd[6408]: Enabling debug information
bluetoothd[6408]: Could not become the primary owner of org.bluez

And that I remember too.
Code:

root@SERVER:/usr/src/bluez-utils-3.9/daemon# /usr/src/bluez-utils-3.9/daemon/passkey-agent --default 2486
Can't register passkey agent
Method "RegisterDefaultPasskeyAgent" with signature "s" on interface "org.bluez.Security" doesn't exist

Been there, haven't got out yet.

I lurk around the system for some time and find
Code:

root@SERVER:~# cat /etc/dbus-1/system.d/bluetooth.conf
<!-- This configuration file specifies the required security policies
    for Bluetooth core service to work. -->

<!DOCTYPE busconfig PUBLIC "-//freedesktop//DTD D-BUS Bus Configuration 1.0//EN"
 "http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd">
<busconfig>

  <!-- ../system.conf have denied everything, so we just punch some holes -->

  <policy user="root">
    <allow own="org.bluez"/>
  </policy>

  <policy at_console="true">
    <allow send_destination="org.bluez.Manager"/>
    <allow receive_sender="org.bluez.Manager"/>

    <allow send_path="/org/bluez"/>

    <allow send_destination="org.bluez.Adapter"/>
    <allow receive_sender="org.bluez.Adapter"/>

    <allow send_destination="org.bluez.Service"/>
    <allow receive_sender="org.bluez.Service"/>

    <allow send_destination="org.bluez.Database"/>
    <allow receive_sender="org.bluez.Database"/>

    <allow send_destination="org.bluez.Security"/>
    <allow receive_sender="org.bluez.Security"/>
  </policy>

</busconfig>

It has cool words like org.bluez and security in it, other then that I have no idea how it works. By now I'm also having serious trouble keeping my eyes open and I'm out of coffee. To be continued tomorrow...

almatic 04-21-2007 05:20 PM

this is some long posting :eek:

I didn't see anything wrong in your steps, at least nothing obvious. However, instead of doing the same over and over again I'd suggest changing something, so you at least come closer to what the problem is.
Did you notice that slackware-current uses bluez 3.8 ? Maybe try their packages for a change (for dbus also) if you can't get forward anymore.
http://slackware-current.net/package.php?id=196

kummiliim 04-22-2007 02:00 AM

That actually sounds pretty reasonable. Before I try though, a question about uninstalling. If I go to /usr/src/<src> and do
Code:

make uninstall
Does it really remove all traces of program from the system, or should I delete something manually?
I intend to start using slackware package management system soon when I finally have the time to understand how to make packages from source. Until then, I want to make sure I don't leave any garbage on my system.

zdavid 05-03-2007 04:54 PM

I had the very same problem (uid/gid) and passkey-agent missing,
but I manage to solve it !!!

add this to /etc/passwd
messagebus:x:81:81:User for D-BUS:/var/run/dbus:/bin/false
and add to /etc/group
messagebus:x:81:

from slackware-current download dbus, bluez-packages and do ./slackbuild
you will found packages in /tmp
#installpgk /tmp/*.tgz

now you should have dbus and all bluez packages installed:

then do
#sh /etc//rc.d/rc.messagebus start

then in some console do
#hcid -ndsf /etc/bluetooth/hcid.conf

You will see:
--------------------------------------
hcid[2404]: Bluetooth HCI daemon
hcid[2404]: Enabling debug information
hcid[2404]: HCI dev 0 registered
hcid[2404]: HCI dev 0 already up
hcid[2404]: Device hci0 has been added
hcid[2404]: Starting security manager 0
hcid[2404]: Device hci0 has been activated
hcid[2404]: Starting SDP server
hcid[2404]: Adding rec : 0x807a238
hcid[2404]: with handle : 0x1
hcid[2404]: Adding rec : 0x807ebc0
hcid[2404]: with handle : 0x0
hcid[2404]: binding L2CAP socket: Address already in use
hcid[2404]: Server initialization failed
hcid[2404]: pin_code_request (sba=00:02:72:D1:71:B5, dba=00:04:3E:65:9A:CA)
hcid[2404]: call_passkey_agent(): no agent available
hcid[2404]: pin_code_request (sba=00:02:72:D1:71:B5, dba=00:04:3E:65:9A:CA)
hcid[2404]: call_passkey_agent(): no agent available
------------------------------------------------------

then do
# cd /tmp/bluez-utils-3.9/daemon/
# cp passkey-agent /usr/local/sbin/
# passkey-agent --default 4321

You will see:
-------------------------------------
hcid[2404]: Default passkey agent (:1.7, /org/bluez/passkey_agent_13560) registered
hcid[2404]: pin_code_request (sba=00:02:72:D1:71:B5, dba=00:04:3E:65:9A:CA)
hcid[2404]: Calling PasskeyAgent.Request: name=:1.7, path=/org/bluez/passkey_agent_13560
hcid[2404]: link_key_notify (sba=00:02:72:D1:71:B5, dba=00:04:3E:65:9A:CA)
hcid[2404]: pin_code_request (sba=00:02:72:D1:71:B5, dba=00:1A:77:65:73:1D)
hcid[2404]: Calling PasskeyAgent.Request: name=:1.7, path=/org/bluez/passkey_agent_13560
hcid[2404]: link_key_notify (sba=00:02:72:D1:71:B5, dba=00:1A:77:65:73:1D)
hcid[2404]: link_key_request (sba=00:02:72:D1:71:B5, dba=00:1A:77:65:73:1D)
hcid[2404]: link_key_request (sba=00:02:72:D1:71:B5, dba=00:04:3E:65:9A:CA)
hcid[2404]: link_key_request (sba=00:02:72:D1:71:B5, dba=00:1A:77:65:73:1D)
hcid[2404]: link_key_request (sba=00:02:72:D1:71:B5, dba=00:1A:77:65:73:1D)
hcid[2404]: link_key_request (sba=00:02:72:D1:71:B5, dba=00:1A:77:65:73:1D)
hcid[2404]: :1.7 exited without unregistering the default passkey agent
hcid[2404]: name_listener_add(:1.8)
hcid[2404]: Default passkey agent (:1.8, /org/bluez/passkey_agent_13645) registered
hcid[2404]: name_listener_remove(:1.8)
hcid[2404]: Default passkey agent (:1.8, /org/bluez/passkey_agent_13645) unregistered
hcid[2404]: name_listener_add(:1.9)
hcid[2404]: Default passkey agent (:1.9, /org/bluez/passkey_agent_13647) registered
-----------------------------------------------------------------------------------

now everything works :)

Have fun .

kummiliim 05-06-2007 01:29 AM

Wow, thanks dude, I'm on it.

kummiliim 05-06-2007 09:05 AM

Wow it's terrible. I used Slackware packages this time.

dbus 1.0.2
bluez-libs-3.8
bluez-utils-3.8

And I can't even get the messagebus to work. rc.messagebus start says it works but it doesn't
Code:

root@SERVER:~# /etc/rc.d/rc.messagebus start
Starting system message bus:  /usr/bin/dbus-uuidgen --ensure ; /usr/bin/dbus-daemon --system
root@SERVER:~# hcid -nf /etc/bluetooth/hcid.conf
hcid[3193]: Bluetooth HCI daemon
hcid[3193]: Can't connect to system message bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
hcid[3193]: Unable to get on D-Bus

I'm looking into this but it's really making me a bit pissed now.

edit: hcid can't even use -d and -s flags. zdavid, maybe I should use the versions I used before?

zdavid 05-09-2007 03:49 PM

Quote:

Originally Posted by kummiliim
Wow it's terrible. I used Slackware packages this time.

dbus 1.0.2
bluez-libs-3.8
bluez-utils-3.8

And I can't even get the messagebus to work. rc.messagebus start says it works but it doesn't
Code:

root@SERVER:~# /etc/rc.d/rc.messagebus start
Starting system message bus:  /usr/bin/dbus-uuidgen --ensure ; /usr/bin/dbus-daemon --system
root@SERVER:~# hcid -nf /etc/bluetooth/hcid.conf
hcid[3193]: Bluetooth HCI daemon
hcid[3193]: Can't connect to system message bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
hcid[3193]: Unable to get on D-Bus

I'm looking into this but it's really making me a bit pissed now.

edit: hcid can't even use -d and -s flags. zdavid, maybe I should use the versions I used before?


again did you add ???
- /etc/passwd
messagebus:x:81:81:User for D-BUS:/var/run/dbus:/bin/false
- and add to /etc/group
messagebus:x:81:

next thing

# ps aufwx |grep `cat /var/run/dbus/dbus.pid`
81 2094 0.0 0.0 2172 772 ? Ss 20:57 0:00 /usr/bin/dbus-daemon --system

I've sent you a packages for slack 11 on your email...

kummiliim 05-10-2007 10:40 AM

I did everything as you said and I've currently got to the point where all's as before, everything works but pairing.

passkey-agent gives me
Code:

root@SERVER:~# passkey-agent --default 2486
passkey-agent: /lib/tls/libc.so.6: version `GLIBC_2.0' not found (required by passkey-agent)

So I'll try to find this glibc thing.

edit: pkgtool says I have it already.

edit2: The user was added too, yes.

kummiliim 05-24-2007 04:59 AM

Bump, could somone explain me the glibc 2.0 error, I don't get it.

kummiliim 07-19-2007 05:04 AM

Just wanted to say that I'm currently using Slackware 12.0 which has perfect bluetooth support. Thanks again.

Tijn 10-03-2007 02:53 AM

Hey people, you definitely need passkey-agent.

I have spent many hours with useless fiddling with bluez on Fedora Core 6 (FC6) but there is no passkey-agent included in the regular bluez RPM packages (utils & lib 3.7).
I had to install dev packages

Code:

# yum --enablerepo development update bluez*
# rpm -qa | grep bluez
bluez-hcidump-1.40-1.fc8
bluez-utils-cups-3.19-1.fc8
bluez-gnome-0.14-5.fc8
bluez-libs-3.19-1.fc8
bluez-utils-3.19-1.fc8

and then I did

Code:

passkey-agent --default 4321
...and voila - everything was fine.

Hope this helps someone...
Tijn

surfzoid 11-27-2007 03:08 PM

Do yu already have same problem with my CS-OBEXFTP tool
http://sourceforge.net/projects/cs-obexftp/
?


All times are GMT -5. The time now is 07:23 PM.