连手机是sbc，而耳机却是msbc，pavucontrol没有sbc选项，怎么办？
我遇到这种情况时重启 PipeWire 就好了。
重启pavucontrol还是没有sbc选项，我安装pipewire-audio，又装了libfdk-aac2，还是只有msbc cvsd。
怎么会这样……你看看系统日志呢？Debian 难道把 A2DP / SBC 给拆出来了？
看看系统日志呀。比如 sudo journalctl -n 1000。
Apr 10 11:44:01 debian bluetoothd[814]: Bluetooth daemon 5.66
Apr 10 11:44:01 debian systemd[1]: Started bluetooth.service - Bluetooth service.
Apr 10 11:44:01 debian bluealsa-aplay[813]: /usr/bin/bluealsa-aplay: W: aplay.c:1008: Couldn’t get BlueALSA PCM list: The name org.bluealsa was not provided by any .service files
Apr 10 11:44:01 debian bluealsa-aplay[813]: /usr/bin/bluealsa-aplay: D: aplay.c:1018: Starting main loop
Apr 10 11:44:01 debian systemd[1]: Starting bluealsa.service - BlueALSA service…
Apr 10 11:44:01 debian bluetoothd[814]: Starting SDP server
Apr 10 11:44:01 debian bluetoothd[814]: profiles/audio/vcp.c:vcp_init() D-Bus experimental not enabled
Apr 10 11:44:01 debian bluetoothd[814]: src/plugin.c:plugin_init() Failed to init vcp plugin
Apr 10 11:44:01 debian bluetoothd[814]: profiles/audio/mcp.c:mcp_init() D-Bus experimental not enabled
Apr 10 11:44:01 debian bluetoothd[814]: src/plugin.c:plugin_init() Failed to init mcp plugin
Apr 10 11:44:01 debian bluetoothd[814]: profiles/audio/bap.c:bap_init() D-Bus experimental not enabled
Apr 10 11:44:01 debian bluetoothd[814]: src/plugin.c:plugin_init() Failed to init bap plugin
Apr 10 11:44:01 debian bluetoothd[814]: Bluetooth management interface 1.22 initialized
Apr 10 11:44:01 debian kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Apr 10 11:44:01 debian kernel: Bluetooth: BNEP filters: protocol multicast
Apr 10 11:44:01 debian kernel: Bluetooth: BNEP socket layer initialized
Apr 10 11:44:01 debian kernel: Bluetooth: MGMT ver 1.22
Apr 10 11:44:01 debian kernel: NET: Registered PF_ALG protocol family
Apr 10 11:44:01 debian bluetoothd[814]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed.
Apr 10 11:44:01 debian bluetoothd[814]: sap-server: Operation not permitted (1)
Apr 10 11:44:01 debian NetworkManager[746]: [1712720641.6606] manager: (2C:D0:66:C8:68:32): new Bluetooth device (/org/freedesktop/NetworkManager/Devices/5)
Apr 10 11:44:01 debian bluealsa[838]: /usr/bin/bluealsa: D: main.c:585: Starting main dispatching loop
Apr 10 11:44:01 debian NetworkManager[746]: [1712720641.6608] device (2C:D0:66:C8:68:32): state change: unmanaged → unavailable (reason ‘managed’, sys-iface-state: ‘external’)
Apr 10 11:44:01 debian NetworkManager[746]: [1712720641.6612] device (2C:D0:66:C8:68:32): state change: unavailable → disconnected (reason ‘none’, sys-iface-state: ‘managed’)
Apr 10 11:44:01 debian systemd[1]: Started bluealsa.service - BlueALSA service.
Apr 10 11:44:01 debian systemd[1]: Reached target bluetooth.target - Bluetooth Support.
Apr 10 11:44:01 debian bluealsa[838]: /usr/bin/bluealsa: D: main.c:112: Acquired D-Bus service name: org.bluealsa
Apr 10 11:44:01 debian bluealsa[838]: /usr/bin/bluealsa: D: bluealsa-dbus.c:426: Registering D-Bus manager: /org/bluealsa
Apr 10 11:44:01 debian bluealsa[838]: /usr/bin/bluealsa: D: bluez.c:679: Registering battery provider: /org/bluez/hci0/battery
Apr 10 11:44:01 debian bluealsa[838]: /usr/bin/bluealsa: D: bluez.c:699: BlueZ battery provider support not available
Apr 10 11:44:01 debian bluealsa[838]: /usr/bin/bluealsa: D: bluez.c:493: Creating media endpoint object: /org/bluez/hci0/A2DP/SBC/source/1
Apr 10 11:44:01 debian bluealsa[838]: /usr/bin/bluealsa: D: bluez.c:402: Registering media endpoint: /org/bluez/hci0/A2DP/SBC/source/1
Apr 10 11:44:01 debian bluetoothd[814]: Endpoint registered: sender=:1.14 path=/org/bluez/hci0/A2DP/SBC/source/1
Apr 10 11:44:01 debian bluealsa[838]: /usr/bin/bluealsa: D: bluez.c:493: Creating media endpoint object: /org/bluez/hci0/A2DP/SBC/source/2
Apr 10 11:44:01 debian bluealsa[838]: /usr/bin/bluealsa: D: bluez.c:402: Registering media endpoint: /org/bluez/hci0/A2DP/SBC/source/2
Apr 10 11:44:01 debian bluetoothd[814]: Endpoint registered: sender=:1.14 path=/org/bluez/hci0/A2DP/SBC/source/2
Apr 10 11:44:01 debian bluealsa[838]: /usr/bin/bluealsa: D: bluez.c:493: Creating media endpoint object: /org/bluez/hci0/A2DP/SBC/sink/1
Apr 10 11:44:01 debian bluealsa[838]: /usr/bin/bluealsa: D: bluez.c:402: Registering media endpoint: /org/bluez/hci0/A2DP/SBC/sink/1
Apr 10 11:44:01 debian bluetoothd[814]: Endpoint registered: sender=:1.14 path=/org/bluez/hci0/A2DP/SBC/sink/1
Apr 10 11:44:01 debian bluealsa[838]: /usr/bin/bluealsa: D: bluez.c:493: Creating media endpoint object: /org/bluez/hci0/A2DP/SBC/sink/2
Apr 10 11:44:01 debian bluealsa[838]: /usr/bin/bluealsa: D: bluez.c:402: Registering media endpoint: /org/bluez/hci0/A2DP/SBC/sink/2
Apr 10 11:44:01 debian bluetoothd[814]: Endpoint registered: sender=:1.14 path=/org/bluez/hci0/A2DP/SBC/sink/2
Apr 10 11:44:01 debian tlp[816]: Applying power save settings…done.
Apr 10 11:44:01 debian avahi-daemon[722]: Server startup complete. Host name is debian.local. Local service cookie is 987069004.
Apr 10 11:44:01 debian tlp[816]: Setting battery charge thresholds…done.
Apr 10 11:44:01 debian systemd[1]: Finished tlp.service - TLP system startup/shutdown.
Apr 10 11:44:01 debian systemd[1]: Startup finished in 9.510s (firmware) + 3.917s (loader) + 2.532s (kernel) + 3.240s (userspace) = 19.201s.
Apr 10 11:44:02 debian kernel: r8169 0000:03:00.0 enp3s0: Link is Up - 100Mbps/Full - flow control rx/tx
Apr 10 11:44:02 debian kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enp3s0: link becomes ready
Apr 10 11:44:02 debian NetworkManager[746]: [1712720642.8191] device (enp3s0): carrier: link connected
Apr 10 11:44:02 debian NetworkManager[746]: [1712720642.8198] device (enp3s0): state change: unavailable → disconnected (reason ‘carrier-changed’, sys-iface-state: ‘managed’)
Apr 10 11:44:02 debian NetworkManager[746]: [1712720642.8211] policy: auto-activating connection ‘Wired connection 1’ (d09f768c-ad5e-359e-80be-bfd5c64e3395)
Apr 10 11:44:02 debian NetworkManager[746]: [1712720642.8220] device (enp3s0): Activation: starting connection ‘Wired connection 1’ (d09f768c-ad5e-359e-80be-bfd5c64e3395)
Apr 10 11:44:02 debian NetworkManager[746]: [1712720642.8222] device (enp3s0): state change: disconnected → prepare (reason ‘none’, sys-iface-state: ‘managed’)
Apr 10 11:44:02 debian NetworkManager[746]: [1712720642.8227] manager: NetworkManager state is now CONNECTING
Apr 10 11:44:02 debian NetworkManager[746]: [1712720642.8236] device (enp3s0): set-hw-addr: set-cloned MAC address to 3A:82:8A:22:FA:0D (stable)
Apr 10 11:44:02 debian NetworkManager[746]: [1712720642.8236] device (enp3s0): state change: prepare → config (reason ‘none’, sys-iface-state: ‘managed’)
Apr 10 11:44:02 debian NetworkManager[746]: [1712720642.8241] device (enp3s0): state change: config → ip-config (reason ‘none’, sys-iface-state: ‘managed’)
Apr 10 11:44:02 debian NetworkManager[746]: [1712720642.8245] dhcp4 (enp3s0): activation: beginning transaction (timeout in 45 seconds)
Apr 10 11:44:02 debian avahi-daemon[722]: Joining mDNS multicast group on interface enp3s0.IPv6 with address fe80::4b76:61e3:dc1a:a94e.
Apr 10 11:44:02 debian avahi-daemon[722]: New relevant interface enp3s0.IPv6 for mDNS.
Apr 10 11:44:02 debian avahi-daemon[722]: Registering new address record for fe80::4b76:61e3:dc1a:a94e on enp3s0.*.
Apr 10 11:44:02 debian NetworkManager[746]: [1712720642.8259] dhcp4 (enp3s0): state changed no lease
Apr 10 11:44:03 debian NetworkManager[746]: [1712720643.4250] dhcp4 (enp3s0): state changed new lease, address=192.168.1.109
Apr 10 11:44:03 debian NetworkManager[746]: [1712720643.4259] policy: set ‘Wired connection 1’ (enp3s0) as default for IPv4 routing and DNS
Apr 10 11:44:03 debian avahi-daemon[722]: Joining mDNS multicast group on interface enp3s0.IPv4 with address 192.168.1.109.
Apr 10 11:44:03 debian avahi-daemon[722]: New relevant interface enp3s0.IPv4 for mDNS.
Apr 10 11:44:03 debian avahi-daemon[722]: Registering new address record for 192.168.1.109 on enp3s0.IPv4.
Apr 10 11:44:03 debian NetworkManager[746]: [1712720643.4376] device (enp3s0): state change: ip-config → ip-check (reason ‘none’, sys-iface-state: ‘managed’)
Apr 10 11:44:03 debian NetworkManager[746]: [1712720643.4414] device (enp3s0): state change: ip-check → secondaries (reason ‘none’, sys-iface-state: ‘managed’)
Apr 10 11:44:03 debian NetworkManager[746]: [1712720643.4417] device (enp3s0): state change: secondaries → activated (reason ‘none’, sys-iface-state: ‘managed’)
Apr 10 11:44:03 debian NetworkManager[746]: [1712720643.4423] manager: NetworkManager state is now CONNECTED_SITE
Apr 10 11:44:03 debian NetworkManager[746]: [1712720643.4428] device (enp3s0): Activation: successful, device activated.
Apr 10 11:44:03 debian NetworkManager[746]: [1712720643.4433] manager: NetworkManager state is now CONNECTED_GLOBAL
Apr 10 11:44:03 debian ModemManager[759]: [base-manager] couldn’t check support for device ‘/sys/devices/pci0000:00/0000:00:1c.0/0000:01:00.0’: not supported by any plugin
Apr 10 11:44:03 debian ModemManager[759]: [base-manager] couldn’t check support for device ‘/sys/devices/pci0000:00/0000:00:1d.1/0000:03:00.0’: not supported by any plugin
Apr 10 11:44:05 debian wpa_supplicant[748]: wlp1s0: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=COUNTRY alpha2=CN
Apr 10 11:44:05 debian NetworkManager[746]: [1712720645.0759] manager: startup complete
Apr 10 11:44:07 debian login[773]: pam_unix(login:session): session opened for user hp(uid=1000) by LOGIN(uid=0)
Apr 10 11:44:07 debian systemd[1]: Created slice user-1000.slice - User Slice of UID 1000.
Apr 10 11:44:07 debian systemd[1]: Starting user-runtime-dir@1000.service - User Runtime Directory /run/user/1000…
Apr 10 11:44:07 debian systemd-logind[732]: New session 1 of user hp.
Apr 10 11:44:07 debian systemd[1]: Finished user-runtime-dir@1000.service - User Runtime Directory /run/user/1000.
Apr 10 11:44:07 debian systemd[1]: Starting user@1000.service - User Manager for UID 1000…
Apr 10 11:44:07 debian (systemd)[1030]: pam_unix(systemd-user:session): session opened for user hp(uid=1000) by (uid=0)
Apr 10 11:44:07 debian systemd-xdg-autostart-generator[1045]: Exec binary ‘start-pulseaudio-x11’ does not exist: No such file or directory
Apr 10 11:44:07 debian systemd-xdg-autostart-generator[1045]: /etc/xdg/autostart/pulseaudio.desktop: not generating unit, executable specified in Exec= does not exist.
Apr 10 11:44:07 debian systemd[1030]: Queued start job for default target default.target.
Apr 10 11:44:07 debian systemd[1030]: Created slice app.slice - User Application Slice.
Apr 10 11:44:07 debian systemd[1030]: Created slice session.slice - User Core Session Slice.
Apr 10 11:44:07 debian systemd[1030]: Reached target paths.target - Paths.
Apr 10 11:44:07 debian systemd[1030]: Reached target timers.target - Timers.
Apr 10 11:44:07 debian systemd[1030]: Starting dbus.socket - D-Bus User Message Bus Socket…
Apr 10 11:44:07 debian systemd[1030]: Listening on dirmngr.socket - GnuPG network certificate management daemon.
Apr 10 11:44:07 debian systemd[1030]: Listening on gpg-agent-browser.socket - GnuPG cryptographic agent and passphrase cache (access for web browsers).
Apr 10 11:44:07 debian systemd[1030]: Listening on gpg-agent-extra.socket - GnuPG cryptographic agent and passphrase cache (restricted).
Apr 10 11:44:07 debian systemd[1030]: Listening on gpg-agent-ssh.socket - GnuPG cryptographic agent (ssh-agent emulation).
Apr 10 11:44:07 debian systemd[1030]: Listening on gpg-agent.socket - GnuPG cryptographic agent and passphrase cache.
Apr 10 11:44:07 debian systemd[1030]: Listening on pipewire-pulse.socket - PipeWire PulseAudio.
Apr 10 11:44:07 debian systemd[1030]: Listening on pipewire.socket - PipeWire Multimedia System Socket.
Apr 10 11:44:07 debian systemd[1030]: Listening on dbus.socket - D-Bus User Message Bus Socket.
Apr 10 11:44:07 debian systemd[1030]: Reached target sockets.target - Sockets.
Apr 10 11:44:07 debian systemd[1030]: Reached target basic.target - Basic System.
Apr 10 11:44:07 debian systemd[1]: Started user@1000.service - User Manager for UID 1000.
Apr 10 11:44:07 debian systemd[1030]: Started pipewire.service - PipeWire Multimedia Service.
Apr 10 11:44:07 debian systemd[1]: Started session-1.scope - Session 1 of User hp.
Apr 10 11:44:07 debian systemd[1030]: Started wireplumber.service - Multimedia Service Session Manager.
Apr 10 11:44:07 debian systemd[1030]: Started pipewire-pulse.service - PipeWire PulseAudio.
Apr 10 11:44:07 debian systemd[1030]: Reached target default.target - Main User Target.
Apr 10 11:44:07 debian systemd[1030]: Startup finished in 130ms.
Apr 10 11:44:07 debian systemd[1030]: Starting dbus.service - D-Bus User Message Bus…
Apr 10 11:44:07 debian systemd[1030]: Started dbus.service - D-Bus User Message Bus.
Apr 10 11:44:07 debian pipewire[1047]: mod.rt: Can’t find org.freedesktop.portal.Desktop. Is xdg-desktop-portal running?
Apr 10 11:44:07 debian pipewire[1047]: mod.rt: found session bus but no portal
Apr 10 11:44:07 debian wireplumber[1048]: Can’t find org.freedesktop.portal.Desktop. Is xdg-desktop-portal running?
Apr 10 11:44:07 debian wireplumber[1048]: found session bus but no portal
Apr 10 11:44:07 debian pipewire-pulse[1049]: mod.rt: Can’t find org.freedesktop.portal.Desktop. Is xdg-desktop-portal running?
Apr 10 11:44:07 debian pipewire-pulse[1049]: mod.rt: found session bus but no portal
Apr 10 11:44:07 debian dbus-daemon[729]: [system] Activating via systemd: service name=‘org.freedesktop.RealtimeKit1’ unit=‘rtkit-daemon.service’ requested by ‘:1.19’ (uid=1000 pid=1047 com>
Apr 10 11:44:07 debian systemd[1]: Starting rtkit-daemon.service - RealtimeKit Scheduling Policy Service…
Apr 10 11:44:07 debian dbus-daemon[729]: [system] Successfully activated service ‘org.freedesktop.RealtimeKit1’
Apr 10 11:44:07 debian systemd[1]: Started rtkit-daemon.service - RealtimeKit Scheduling Policy Service.
Apr 10 11:44:07 debian rtkit-daemon[1056]: Successfully called chroot.
Apr 10 11:44:07 debian rtkit-daemon[1056]: Successfully dropped privileges.
Apr 10 11:44:07 debian rtkit-daemon[1056]: Successfully limited resources.
Apr 10 11:44:07 debian rtkit-daemon[1056]: Running.
Apr 10 11:44:07 debian rtkit-daemon[1056]: Canary thread running.
Apr 10 11:44:07 debian rtkit-daemon[1056]: Watchdog thread running.
Apr 10 11:44:07 debian rtkit-daemon[1056]: Successfully made thread 1047 of process 1047 owned by ‘1000’ high priority at nice level -11.
Apr 10 11:44:07 debian rtkit-daemon[1056]: Supervising 1 threads of 1 processes of 1 users.
Apr 10 11:44:07 debian rtkit-daemon[1056]: Successfully made thread 1049 of process 1049 owned by ‘1000’ high priority at nice level -11.
Apr 10 11:44:07 debian rtkit-daemon[1056]: Supervising 2 threads of 2 processes of 1 users.
Apr 10 11:44:07 debian rtkit-daemon[1056]: Successfully made thread 1048 of process 1048 owned by ‘1000’ high priority at nice level -11.
Apr 10 11:44:07 debian rtkit-daemon[1056]: Supervising 3 threads of 3 processes of 1 users.
Apr 10 11:44:07 debian rtkit-daemon[1056]: Supervising 3 threads of 3 processes of 1 users.
Apr 10 11:44:07 debian rtkit-daemon[1056]: Supervising 3 threads of 3 processes of 1 users.
Apr 10 11:44:07 debian rtkit-daemon[1056]: Supervising 3 threads of 3 processes of 1 users.
Apr 10 11:44:07 debian rtkit-daemon[1056]: Supervising 3 threads of 3 processes of 1 users.
Apr 10 11:44:07 debian rtkit-daemon[1056]: Successfully made thread 1063 of process 1048 owned by ‘1000’ RT at priority 20.
Apr 10 11:44:07 debian rtkit-daemon[1056]: Supervising 4 threads of 3 processes of 1 users.
Apr 10 11:44:07 debian rtkit-daemon[1056]: Supervising 4 threads of 3 processes of 1 users.
Apr 10 11:44:07 debian rtkit-daemon[1056]: Successfully made thread 1065 of process 1047 owned by ‘1000’ RT at priority 20.
Apr 10 11:44:07 debian rtkit-daemon[1056]: Supervising 5 threads of 3 processes of 1 users.
Apr 10 11:44:07 debian rtkit-daemon[1056]: Supervising 5 threads of 3 processes of 1 users.
Apr 10 11:44:07 debian rtkit-daemon[1056]: Successfully made thread 1067 of process 1049 owned by ‘1000’ RT at priority 20.
Apr 10 11:44:07 debian rtkit-daemon[1056]: Supervising 6 threads of 3 processes of 1 users.
Apr 10 11:44:07 debian wireplumber[1048]: Failed to set scheduler settings: Operation not permitted
Apr 10 11:44:07 debian wireplumber[1048]: SPA handle ‘api.libcamera.enum.manager’ could not be loaded; is it installed?
Apr 10 11:44:07 debian wireplumber[1048]: PipeWire’s libcamera SPA missing or broken. libcamera not supported.
Apr 10 11:44:07 debian wireplumber[1048]: Trying to use legacy bluez5 API for LE Audio - only A2DP will be supported. Please upgrade bluez5.
Apr 10 11:44:07 debian kernel: Bluetooth: RFCOMM TTY layer initialized
Apr 10 11:44:07 debian kernel: Bluetooth: RFCOMM socket layer initialized
Apr 10 11:44:07 debian kernel: Bluetooth: RFCOMM ver 1.11
Apr 10 11:44:07 debian bluetoothd[814]: Endpoint registered: sender=:1.24 path=/MediaEndpoint/A2DPSource/ldac
Apr 10 11:44:07 debian bluetoothd[814]: Endpoint registered: sender=:1.24 path=/MediaEndpoint/A2DPSink/aptx_hd
Apr 10 11:44:07 debian bluetoothd[814]: Endpoint registered: sender=:1.24 path=/MediaEndpoint/A2DPSource/aptx_hd
Apr 10 11:44:07 debian bluetoothd[814]: Endpoint registered: sender=:1.24 path=/MediaEndpoint/A2DPSink/aptx
Apr 10 11:44:07 debian bluetoothd[814]: Endpoint registered: sender=:1.24 path=/MediaEndpoint/A2DPSource/aptx
Apr 10 11:44:07 debian bluetoothd[814]: Endpoint registered: sender=:1.24 path=/MediaEndpoint/A2DPSink/sbc
Apr 10 11:44:07 debian bluetoothd[814]: Endpoint registered: sender=:1.24 path=/MediaEndpoint/A2DPSource/sbc
Apr 10 11:44:07 debian bluetoothd[814]: Endpoint registered: sender=:1.24 path=/MediaEndpoint/A2DPSink/sbc_xq
Apr 10 11:44:07 debian bluetoothd[814]: Endpoint registered: sender=:1.24 path=/MediaEndpoint/A2DPSource/sbc_xq
Apr 10 11:44:07 debian bluetoothd[814]: Endpoint registered: sender=:1.24 path=/MediaEndpoint/A2DPSource/aptx_ll_1
Apr 10 11:44:07 debian bluetoothd[814]: Endpoint registered: sender=:1.24 path=/MediaEndpoint/A2DPSource/aptx_ll_0
Apr 10 11:44:07 debian bluetoothd[814]: Endpoint registered: sender=:1.24 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
Apr 10 11:44:07 debian bluetoothd[814]: Endpoint registered: sender=:1.24 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
Apr 10 11:44:07 debian bluetoothd[814]: Endpoint registered: sender=:1.24 path=/MediaEndpoint/A2DPSource/faststream
Apr 10 11:44:07 debian bluetoothd[814]: Endpoint registered: sender=:1.24 path=/MediaEndpoint/A2DPSource/faststream_duplex
Apr 10 11:44:07 debian bluetoothd[814]: Endpoint registered: sender=:1.24 path=/MediaEndpoint/A2DPSink/opus_05
Apr 10 11:44:07 debian bluetoothd[814]: Endpoint registered: sender=:1.24 path=/MediaEndpoint/A2DPSource/opus_05
Apr 10 11:44:07 debian bluetoothd[814]: Endpoint registered: sender=:1.24 path=/MediaEndpoint/A2DPSink/opus_05_duplex
Apr 10 11:44:07 debian bluetoothd[814]: Endpoint registered: sender=:1.24 path=/MediaEndpoint/A2DPSource/opus_05_duplex
Apr 10 11:44:13 debian systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Apr 10 11:44:17 debian dbus-daemon[1052]: [session uid=1000 pid=1052] Activating via systemd: service name=‘org.a11y.Bus’ unit=‘at-spi-dbus-bus.service’ requested by ‘:1.15’ (uid=1000 pid=1>
Apr 10 11:44:17 debian systemd[1030]: Starting at-spi-dbus-bus.service - Accessibility services bus…
Apr 10 11:44:17 debian dbus-daemon[1052]: [session uid=1000 pid=1052] Successfully activated service ‘org.a11y.Bus’
Apr 10 11:44:17 debian systemd[1030]: Started at-spi-dbus-bus.service - Accessibility services bus.
Apr 10 11:44:17 debian dbus-daemon[1052]: [session uid=1000 pid=1052] Activating via systemd: service name=‘org.gtk.vfs.Daemon’ unit=‘gvfs-daemon.service’ requested by ‘:1.14’ (uid=1000 pid>
Apr 10 11:44:17 debian systemd[1030]: Starting gvfs-daemon.service - Virtual filesystem service…
Apr 10 11:44:17 debian dbus-daemon[1052]: [session uid=1000 pid=1052] Successfully activated service ‘org.gtk.vfs.Daemon’
Apr 10 11:44:17 debian systemd[1030]: Started gvfs-daemon.service - Virtual filesystem service.
Apr 10 11:44:17 debian at-spi-bus-launcher[1165]: dbus-daemon[1165]: Activating service name=‘org.a11y.atspi.Registry’ requested by ‘:1.0’ (uid=1000 pid=1153 comm=“wofi --show drun”)
Apr 10 11:44:17 debian at-spi-bus-launcher[1165]: dbus-daemon[1165]: Successfully activated service ‘org.a11y.atspi.Registry’
Apr 10 11:44:17 debian at-spi-bus-launcher[1180]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Apr 10 11:44:22 debian dbus-daemon[1052]: [session uid=1000 pid=1052] Activating via systemd: service name=‘org.freedesktop.portal.Desktop’ unit=‘xdg-desktop-portal.service’ requested by ':>
Apr 10 11:44:22 debian systemd[1030]: Starting xdg-desktop-portal.service - Portal service…
Apr 10 11:44:22 debian dbus-daemon[1052]: [session uid=1000 pid=1052] Activating via systemd: service name=‘org.freedesktop.portal.Documents’ unit=‘xdg-document-portal.service’ requested by>
Apr 10 11:44:22 debian systemd[1030]: Starting xdg-document-portal.service - flatpak document portal service…
Apr 10 11:44:22 debian dbus-daemon[1052]: [session uid=1000 pid=1052] Activating via systemd: service name=‘org.freedesktop.impl.portal.PermissionStore’ unit=‘xdg-permission-store.service’ >
Apr 10 11:44:22 debian systemd[1030]: Starting xdg-permission-store.service - sandboxed app permission store…
Apr 10 11:44:22 debian dbus-daemon[1052]: [session uid=1000 pid=1052] Successfully activated service ‘org.freedesktop.impl.portal.PermissionStore’
Apr 10 11:44:22 debian systemd[1030]: Started xdg-permission-store.service - sandboxed app permission store.
Apr 10 11:44:22 debian dbus-daemon[1052]: [session uid=1000 pid=1052] Successfully activated service ‘org.freedesktop.portal.Documents’
Apr 10 11:44:22 debian systemd[1030]: Started xdg-document-portal.service - flatpak document portal service.
Apr 10 11:44:22 debian xdg-document-portal[1204]: Ignoring invalid max threads value 4294967295 > max (100000).
Apr 10 11:44:22 debian dbus-daemon[1052]: [session uid=1000 pid=1052] Activating via systemd: service name=‘org.freedesktop.impl.portal.desktop.gtk’ unit=‘xdg-desktop-portal-gtk.service’ re>
Apr 10 11:44:22 debian systemd[1030]: Starting xdg-desktop-portal-gtk.service - Portal service (GTK/GNOME implementation)…
Apr 10 11:44:22 debian dbus-daemon[1052]: [session uid=1000 pid=1052] Successfully activated service ‘org.freedesktop.impl.portal.desktop.gtk’
Apr 10 11:44:22 debian systemd[1030]: Started xdg-desktop-portal-gtk.service - Portal service (GTK/GNOME implementation).
Apr 10 11:44:22 debian rtkit-daemon[1056]: Supervising 6 threads of 3 processes of 1 users.
Apr 10 11:44:22 debian rtkit-daemon[1056]: Supervising 6 threads of 3 processes of 1 users.
Apr 10 11:44:22 debian rtkit-daemon[1056]: Supervising 6 threads of 3 processes of 1 users.
Apr 10 11:44:22 debian dbus-daemon[1052]: [session uid=1000 pid=1052] Successfully activated service ‘org.freedesktop.portal.Desktop’
Apr 10 11:44:22 debian systemd[1030]: Started xdg-desktop-portal.service - Portal service.
Apr 10 11:44:22 debian dbus-daemon[1052]: [session uid=1000 pid=1052] Activating via systemd: service name=‘org.blueman.Applet’ unit=‘blueman-applet.service’ requested by ‘:1.21’ (uid=1000 >
Apr 10 11:44:22 debian systemd[1030]: Starting blueman-applet.service - Bluetooth management applet…
Apr 10 11:44:23 debian blueman-applet[1230]: blueman-applet 11.44.23 WARNING PluginManager:94 load_plugin: Failed to start plugin GameControllerWakelock: Only X11 platform is supported
Apr 10 11:44:23 debian blueman-applet[1230]: blueman-applet 11.44.23 WARNING TransferService:213 _make_share_path: Failed to get Download dir from XDG
Apr 10 11:44:23 debian blueman-applet[1230]: blueman-applet 11.44.23 WARNING PluginManager:151 __load_plugin: Not loading PPPSupport because its conflict has higher priority
Apr 10 11:44:23 debian blueman-applet[1230]: blueman-applet 11.44.23 WARNING PluginManager:151 __load_plugin: Not loading DhcpClient because its conflict has higher priority
Apr 10 11:44:23 debian dbus-daemon[1052]: [session uid=1000 pid=1052] Successfully activated service ‘org.blueman.Applet’
Apr 10 11:44:23 debian systemd[1030]: Started blueman-applet.service - Bluetooth management applet.
Apr 10 11:44:23 debian dbus-daemon[1052]: [session uid=1000 pid=1052] Activating via systemd: service name=‘org.bluez.obex’ unit=‘obex.service’ requested by ‘:1.28’ (uid=1000 pid=1230 comm=>
Apr 10 11:44:23 debian systemd[1030]: Starting obex.service - Bluetooth OBEX service…
Apr 10 11:44:23 debian obexd[1235]: OBEX daemon 5.66
Apr 10 11:44:23 debian dbus-daemon[1052]: [session uid=1000 pid=1052] Successfully activated service ‘org.bluez.obex’
Apr 10 11:44:23 debian systemd[1030]: Started obex.service - Bluetooth OBEX service.
Apr 10 11:44:23 debian dbus-daemon[1052]: [session uid=1000 pid=1052] Activating via systemd: service name=‘ca.desrt.dconf’ unit=‘dconf.service’ requested by ‘:1.21’ (uid=1000 pid=1194 comm>
Apr 10 11:44:23 debian systemd[1030]: Starting dconf.service - User preferences database…
Apr 10 11:44:23 debian dbus-daemon[1052]: [session uid=1000 pid=1052] Successfully activated service ‘ca.desrt.dconf’
Apr 10 11:44:23 debian systemd[1030]: Started dconf.service - User preferences database.
Apr 10 11:44:25 debian systemd[1030]: Reached target bluetooth.target - Bluetooth.
Apr 10 11:44:29 debian systemd[1]: systemd-fsckd.service: Deactivated successfully.
Apr 10 11:44:29 debian bluealsa[838]: /usr/bin/bluealsa: D: bluez.c:1049: Signal: org.freedesktop.DBus.ObjectManager.InterfacesAdded()
Apr 10 11:44:29 debian bluealsa[838]: /usr/bin/bluealsa: D: bluez.c:1145: Adding new Stream End-Point: 9C:49:52:C0:1D:10: SBC
Apr 10 11:44:29 debian bluealsa[838]: /usr/bin/bluealsa: D: bluez.c:1049: Signal: org.freedesktop.DBus.ObjectManager.InterfacesAdded()
Apr 10 11:44:29 debian bluealsa[838]: /usr/bin/bluealsa: D: bluez.c:1145: Adding new Stream End-Point: 9C:49:52:C0:1D:10: AAC
Apr 10 11:44:30 debian bluealsa[838]: /usr/bin/bluealsa: D: bluez.c:1049: Signal: org.freedesktop.DBus.ObjectManager.InterfacesAdded()
Apr 10 11:44:30 debian bluealsa[838]: /usr/bin/bluealsa: D: dbus.c:66: Called: org.bluez.MediaEndpoint1.SetConfiguration() on /org/bluez/hci0/A2DP/SBC/source/1
Apr 10 11:44:30 debian bluealsa[838]: /usr/bin/bluealsa: D: a2dp.c:356: Selected A2DP SBC bit-pool range: [2, 39]
Apr 10 11:44:30 debian bluealsa[838]: /usr/bin/bluealsa: D: bluez.c:313: A2DP Source (SBC) configured for device 9C:49:52:C0:1D:10
Apr 10 11:44:30 debian bluealsa[838]: /usr/bin/bluealsa: D: bluez.c:316: A2DP selected configuration blob [len=4]: 21150227
Apr 10 11:44:30 debian bluealsa[838]: /usr/bin/bluealsa: D: bluez.c:318: PCM configuration: channels: 2, sampling: 44100
Apr 10 11:44:30 debian bluealsa[838]: /usr/bin/bluealsa: D: bluez.c:493: Creating media endpoint object: /org/bluez/hci0/A2DP/SBC/source/3
Apr 10 11:44:30 debian bluealsa[838]: /usr/bin/bluealsa: D: bluez.c:402: Registering media endpoint: /org/bluez/hci0/A2DP/SBC/source/3
Apr 10 11:44:30 debian bluetoothd[814]: Endpoint registered: sender=:1.14 path=/org/bluez/hci0/A2DP/SBC/source/3
Apr 10 11:44:30 debian bluealsa[838]: /usr/bin/bluealsa: D: bluez.c:1247: Signal: org.freedesktop.DBus.Properties.PropertiesChanged(): org.bluez.MediaTransport1: Delay
Apr 10 11:44:30 debian wireplumber[1048]: Properties changed in unknown transport /org/bluez/hci0/dev_9C_49_52_C0_1D_10/fd0
Apr 10 11:44:31 debian systemd-timesyncd[677]: Contacted time server 5.79.108.34:123 (2.debian.pool.ntp.org).
Apr 10 11:44:31 debian systemd-timesyncd[677]: Initial clock synchronization to Wed 2024-04-10 11:44:31.830539 CST.
Apr 10 11:44:32 debian systemd[1]: systemd-hostnamed.service: Deactivated successfully.
Apr 10 11:44:32 debian wireplumber[1048]: Failed to register battery provider. Error: org.freedesktop.DBus.Error.UnknownMethod
Apr 10 11:44:32 debian wireplumber[1048]: BlueZ Battery Provider is not available, won’t retry to register it. Make sure you are running BlueZ 5.56+ with experimental features to use Batter>
Apr 10 11:44:32 debian kernel: input: Redmi Buds 5 (AVRCP) as /devices/virtual/input/input16
Apr 10 11:44:32 debian bluealsa[838]: /usr/bin/bluealsa: D: bluez.c:1247: Signal: org.freedesktop.DBus.Properties.PropertiesChanged(): org.bluez.MediaTransport1: Volume
Apr 10 11:44:32 debian bluealsa[838]: /usr/bin/bluealsa: D: bluez.c:1265: Skipping A2DP volume update: 64
Apr 10 11:44:32 debian wireplumber[1048]: Properties changed in unknown transport /org/bluez/hci0/dev_9C_49_52_C0_1D_10/fd0
Apr 10 11:44:32 debian systemd-logind[732]: Watching system buttons on /dev/input/event16 (Redmi Buds 5 (AVRCP))
Apr 10 11:44:35 debian wireplumber[1048]: RFCOMM receive command but modem not available: AT+CCWA=1
Apr 10 11:44:35 debian wireplumber[1048]: RFCOMM receive command but modem not available: AT+XIAOMI=1,1,110,100,100,80,101
Apr 10 11:44:35 debian wireplumber[1048]: RFCOMM receive command but modem not available: AT+XIAOMI=FF01020101120004013FFF150B2005010116040006030001FF
Apr 10 11:44:35 debian wireplumber[1048]: RFCOMM receive command but modem not available: AT+XIAOMI=FF010201010400020B00FF
Apr 10 11:44:35 debian wireplumber[1048]: RFCOMM receive command but modem not available: AT+XIAOMI=1,1,110,100,100,80,101
Apr 10 11:44:35 debian wireplumber[1048]: RFCOMM receive command but modem not available: AT+XIAOMI=FF010201010400020A00FF
Apr 10 11:44:35 debian wireplumber[1048]: RFCOMM receive command but modem not available: AT+XIAOMI=FF01020103020E00FF
Apr 10 11:44:42 debian blueman-applet[1230]: /usr/lib/python3/dist-packages/blueman/gui/GtkAnimation.py:73: Warning: Source ID 846 was not found when attempting to remove it
Apr 10 11:44:42 debian blueman-applet[1230]: GLib.source_remove(self._source)
Apr 10 11:44:42 debian kernel: Bluetooth: hci0: SCO packet for unknown connection handle 0
Apr 10 11:44:42 debian kernel: Bluetooth: hci0: SCO packet for unknown connection handle 0
Apr 10 11:44:42 debian kernel: Bluetooth: hci0: SCO packet for unknown connection handle 0
Apr 10 11:44:42 debian kernel: Bluetooth: hci0: SCO packet for unknown connection handle 0
Apr 10 11:44:42 debian kernel: Bluetooth: hci0: SCO packet for unknown connection handle 0
Apr 10 11:44:42 debian kernel: Bluetooth: hci0: SCO packet for unknown connection handle 0
Apr 10 11:44:42 debian kernel: Bluetooth: hci0: SCO packet for unknown connection handle 0
Apr 10 11:44:42 debian kernel: Bluetooth: hci0: SCO packet for unknown connection handle 0
Apr 10 11:44:42 debian wireplumber[1048]: RFCOMM receive command but modem not available: AT+XIAOMI=1,1,110,100,100,80,101
Apr 10 11:44:43 debian wireplumber[1048]: RFCOMM receive command but modem not available: AT+XIAOMI=1,1,110,100,100,80,101
Apr 10 11:44:45 debian blueman-applet[1230]: /usr/lib/python3/dist-packages/blueman/gui/GtkAnimation.py:73: Warning: Source ID 908 was not found when attempting to remove it
Apr 10 11:44:45 debian blueman-applet[1230]: GLib.source_remove(self._source)
Apr 10 11:44:46 debian blueman-applet[1230]: /usr/lib/python3/dist-packages/blueman/gui/GtkAnimation.py:73: Warning: Source ID 927 was not found when attempting to remove it
Apr 10 11:44:46 debian blueman-applet[1230]: GLib.source_remove(self._source)
Apr 10 11:44:52 debian su[1442]: (to root) hp on pts/0
Apr 10 11:44:52 debian su[1442]: pam_unix(su:session): session opened for user root(uid=0) by (uid=1000)
Apr 10 11:44:54 debian systemd[1]: blueman-mechanism.service: Deactivated successfully.
Apr 10 11:45:08 debian sudo[1479]: root : TTY=pts/0 ; PWD=/home/hp ; USER=root ; COMMAND=/usr/bin/journalctl -n 1000
Apr 10 11:45:08 debian sudo[1479]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0)
咦，bluealsa 是啥？
不管它是啥，建议卸载之。用 PipeWire 或者 PulseAudio（不管你用的是哪个）自己的蓝牙支持就好。
1 个赞
十分感谢，解决了，bluez-alsa-utils应该是没看wiki前瞎装的。
BlueALSA 旨在直接提供 ALSA 和 BlueZ 之间的集成。该集成原内置于 Bluez 中，于 Bluez5 开始被从 Bluez 中移除。
它的主要用例是那些不需要或不能使用 PulseAudio/PipeWire 的系统：
BlueALSA is designed specifically for use on small, low-powered, dedicated audio or audio/visual systems where the high-level audio management features of PulseAudio or PipeWire are not required. The target system must be able to function correctly with all its audio applications interfacing directly with ALSA, with only one application at a time using each Bluetooth audio stream. In such systems BlueALSA adds Bluetooth audio support to the existing ALSA sound card support. Note this means that the applications are constrained by the capabilities of the ALSA API, and the higher-level audio processing features of audio servers such as PulseAudio and PipeWire are not available.
换句话说，如果你运行 PulseAudio/PipeWire，你可能不应该运行 BlueALSA，除非有充分理由这么做。如文档中所述：
PulseAudio has its own bluetooth audio implementation which is sufficient in many common usage scenarios. If you need to use PulseAudio for any reason then it is recommended to at least try its internal bluetooth audio implementation before attempting this integration. Conversely, if you do not need PulseAudio, then it is recommended to use BlueALSA for bluetooth audio and not to run PulseAudio at all.
Of course, there may be rare occasions when you find it necessary to run both services. This wiki article describes one method of using the two services in an integrated way. This approach should be considered as “experimental” and as such suffers many compromises and limitations.
2 个赞