Hello David,

Am 13.10.2016 um 13:04 schrieb David Runge:
Hey again,

On 2016-10-13 12:01:42 (+0200), Peter Nabbefeld wrote:
I've got problems with bluetooth (service does not start), which seem to be
caused by systemd problems, as several services are "dead".
you might want to check the log output of those services then.
What does bluetooth/bluetoothd service log?
  journalctl -f -u bluetoothd -u bluetooth



Okt 13 05:05:47 tuchola systemd[1]: Starting Bluetooth service...
Okt 13 05:05:48 tuchola bluetoothd[485]: Bluetooth daemon 5.41
Okt 13 05:05:48 tuchola systemd[1]: Started Bluetooth service.
Okt 13 05:05:48 tuchola bluetoothd[485]: Starting SDP server
Okt 13 05:05:48 tuchola bluetoothd[485]: Bluetooth management interface 1.12 initialized Okt 13 05:05:48 tuchola bluetoothd[485]: Failed to obtain handles for "Service Changed" characteristic
Okt 13 05:05:48 tuchola bluetoothd[485]: Sap driver initialization failed.
Okt 13 05:05:48 tuchola bluetoothd[485]: sap-server: Operation not permitted (1) Okt 13 05:06:45 tuchola bluetoothd[485]: Endpoint registered: sender=:1.25 path=/MediaEndpoint/A2DPSource Okt 13 05:06:45 tuchola bluetoothd[485]: Endpoint registered: sender=:1.25 path=/MediaEndpoint/A2DPSink



Are all dependencies installed to make it run?
Have you read the wiki: https://wiki.archlinux.org/index.php/Bluetooth ?


Yes, Ihad bluetooth up and running before. I only needed to downgrad bluez* from version 5.42 to 5.41 because it has a known bug rejecting file trnsmission originating from a mobile phone to my linux laptop.


https://dpaste.de/LC2h/raw
You seem to have initialized bluetooth hardware.
The bluetooth/bluetoothd services don't seem to run though.

No results shown.
That means, no services have failed.
Why do you think, your bluetooth service has failed?


blueman-applet doesn't show any bluetooth devices and doesn't even search for those.


Tried with systemctl --all --full |grep "not-found" then,
gettings these results:

apparmor.service
auditd.service
display-manager.service
iscsid.service
plymouth-quit-wait.service
plymouth-start.service
syslog.service
Those are pretty irrelevant. What systemd can't find, it won't start.
;-)

Can I remove those, however, somehow?



I'm still a bit unsure, what the exact issue is.

Best,
David


Kind regards
Peter

Reply via email to