Hello Peter,

On 2016-10-13 13:33:27 (+0200), Peter Nabbefeld wrote:
> 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
I'm also getting the Sap driver errors. They don't seem to be a problem
though.
If you want to disable that error message, you can follow the
instructions in the following bug report:
https://bugs.archlinux.org/task/41247

As there's endpoints connected (with pulseaudio), you should also be
able to find other devices through your bluetooth adapter.
Works fine here at least (and also seems to work on your side).

> 
> > 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.
Yeah, transmission is painful.
I never use bluetooth for that. It's unsafe and slow.

> blueman-applet doesn't show any bluetooth devices and doesn't even search
> for those.
Hm, does it show your builtin hardware in the "Adapter" menu?
If so, you're all set to go, just have to make your computer visible (if
needed) and get your device in pairing mode.
Just tried it, and it works.

> > > 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 would recommend against it ;)
They are linked in some services shipped with systemd.
As I wrote before: If they're not there, they won't be started.

display-manager.service however will be a symlink to whatever display
manager you use (lightdm, gdm, etc.) though and therefore is a kind of
placeholder.
There's no need to change anything about them.

Best,
David

-- 
https://sleepmap.de

Attachment: signature.asc
Description: PGP signature

Reply via email to