FS#35696 - [bluez] updates broke bluetooth
Attached to Project:
Arch Linux
Opened by peter (jqvillanova) - Friday, 07 June 2013, 18:49 GMT
Last edited by Andreas Radke (AndyRTR) - Sunday, 24 November 2013, 11:33 GMT
Opened by peter (jqvillanova) - Friday, 07 June 2013, 18:49 GMT
Last edited by Andreas Radke (AndyRTR) - Sunday, 24 November 2013, 11:33 GMT
|
Details
Description:
Here is the output of `journalctl -xu bluetooth.service' . It refuses to make any bluetooth connection. [code] Jun 07 20:32:28 arch bluetoothd[281]: Bluetooth daemon 4.101 Jun 07 20:32:30 arch bluetoothd[281]: Starting SDP server Jun 07 20:32:30 arch bluetoothd[281]: DIS cannot start: GATT is disabled Jun 07 20:32:30 arch bluetoothd[281]: Failed to init deviceinfo plugin Jun 07 20:32:30 arch bluetoothd[281]: Failed to init proximity plugin Jun 07 20:32:30 arch bluetoothd[281]: Failed to init time plugin Jun 07 20:32:30 arch bluetoothd[281]: Failed to init alert plugin Jun 07 20:32:30 arch bluetoothd[281]: Failed to init thermometer plugin Jun 07 20:32:30 arch bluetoothd[281]: Failed to init gatt_example plugin Jun 07 20:32:30 arch bluetoothd[281]: Bluetooth Management interface initialized Jun 07 20:32:31 arch bluetoothd[281]: Unknown command complete for opcode 19 Jun 07 20:32:32 arch bluetoothd[281]: Adapter /org/bluez/281/hci0 has been enabled Jun 07 20:32:32 arch bluetoothd[281]: bluetoothd[281]: Bluetooth daemon 4.101 Jun 07 20:32:32 arch bluetoothd[281]: bluetoothd[281]: Starting SDP server Jun 07 20:32:32 arch bluetoothd[281]: bluetoothd[281]: DIS cannot start: GATT is disabled Jun 07 20:32:32 arch bluetoothd[281]: bluetoothd[281]: Failed to init deviceinfo plugin Jun 07 20:32:32 arch bluetoothd[281]: bluetoothd[281]: Failed to init proximity plugin Jun 07 20:32:32 arch bluetoothd[281]: bluetoothd[281]: Failed to init time plugin Jun 07 20:32:32 arch bluetoothd[281]: bluetoothd[281]: Failed to init alert plugin Jun 07 20:32:32 arch bluetoothd[281]: bluetoothd[281]: Failed to init thermometer plugin Jun 07 20:32:32 arch bluetoothd[281]: bluetoothd[281]: Failed to init gatt_example plugin Jun 07 20:32:32 arch bluetoothd[281]: bluetoothd[281]: Bluetooth Management interface initialized Jun 07 20:32:32 arch bluetoothd[281]: bluetoothd[281]: Unknown command complete for opcode 19 Jun 07 20:32:32 arch bluetoothd[281]: bluetoothd[281]: Adapter /org/bluez/281/hci0 has been enabled Jun 07 20:33:09 arch bluetoothd[281]: bluetoothd[281]: Endpoint registered: sender=:1.30 path=/MediaEndpoint/HFPAG Jun 07 20:33:09 arch bluetoothd[281]: Endpoint registered: sender=:1.30 path=/MediaEndpoint/HFPAG Jun 07 20:33:09 arch bluetoothd[281]: Endpoint registered: sender=:1.30 path=/MediaEndpoint/HFPHS Jun 07 20:33:09 arch bluetoothd[281]: Endpoint registered: sender=:1.30 path=/MediaEndpoint/A2DPSource Jun 07 20:33:09 arch bluetoothd[281]: bluetoothd[281]: Endpoint registered: sender=:1.30 path=/MediaEndpoint/HFPHS Jun 07 20:33:09 arch bluetoothd[281]: bluetoothd[281]: Endpoint registered: sender=:1.30 path=/MediaEndpoint/A2DPSource Jun 07 20:33:42 arch bluetoothd[281]: bluetoothd[281]: Host is down (112) Jun 07 20:33:42 arch bluetoothd[281]: Host is down (112) Jun 07 20:34:15 arch bluetoothd[281]: bluetoothd[281]: Host is down (112) Jun 07 20:34:15 arch bluetoothd[281]: Host is down (112) Jun 07 20:34:24 arch bluetoothd[281]: bluetoothd[281]: Host is down (112) Jun 07 20:34:24 arch bluetoothd[281]: Host is down (112) Jun 07 20:36:51 arch systemd[1]: Started Bluetooth service. [/code] Additional info: * package version(s) * config and/or log files etc. Steps to reproduce: Connect any audio headset in gnome shell with network manager (I guess, at least not blueman) |
This task depends upon
Closed by Andreas Radke (AndyRTR)
Sunday, 24 November 2013, 11:33 GMT
Reason for closing: Won't fix
Additional comments about closing: Bleuz4 has been dropped. Please check bluez5 stack.
Sunday, 24 November 2013, 11:33 GMT
Reason for closing: Won't fix
Additional comments about closing: Bleuz4 has been dropped. Please check bluez5 stack.
then is bluez4 instead bluez(5)
and bluetooth gprs connections broken, "rc.d start bluetooth" command not work anymore.
please update packages more carefully.
| Jun 09 10:44:01 mars bluetoothd[1732]: Bluetooth daemon 4.101
| Jun 09 10:44:01 mars bluetoothd[1732]: Starting SDP server
| Jun 09 10:44:01 mars bluetoothd[1732]: Parsing /etc/bluetooth/proximity.conf failed: No such file or directory
| Jun 09 10:44:01 mars bluetoothd[1732]: Not enough free handles to register service
| Jun 09 10:44:01 mars bluetoothd[1732]: Bluetooth Management interface initialized
| Jun 09 10:44:01 mars bluetoothd[1732]: bluetoothd[1732]: Bluetooth daemon 4.101
| Jun 09 10:44:01 mars bluetoothd[1732]: bluetoothd[1732]: Starting SDP server
| Jun 09 10:44:01 mars bluetoothd[1732]: bluetoothd[1732]: Parsing /etc/bluetooth/proximity.conf failed: No such file or directory
| Jun 09 10:44:01 mars bluetoothd[1732]: bluetoothd[1732]: Not enough free handles to register service
| Jun 09 10:44:01 mars bluetoothd[1732]: bluetoothd[1732]: Bluetooth Management interface initialized
| Jun 09 10:44:01 mars bluetoothd[1732]: bluetoothd[1732]: input-headset driver probe failed for device 00:1D:28:D1:22:65
| Jun 09 10:44:01 mars bluetoothd[1732]: input-headset driver probe failed for device 00:1D:28:D1:22:65
| Jun 09 10:44:01 mars bluetoothd[1732]: bluetoothd[1732]: Adapter /org/bluez/1732/hci0 has been enabled
| Jun 09 10:44:01 mars bluetoothd[1732]: Adapter /org/bluez/1732/hci0 has been enabled
| Jun 09 10:44:01 mars bluetoothd[1732]: bluetoothd[1732]: Unknown command complete for opcode 19
| Jun 09 10:44:01 mars bluetoothd[1732]: Unknown command complete for opcode 19
When I try to connect to a phone device using dolphin and bluedevil I got
| Jun 09 10:44:47 mars obex-data-server[1735]: sdp_extract_seqtype: Unexpected end of packet
| Jun 09 10:45:03 mars obex-data-server[1735]: sdp_extract_seqtype: Unexpected end of packet
| Jun 09 10:45:18 mars obex-data-server[1735]: sdp_extract_seqtype: Unexpected end of packet
I can't install bluez(5) due to broken dependencies on obexd-client (needed by bluedevil) and libbluedevil needs bluez4.
So you any suggestion how to solve the problem with bluez4-4.101-1 or how to downgrade to a working bluez-4.101-1 would be welcome.
I use gnome-bluetooth which has bluez4 as dependence, so i can't install bluez(5)
i enabled GATT in /etc/bluetooth/main.conf and if i start the service (bluetooth.service) the result is:
[code]
-- The start-up result is done.
giu 09 17:53:52 dellst bluetoothd[6702]: bluetoothd[6702]: Parsing /etc/bluetooth/proximity.conf failed: No such file or directory
giu 09 17:53:52 dellst bluetoothd[6702]: bluetoothd[6702]: Not enough free handles to register service
giu 09 17:53:52 dellst bluetoothd[6702]: bluetoothd[6702]: Bluetooth Management interface initialized
giu 09 17:53:52 dellst bluetoothd[6702]: Parsing /etc/bluetooth/proximity.conf failed: No such file or directory
giu 09 17:53:52 dellst bluetoothd[6702]: Not enough free handles to register service
giu 09 17:53:52 dellst bluetoothd[6702]: Bluetooth Management interface initialized
giu 09 17:53:56 dellst systemd[1]: Started Bluetooth service.
-- Subject: Unit bluetooth.service has finished start-up
-- Defined-By: systemd
--
-- Unit bluetooth.service has finished starting up.
--
-- The start-up result is done.
[/code]
It seems like work fine, but the bluetooth not is detected from gnome-bluetooth.
Of that works, please record the logs before reinstalling gnome-Bluetooth and hence pulling in the new dependencies. Finally record the new log and post both.
EDIT:
i haven't restarted :D
After restart all works fine.
For those who have to bring up the adapter as root: I had an entry for myself in /etc/dbus-1/system.d/bluetooth.conf. This file has been renamed during the last update to bluetooth.conf.pacsave and replaced by the bluetooth.conf of the installation package. I expect that the installer left it untouched and place a bluetooth.conf.pacnew in the folder, as usual. However, it might help if you duplicate the "root"-section and rename it to the user you sign on with.
| Jun 12 23:12:22 mars bluetoothd[1178]: Adapter /org/bluez/1178/hci0 has been enabled
| Jun 12 23:12:22 mars bluetoothd[1178]: bluetoothd[1178]: Unknown command complete for opcode 19
| Jun 12 23:12:22 mars bluetoothd[1178]: bluetoothd[1178]: Adapter /org/bluez/1178/hci0 has been enabled
| Jun 12 23:13:24 mars obex-data-server[1187]: sdp_extract_seqtype: Unexpected end of packet
| Jun 12 23:13:40 mars obex-data-server[1187]: sdp_extract_seqtype: Unexpected end of packet
| Jun 12 23:13:56 mars obex-data-server[1187]: sdp_extract_seqtype: Unexpected end of packet
| Jun 12 23:14:12 mars obex-data-server[1187]: sdp_extract_seqtype: Unexpected end of packet
| Jun 12 23:14:28 mars obex-data-server[1187]: sdp_extract_seqtype: Unexpected end of packet
| Jun 12 23:14:45 mars obex-data-server[1187]: sdp_extract_seqtype: Unexpected end of packet
dolphin says "Device busy, please wait" while the progressbar moving for- and backward and frequently report the "Unexpected end of packet" message.
@Martin-MS: the errors you are seeing appears to be different from the other people. Could you open a separate report for that?
I downgraded today to libbluedevil-1.9.3-1, bluez-4.101-1, obexd-client-1:0.46-1 and removed bluez-libs-5.5-3 and bluez-utils-5.5-3. No progress so far, I can't still search the device using the dolphin filemanager.
It could also be an issue with kde4, since I upgraded the same day kde from 4.10.3 to 4.10.4, since it seems that the problem only appears with dolphin; and users with gnome had no problems and I can also transfer single files up the phone device if I use the bluedevil-plugin or if I start the transfer from the phone.
[Edit]
This https://bbs.archlinux.org/viewtopic.php?id=165186 describe exactly the problem that I have, too. Since obexftp works for him it looks like an issue with the last upgrade to kde-4.10.4, no solution available so far.