aballen@monster ~ $ gnome-obex-server ** (gnome-obex-server:30929): WARNING **: OBEX server register error: -1 ** (gnome-obex-server:30929): WARNING **: Unable to initialize OBEX source ** (gnome-obex-server:30929): WARNING **: Couldn't initialise OBEX listener aballen@monster ~ $
there is not enough information for me to even guess what is wrong. please provide more relevent information such as version numbers, ways to reproduce, hardware, kernel, emerge info, etc.
monster ~ # emerge -V Portage 2.0.50-r11 (default-x86-2004.0, gcc-3.4.2, glibc-2.3.4.20040808-r0, 2.6.8.1) monster ~ # emerge -p gnome-bluetooth These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild R ] net-wireless/gnome-bluetooth-0.5.1 monster ~ # uname -a Linux monster 2.6.8.1 #2 SMP Fri Sep 10 23:20:31 EDT 2004 i686 Intel(R) Pentium(R) 4 CPU 3.00GHz GenuineIntel GNU/Linux
what about things like openobex, libbtctl, bluez-libs bluez-utils, etc.
monster ~ # emerge -p openobex libbtctl bluez-libs bluez-utils These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild R ] dev-libs/openobex-1.0.1 [ebuild R ] net-wireless/libbtctl-0.4.1 [ebuild R ] net-wireless/bluez-libs-2.10 [ebuild U ] net-wireless/bluez-utils-2.10-r1 [2.10]
has it worked before with other kernels? do you have the correct kernel modules loaded? if you have the modules loaded, do they detect your bluetooth dongle or device? have you started hcid and sdpd through /etc/init.d/bluetooth? you need to provide more information than just cut and paste from your terminal.
yes, I have /etc/init.d/bluetooth on my default runlevel, here is the output from hcitool aballen@monster ~ $ hcitool scan Scanning ... 00:0A:D9:7E:1C:89 Aristotles Phone It finds my phone just fine, In fact all of the KDE bluetooth stuff works great , however I prefer gnome, and none of the gnome bluetooth tools seem to want to work.
here is some additional info from hci tool, showing an info query on my phone monster ~ # hcitool info 00:0A:D9:7E:1C:89 Requesting information ... BD Address: 00:0A:D9:7E:1C:89 LMP Version: 1.1 (0x1) LMP Subversion: 0x400 Manufacturer: Ericsson Technology Licensing (0) Features: 0x04 0xca 0x31 0x00 0x00 0x00 0x00 0x00 <encryption> <RSSI> <SCO link> <u-law log> <A-law log> <CVSD> seems to be working fine
here is some more info from sdptool, so i think sdpd is working fine too aballen@monster ~ $ sdptool browse Inquiring ... Browsing 00:0A:D9:7E:1C:89 ... Service Name: Dial-up Networking Service RecHandle: 0x10000 Service Class ID List: "Dialup Networking" (0x1103) "Generic Networking" (0x1201) Protocol Descriptor List: "L2CAP" (0x0100) "RFCOMM" (0x0003) Channel: 1 Profile Descriptor List: "Dialup Networking" (0x1103) Version: 0x0100 Service Name: Voice gateway Service RecHandle: 0x10002 Service Class ID List: "Headset Audio Gateway" (0x1112) "Generic Audio" (0x1203) Protocol Descriptor List: "L2CAP" (0x0100) "RFCOMM" (0x0003) Channel: 3 Profile Descriptor List: "Headset" (0x1108) Version: 0x0100 Service Name: Serial Port 1 Service RecHandle: 0x10003 Service Class ID List: "Serial Port" (0x1101) Protocol Descriptor List: "L2CAP" (0x0100) "RFCOMM" (0x0003) Channel: 4 Service Name: Serial Port 2 Service RecHandle: 0x10004 Service Class ID List: "Serial Port" (0x1101) Protocol Descriptor List: "L2CAP" (0x0100) "RFCOMM" (0x0003) Channel: 5 Service Name: OBEX Object Push Service RecHandle: 0x10005 Service Class ID List: "OBEX Object Push" (0x1105) Protocol Descriptor List: "L2CAP" (0x0100) "RFCOMM" (0x0003) Channel: 10 "OBEX" (0x0008) Profile Descriptor List: "OBEX Object Push" (0x1105) Version: 0x0100 Service Name: IrMC Synchronization Service RecHandle: 0x10006 Service Class ID List: "IrMCSync" (0x1104) Protocol Descriptor List: "L2CAP" (0x0100) "RFCOMM" (0x0003) Channel: 11 "OBEX" (0x0008) Profile Descriptor List: "IrMCSync" (0x1104) Version: 0x0100 Service Name: HF Voice gateway Service RecHandle: 0x10007 Service Class ID List: "" (0x111f) "Generic Audio" (0x1203) Protocol Descriptor List: "L2CAP" (0x0100) "RFCOMM" (0x0003) Channel: 6 Profile Descriptor List: "" (0x111e) Version: 0x0100 Service Name: OBEX Basic Imaging Service RecHandle: 0x1000b Service Class ID List: "" (0x111b) Protocol Descriptor List: "L2CAP" (0x0100) "RFCOMM" (0x0003) Channel: 15 "OBEX" (0x0008) Profile Descriptor List: "" (0x111a) Version: 0x0100 Service Name: OBEX File Transfer Service RecHandle: 0x1000f Service Class ID List: "OBEX File Transfer" (0x1106) Protocol Descriptor List: "L2CAP" (0x0100) "RFCOMM" (0x0003) Channel: 7 "OBEX" (0x0008) Profile Descriptor List: "OBEX File Transfer" (0x1106) Version: 0x0100
This is very simple. Another application is listening as OBEX object push service. That's why gnome-obex-server cannot allocate connection.
no further response. has always worked for me, i believe the previous comment might be the solution. make sure nothing else is running as an obex server.
