Auf einem aktualisierten System verbindet sich mein Headset zwar, es gibt aber kein Ton aus (und nimmt auch keinen auf)
Beim Start werden folgende Meldungen gelogged:
Jun 19 07:27:45 nuk obexd[2822]: OBEX daemon 5.47 Jun 19 07:27:45 nuk obexd[2822]: manager_init failed Jun 19 07:27:45 nuk bluez.obex[2822]: Failed to connect to socket /var/run/dbus/system_bus_socket: Permission denied Jun 19 07:27:45 nuk bluetoothd[2821]: Bluetooth daemon 5.47 Jun 19 07:27:45 nuk systemd[1]: snap.bluez.obex.service: Main process exited, code=exited, status=1/FAILURE Jun 19 07:27:45 nuk systemd[1]: snap.bluez.obex.service: Failed with result 'exit-code'. Jun 19 07:27:45 nuk bluez.bluez[2821]: D-Bus setup failed: Failed to connect to socket /var/run/dbus/system_bus_socket: Permission denied Jun 19 07:27:45 nuk bluetoothd[2821]: Unable to get on D-Bus Jun 19 07:27:45 nuk systemd[1]: snap.bluez.bluez.service: Main process exited, code=exited, status=1/FAILURE Jun 19 07:27:45 nuk systemd[1]: snap.bluez.bluez.service: Failed with result 'exit-code'. ... Jun 19 07:27:45 nuk systemd[1]: snap.bluez.obex.service: Scheduled restart job, restart counter is at 1. Jun 19 07:27:45 nuk systemd[1]: snap.bluez.bluez.service: Scheduled restart job, restart counter is at 1. Jun 19 07:27:45 nuk systemd[1]: Stopped Service for snap application bluez.bluez. Jun 19 07:27:45 nuk systemd[1]: Started Service for snap application bluez.bluez. Jun 19 07:27:45 nuk systemd[1]: Stopped Service for snap application bluez.obex. Jun 19 07:27:45 nuk dbus-daemon[3211]: [session uid=125 pid=3211] Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service' requested by ':1.32' (uid=125 pid=3316 comm="/usr/bin/gnome-shell " label="unconfined") Jun 19 07:27:45 nuk systemd[1]: Started Service for snap application bluez.obex.
Damit schlagen folgende Services fehl:
snap application bluez.bluez
bluez.obex
Der Socket ist vorhanden und hat die Berechtigungen srw-rw-rw- root.root. Woran liegt der Fehler? Wie kann ich ihn beseitigen?