- flxfxp - 2009-10-21
Nothing got fragmented, just read well: http://forum.xbmc.org/showpost.php?p=415216&postcount=205
- ruff - 2009-10-21
It means d-bus subsystem can't initialize. is dbus set and running?
- flxfxp - 2009-10-21
I personally don't have that problem. I did had it in the beginning, rebooting fixed it. What should I tell people who have this problem? What can they check?
- ruff - 2009-10-21
This appears after fresh install i presume, when d-bus was installed but is not yet running. Let them try /etc/init.d/dbus restart. Or, as you said - reboot %)
- dogk1cker - 2009-10-22
hey flxfxp,
I did you patch:
http://flx.me/script/bluez-patched-4.54.tar.gz
AND IT WORKS!!!!!!!
Thanx a bunch.
dogk1cker
- folecr - 2009-10-23
flxfxp Wrote:It's just that some people have the error "Can't get on D-Bus". Any idea what this means?
I'm still trying to get my PS3 remote working correctly.
But, it looks like this error is reported when running bluetoothd -nd from the command line and :
- you are not root
- bluetoothd is already running
So, run all these commands as root. If you are running as root, and see this error, kill the bluetoothd process. Then re-run the command.
flxflp could you confirm you are running all commands as root? (It seems so...)
BTW, which file has the error log from bluetoothd when started by init.d?
- folecr - 2009-10-23
First, much thanks to everyone here!
Could someone help me debug?
- I have the custom deb from flxflp/ruff installed.
- I ran ps3_pair.py
Now, I need to confirm that my remote actually works....
Here's output from ps3_pair
Code: xbmc@xbmc:~/ws/pythong$ sudo python ps3_pair.py
Searching for devices, please wait...
Found:
1: 00:24:33:9A:9A:58 [BD Remote Control]
Select the device you wish to add [1]: 1
Registering device... Done
and hciconfig
Code: xbmc@xbmc:~/ws$ hciconfig
hci0: Type: USB
BD Address: 11:11:11:11:11:11 ACL MTU: 678:8 SCO MTU: 48:10
UP RUNNING PSCAN
RX bytes:3475 acl:11 sco:0 events:89 errors:0
TX bytes:1105 acl:11 sco:0 commands:66 errors:0
The addresses of the bd devices seem different.
Code: xbmc@xbmc:~/ws$ hcidump
HCI sniffer - Bluetooth packet analyzer ver 1.42
Can't access device: Permission denied
xbmc@xbmc:~/ws$ sudo hcidump
HCI sniffer - Bluetooth packet analyzer ver 1.42
device: hci0 snap_len: 1028 filter: 0xffffffff
(And nothing else printed after.... even if I press keys on the remote)
Is this normal?
Any other way to check?
- Amelandbor - 2009-10-24
I have the exact same problem as described above.
- ruff - 2009-10-24
folecr Wrote:BTW, which file has the error log from bluetoothd when started by init.d?
It uses syslog.
As for hcidump - seems like device is not registered properly. Try to re-run that python script or try pure blueman
- folecr - 2009-10-24
Here's some more info...
Code: xbmc@xbmc:/var/log$ cat /var/log/syslog | grep -i blue
Oct 24 12:56:15 xbmc kernel: [ 0.700009] Bluetooth: Core ver 2.13
Oct 24 12:56:15 xbmc kernel: [ 0.700020] Bluetooth: HCI device and connection manager initialized
Oct 24 12:56:15 xbmc kernel: [ 0.700020] Bluetooth: HCI socket layer initialized
Oct 24 12:56:15 xbmc kernel: [ 4.866052] Bluetooth: L2CAP ver 2.11
Oct 24 12:56:15 xbmc kernel: [ 4.866053] Bluetooth: L2CAP socket layer initialized
Oct 24 12:56:15 xbmc kernel: [ 4.866056] Bluetooth: SCO (Voice Link) ver 0.6
Oct 24 12:56:15 xbmc kernel: [ 4.866057] Bluetooth: SCO socket layer initialized
Oct 24 12:56:15 xbmc kernel: [ 4.866088] Bluetooth: RFCOMM socket layer initialized
Oct 24 12:56:15 xbmc kernel: [ 4.866093] Bluetooth: RFCOMM TTY layer initialized
Oct 24 12:56:15 xbmc kernel: [ 4.866095] Bluetooth: RFCOMM ver 1.10
Oct 24 12:56:16 xbmc kernel: [ 16.154839] Bluetooth: Generic Bluetooth USB driver ver 0.3
Oct 24 12:56:16 xbmc bluetoothd[2746]: Bluetooth daemon 4.54
Oct 24 12:56:16 xbmc bluetoothd[2749]: Starting SDP server
Oct 24 12:56:16 xbmc bluetoothd[2749]: Parsing /etc/bluetooth/network.conf failed: No such file or directory
Oct 24 12:56:16 xbmc kernel: [ 16.327908] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Oct 24 12:56:16 xbmc kernel: [ 16.327911] Bluetooth: BNEP filters: protocol multicast
Oct 24 12:56:17 xbmc bluetoothd[2749]: bridge pan0 created
Oct 24 12:56:17 xbmc bluetoothd[2749]: Parsing /etc/bluetooth/input.conf failed: No such file or directory
Oct 24 12:56:17 xbmc bluetoothd[2749]: Parsing /etc/bluetooth/audio.conf failed: No such file or directory
Oct 24 12:56:17 xbmc bluetoothd[2749]: HCI dev 0 registered
Oct 24 12:56:17 xbmc bluetoothd[2749]: Failed to open RFKILL control device
Oct 24 12:56:17 xbmc bluetoothd[2749]: HCI dev 0 up
Oct 24 12:56:17 xbmc bluetoothd[2749]: Starting security manager 0
Oct 24 12:56:17 xbmc bluetoothd[2749]: Parsing /etc/bluetooth/serial.conf failed: No such file or directory
Oct 24 12:56:17 xbmc bluetoothd[2749]: Adapter /org/bluez/2746/hci0 has been enabled
Oct 24 12:56:20 xbmc bluetoothd[3212]: Bluetooth daemon 4.54
Oct 24 12:56:20 xbmc bluetoothd[3212]: Unable to get on D-Bus
I guess I'll try blueman.
- folecr - 2009-10-24
hmmm is a Code: /etc/bluetooth/input.conf
required?
- folecr - 2009-10-24
hey ruff... thanks again for all your work here...
ruff Wrote:As for hcidump - seems like device is not registered properly.
You are probably right... and I'll try blueman.
Just FYI, listing registered devices using this quick-and-dirty script :
Code: from bluez.Manager import Manager
import glib
import sys
import os
import signal
def handler(signum, frame):
print
os._exit(1)
signal.signal(signal.SIGINT, handler)
signal.signal(signal.SIGTERM, handler)
class Main:
def __init__(self):
self.manager = Manager("gobject")
self.adapter = self.manager.GetAdapter()
print "Getting device list, please wait..."
self.devices = self.adapter.ListDevices()
print "Listing devices, please wait..."
for d in self.devices:
print "%s, %s" % (d, d.GetProperties())
Main()
shows :
Code: xbmc@xbmc:~/ws/pythong$ sudo python list_bluetooth_devices.py
Getting device list, please wait...
Listing devices, please wait...
<bluez.Device.Device object at 0x844a6ec>, dbus.Dictionary({dbus.String(u'Name'): dbus.String(u'BD Remote Control', variant_level=1), dbus.String(u'Paired'): dbus.Boolean(False, variant_level=1), dbus.String(u'Adapter'): dbus.ObjectPath('/org/bluez/2746/hci0', variant_level=1), dbus.String(u'Alias'): dbus.String(u'BD Remote Control', variant_level=1), dbus.String(u'Connected'): dbus.Boolean(False, variant_level=1), dbus.String(u'UUIDs'): dbus.Array([dbus.String(u'00001124-0000-1000-8000-00805f9b34fb'), dbus.String(u'00001200-0000-1000-8000-00805f9b34fb')], signature=dbus.Signature('s'), variant_level=1), dbus.String(u'Address'): dbus.String(u'00:24:33:9A:9A:58', variant_level=1), dbus.String(u'Class'): dbus.UInt32(9484L, variant_level=1), dbus.String(u'Trusted'): dbus.Boolean(True, variant_level=1)}, signature=dbus.Signature('sv'))
- Amelandbor - 2009-10-24
Found something concerning the unable to get on d-bus problem
Quote:Unable to get on D-Bus:
It seems (I'm not sure on this) that adding local user to the group 'lp' fixed the issue. Before that, I removed bluez and installed bluez-git from AUR and back to the default, so it's probably the latter action that fixed it.
- Amelandbor - 2009-10-25
Another site I found during the search for some answers.
Anyone seen/tested this one already??
http://code.google.com/p/bdremote-ng/
- ruff - 2009-10-25
input.conf is not mandatory, without that remote will use timeout of 15 sec (or 3 min in case of flxfxp version) and original keymap layout (with high keycodes).
Properties seems to be ok for remote in script dump %\
as for groups and stuff - it is not needed since d-bus daemon and bluetoothd should be run by root. Thus local user has nothing to do with it.
|