| View previous topic :: View next topic |
| Author |
Message |
bawig1
n00b
Joined: 03 Aug 2011
Posts: 68
Location: Melbourne, Australia
|
 Posted: Sat May 05, 2012 9:49 am Post subject: KDE - BlueDevil and bluez not working.[Solved] |
 |
|
Hi Everyone,
I have just installed KDE after a fresh install this week and everything was working fine. When I booted into KDE BlueDevil came up as it detected my logitech bluetooth mouse (M555b). Everything was sweet and the bluetooth mouse has just stopped working and so has BlueDevil. I have tried using bluez but I just get error messages. The following is taken from my dmesg;
| Code: |
[ 599.383007] Bluetooth: hci0 corrupted ACL packet
[ 599.383038] Bluetooth: hci0 ACL packet for unknown connection handle 185
[ 627.751535] Bluetooth: hci0 corrupted ACL packet
[ 627.751570] Bluetooth: hci0 ACL packet for unknown connection handle 12
[ 638.886250] Bluetooth: hci0 corrupted ACL packet
[ 638.886271] Bluetooth: hci0 ACL packet for unknown connection handle 11
[ 638.886276] Bluetooth: Frame is too long (len 8, expected len 5)
[ 649.231694] Bluetooth: hci0 corrupted ACL packet
[ 649.231714] Bluetooth: hci0 ACL packet for unknown connection handle 12
[ 660.563418] Bluetooth: hci0 corrupted ACL packet
[ 660.563434] Bluetooth: hci0 ACL packet for unknown connection handle 11
[ 660.563439] Bluetooth: Frame is too long (len 8, expected len 5)
[ 669.644532] Bluetooth: hci0 corrupted ACL packet
[ 669.644548] Bluetooth: hci0 ACL packet for unknown connection handle 12
[ 687.891184] Bluetooth: hci0 corrupted ACL packet
[ 687.891214] Bluetooth: hci0 ACL packet for unknown connection handle 11
[ 687.891219] Bluetooth: Frame is too long (len 8, expected len 5)
[ 739.884746] Bluetooth: hci0 corrupted ACL packet
[ 739.884768] Bluetooth: Frame is too short (len 1)
[ 799.311728] Bluetooth: hci0 ACL packet for unknown connection handle 16
[ 1915.277412] Bluetooth: hci0 ACL packet for unknown connection handle 185
[ 1920.376184] Bluetooth: hci0 corrupted ACL packet
[ 1934.505845] Bluetooth: hci0 corrupted ACL packet
[ 1934.505869] Bluetooth: hci0 ACL packet for unknown connection handle 12
[ 2159.927747] wlan0: deauthenticated from 1c:aa:07:17:db:23 (Reason: 1)
[ 2159.966204] cfg80211: Calling CRDA to update world regulatory domain
[ 2161.046252] wlan0: authenticate with 1c:aa:07:17:db:23 (try 1)
[ 2161.047795] wlan0: authenticated
[ 2161.047821] wlan0: associate with 1c:aa:07:17:db:23 (try 1)
[ 2161.051580] wlan0: RX AssocResp from 1c:aa:07:17:db:23 (capab=0x421 status=0 aid=3)
[ 2161.051585] wlan0: associated
[ 2321.231878] Bluetooth: hci0 corrupted ACL packet
[ 2321.231899] Bluetooth: hci0 ACL packet for unknown connection handle 11
[ 2321.231905] Bluetooth: Frame is too long (len 8, expected len 5)
[ 2395.461838] Bluetooth: hci0 corrupted ACL packet
[ 2395.461855] Bluetooth: hci0 ACL packet for unknown connection handle 12
|
I have tried to stop and restart bluetooth in /etc/init.d but this has no effect. I tried running the BlueDevil command on the command line as both a normal user and root. as root is spits out the following;
| Code: | tux bawig1 # bluedevil-monolithic
bluedevilmonolithic(15946): KUniqueApplication: Cannot find the D-Bus session server: "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken."
bluedevilmonolithic(15945): KUniqueApplication: Pipe closed unexpectedly.
|
but as a normal user it just fails to start. I can post the output of the bluez commands if required. Nothing seems to work. 
edit: below is the output of trying to use hcitool and bluez;
| Code: | tux bluetooth # hcitool scan
Scanning ...
00:1F:20:14:1E:11 Logitech Bluetooth Mouse M555b
tux bluetooth # hcitool inq
Inquiring ...
00:1F:20:14:1E:11 clock offset: 0x002b class: 0x002580
tux bluetooth # l2ping 00:1F:20:14:1E:11
Ping: 00:1F:20:14:1E:11 from 18:F4:6A:FD:AA:76 (data size 44) ...
Recv failed: Software caused connection abort
tux bluetooth # hcitool scan
Scanning ...
00:1F:20:14:1E:11 Logitech Bluetooth Mouse M555b
tux bluetooth # simple-agent hci0 00:1F:20:14:1E:11
RequestPinCode (/org/bluez/2576/hci0/dev_00_1F_20_14_1E_11)
Enter PIN Code: 0000
Release
Creating device failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
tux bluetooth # bluez-test-device trusted 00:1F:20:14:1E:11
Traceback (most recent call last):
File "/usr/bin/bluez-test-device", line 158, in <module>
path = adapter.FindDevice(args[1])
File "/usr/lib64/python2.7/site-packages/dbus/proxies.py", line 70, in __call__
return self._proxy_method(*args, **keywords)
File "/usr/lib64/python2.7/site-packages/dbus/proxies.py", line 145, in __call__
**keywords)
File "/usr/lib64/python2.7/site-packages/dbus/connection.py", line 651, in call_blocking
message, timeout)
dbus.exceptions.DBusException: org.bluez.Error.DoesNotExist: Does Not Exist
tux bluetooth # bluez-test-input connect 00:1F:20:14:1E:11
Traceback (most recent call last):
File "/usr/bin/bluez-test-input", line 35, in <module>
device = adapter.FindDevice(args[1])
File "/usr/lib64/python2.7/site-packages/dbus/proxies.py", line 70, in __call__
return self._proxy_method(*args, **keywords)
File "/usr/lib64/python2.7/site-packages/dbus/proxies.py", line 145, in __call__
**keywords)
File "/usr/lib64/python2.7/site-packages/dbus/connection.py", line 651, in call_blocking
message, timeout)
dbus.exceptions.DBusException: org.bluez.Error.DoesNotExist: Does Not Exist
|
|
|
| Back to top |
|
 |
bawig1
n00b
Joined: 03 Aug 2011
Posts: 68
Location: Melbourne, Australia
|
| Posted: Sat May 05, 2012 1:11 pm Post subject: |
|
|
Well Everything is back to normal. My mouse is working fine. All I did first was remove acpid from runlevel default. I stopped the service first just to test it out, then removed it from the runlevel and rebooted and bluedevil works and the mouse works. Now I am left wondering, what do I need acpid for?
It seems the problem is that there is a conflict somewhere between acpid and bluetooth I think. I could be wrong. Would more enlightened minds like to comment on this? |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Desktop Environments
