Feb 28 12:07:13 teo-vivobook kernel: pci 10000:e0:06.0: Primary bus is hard wired to 0
Feb 28 12:07:13 teo-vivobook kernel: pci 10000:e0:06.0: Primary bus is hard wired to 0
Feb 28 12:07:16 teo-vivobook dbus-broker-launch[593]: Looking up NSS user entry for 'pulse'...
Feb 28 12:07:16 teo-vivobook dbus-broker-launch[593]: NSS returned no entry for 'pulse'
Feb 28 12:07:16 teo-vivobook dbus-broker-launch[593]: Invalid user-name in /usr/share/dbus-1/system.d/pulseaudio-system.conf +27: user="pulse"
Feb 28 12:07:16 teo-vivobook bluetoothd[596]: Bluetooth daemon 5.79
Feb 28 12:07:16 teo-vivobook bluetoothd[596]: Starting SDP server
Feb 28 12:07:16 teo-vivobook bluetoothd[596]: src/plugin.c:init_plugin() System does not support bap plugin
Feb 28 12:07:16 teo-vivobook bluetoothd[596]: src/plugin.c:init_plugin() System does not support bass plugin
Feb 28 12:07:16 teo-vivobook bluetoothd[596]: src/plugin.c:init_plugin() System does not support mcp plugin
Feb 28 12:07:16 teo-vivobook bluetoothd[596]: src/plugin.c:init_plugin() System does not support vcp plugin
Feb 28 12:07:16 teo-vivobook bluetoothd[596]: profiles/audio/micp.c:micp_init() D-Bus experimental not enabled
Feb 28 12:07:16 teo-vivobook bluetoothd[596]: src/plugin.c:init_plugin() System does not support micp plugin
Feb 28 12:07:16 teo-vivobook bluetoothd[596]: src/plugin.c:init_plugin() System does not support ccp plugin
Feb 28 12:07:16 teo-vivobook bluetoothd[596]: src/plugin.c:init_plugin() System does not support csip plugin
Feb 28 12:07:16 teo-vivobook bluetoothd[596]: src/plugin.c:init_plugin() System does not support asha plugin
Feb 28 12:07:16 teo-vivobook bluetoothd[596]: Bluetooth management interface 1.22 initialized
Feb 28 12:07:16 teo-vivobook NetworkManager[595]: <info> [1740740836.3050] Loaded device plugin: NMBluezManager (/usr/lib/NetworkManager/1.50.2-1/libnm-device-plugin-bluetooth.so)
Feb 28 12:07:16 teo-vivobook bluetoothd[596]: Battery Provider Manager created
Feb 28 12:07:24 teo-vivobook wireplumber[817]: wp-internal-comp-loader: Loading profile 'main'
Feb 28 12:07:25 teo-vivobook bluetoothd[596]: Endpoint registered: sender=:1.31 path=/MediaEndpoint/A2DPSource/ldac
Feb 28 12:07:25 teo-vivobook bluetoothd[596]: Endpoint registered: sender=:1.31 path=/MediaEndpoint/A2DPSink/aptx_hd
Feb 28 12:07:25 teo-vivobook bluetoothd[596]: Endpoint registered: sender=:1.31 path=/MediaEndpoint/A2DPSource/aptx_hd
Feb 28 12:07:25 teo-vivobook bluetoothd[596]: Endpoint registered: sender=:1.31 path=/MediaEndpoint/A2DPSink/aptx
Feb 28 12:07:25 teo-vivobook bluetoothd[596]: Endpoint registered: sender=:1.31 path=/MediaEndpoint/A2DPSource/aptx
Feb 28 12:07:25 teo-vivobook bluetoothd[596]: Endpoint registered: sender=:1.31 path=/MediaEndpoint/A2DPSink/aac
Feb 28 12:07:25 teo-vivobook bluetoothd[596]: Endpoint registered: sender=:1.31 path=/MediaEndpoint/A2DPSource/aac
Feb 28 12:07:25 teo-vivobook bluetoothd[596]: Endpoint registered: sender=:1.31 path=/MediaEndpoint/A2DPSink/opus_g
Feb 28 12:07:25 teo-vivobook bluetoothd[596]: Endpoint registered: sender=:1.31 path=/MediaEndpoint/A2DPSource/opus_g
Feb 28 12:07:25 teo-vivobook bluetoothd[596]: Endpoint registered: sender=:1.31 path=/MediaEndpoint/A2DPSink/sbc
Feb 28 12:07:25 teo-vivobook bluetoothd[596]: Endpoint registered: sender=:1.31 path=/MediaEndpoint/A2DPSource/sbc
Feb 28 12:07:25 teo-vivobook bluetoothd[596]: Endpoint registered: sender=:1.31 path=/MediaEndpoint/A2DPSource/aptx_ll_1
Feb 28 12:07:25 teo-vivobook bluetoothd[596]: Endpoint registered: sender=:1.31 path=/MediaEndpoint/A2DPSource/aptx_ll_0
Feb 28 12:07:25 teo-vivobook bluetoothd[596]: Endpoint registered: sender=:1.31 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
Feb 28 12:07:25 teo-vivobook bluetoothd[596]: Endpoint registered: sender=:1.31 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
Feb 28 12:07:25 teo-vivobook bluetoothd[596]: Endpoint registered: sender=:1.31 path=/MediaEndpoint/A2DPSource/faststream
Feb 28 12:07:25 teo-vivobook bluetoothd[596]: Endpoint registered: sender=:1.31 path=/MediaEndpoint/A2DPSource/faststream_duplex
Feb 28 12:07:25 teo-vivobook bluetoothd[596]: Endpoint registered: sender=:1.31 path=/MediaEndpoint/A2DPSink/opus_05
Feb 28 12:07:25 teo-vivobook bluetoothd[596]: Endpoint registered: sender=:1.31 path=/MediaEndpoint/A2DPSource/opus_05
Feb 28 12:07:25 teo-vivobook bluetoothd[596]: Endpoint registered: sender=:1.31 path=/MediaEndpoint/A2DPSink/opus_05_duplex
Feb 28 12:07:25 teo-vivobook bluetoothd[596]: Endpoint registered: sender=:1.31 path=/MediaEndpoint/A2DPSource/opus_05_duplex
Feb 28 12:07:25 teo-vivobook wireplumber[817]: wp-device: SPA handle 'api.libcamera.enum.manager' could not be loaded; is it installed?
Feb 28 12:07:25 teo-vivobook wireplumber[817]: s-monitors-libcamera: PipeWire's libcamera SPA plugin is missing or broken. Some camera types may not be supported.
Feb 28 12:07:27 teo-vivobook bluetoothd[596]: src/profile.c:register_profile() :1.40 tried to register 0000111f-0000-1000-8000-00805f9b34fb which is already registered
Feb 28 12:07:27 teo-vivobook pulseaudio[880]: org.bluez.ProfileManager1.RegisterProfile() failed: org.bluez.Error.NotPermitted: UUID already registered
Feb 28 12:07:27 teo-vivobook bluetoothd[596]: Endpoint registered: sender=:1.40 path=/MediaEndpoint/A2DPSource/ldac_hq
Feb 28 12:07:27 teo-vivobook bluetoothd[596]: Endpoint registered: sender=:1.40 path=/MediaEndpoint/A2DPSource/ldac_sq
Feb 28 12:07:27 teo-vivobook bluetoothd[596]: Endpoint registered: sender=:1.40 path=/MediaEndpoint/A2DPSource/ldac_mq
Feb 28 12:07:27 teo-vivobook bluetoothd[596]: Endpoint registered: sender=:1.40 path=/MediaEndpoint/A2DPSink/aptx_hd
Feb 28 12:07:27 teo-vivobook bluetoothd[596]: Endpoint registered: sender=:1.40 path=/MediaEndpoint/A2DPSource/aptx_hd
Feb 28 12:07:27 teo-vivobook bluetoothd[596]: Endpoint registered: sender=:1.40 path=/MediaEndpoint/A2DPSink/aptx
Feb 28 12:07:27 teo-vivobook bluetoothd[596]: Endpoint registered: sender=:1.40 path=/MediaEndpoint/A2DPSource/aptx
Feb 28 12:07:27 teo-vivobook bluetoothd[596]: Endpoint registered: sender=:1.40 path=/MediaEndpoint/A2DPSink/sbc
Feb 28 12:07:27 teo-vivobook bluetoothd[596]: Endpoint registered: sender=:1.40 path=/MediaEndpoint/A2DPSource/sbc
Feb 28 12:07:27 teo-vivobook bluetoothd[596]: Endpoint registered: sender=:1.40 path=/MediaEndpoint/A2DPSink/sbc_xq_453
Feb 28 12:07:27 teo-vivobook bluetoothd[596]: Endpoint registered: sender=:1.40 path=/MediaEndpoint/A2DPSource/sbc_xq_453
Feb 28 12:07:27 teo-vivobook bluetoothd[596]: Endpoint registered: sender=:1.40 path=/MediaEndpoint/A2DPSink/sbc_xq_512
Feb 28 12:07:27 teo-vivobook bluetoothd[596]: Endpoint registered: sender=:1.40 path=/MediaEndpoint/A2DPSource/sbc_xq_512
Feb 28 12:07:27 teo-vivobook bluetoothd[596]: Endpoint registered: sender=:1.40 path=/MediaEndpoint/A2DPSink/sbc_xq_552
Feb 28 12:07:27 teo-vivobook bluetoothd[596]: Endpoint registered: sender=:1.40 path=/MediaEndpoint/A2DPSource/sbc_xq_552
Feb 28 12:07:27 teo-vivobook bluetoothd[596]: Endpoint registered: sender=:1.40 path=/MediaEndpoint/A2DPSink/faststream
Feb 28 12:07:27 teo-vivobook bluetoothd[596]: Endpoint registered: sender=:1.40 path=/MediaEndpoint/A2DPSource/faststream
Feb 28 12:07:27 teo-vivobook kded6[924]: kf.bluezqt: PendingCall Error: "The name is not activatable"
Feb 28 12:07:27 teo-vivobook NetworkManager[595]: <info> [1740740847.6335] device (wlo1): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "Sixty-Seven 5G"
Feb 28 12:07:28 teo-vivobook kernel: warning: `kdeconnectd' uses wireless extensions which will stop working for Wi-Fi 7 hardware; use nl80211
Feb 28 12:07:28 teo-vivobook wireplumber[817]: spa.bluez5.native: RFCOMM receive command but modem not available: AT+NREC=0
Feb 28 12:07:28 teo-vivobook pulseaudio[880]: Failed to open connection to session manager: None of the authentication protocols specified are supported
Feb 28 12:07:28 teo-vivobook pulseaudio[880]: Failed to load module "module-x11-xsmp" (argument: "display=:1 xauthority=/run/user/1000/xauth_fdrsku session_manager=local/teo-vivobook:@/tmp/.ICE-unix/922,unix/teo-vivobook:/tmp/.ICE-unix/922"): initialization failed.
Feb 28 12:07:28 teo-vivobook start-pulseaudio-x11[1401]: Failure: Module initialization failed
Feb 28 12:07:28 teo-vivobook systemd[709]: app-pulseaudio@autostart.service: Main process exited, code=exited, status=1/FAILURE
Feb 28 12:07:28 teo-vivobook systemd[709]: app-pulseaudio@autostart.service: Failed with result 'exit-code'.
Feb 28 12:22:42 teo-vivobook bluetoothd[596]: src/profile.c:ext_io_disconnected() Unable to get io data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected (107)
Feb 28 12:22:57 teo-vivobook systemsettings[2884]: qrc:/kcm/kcm_bluetooth/ForgetDeviceDialog.qml:35: TypeError: Cannot read property 'name' of null
Feb 28 12:22:57 teo-vivobook systemsettings[2884]: qrc:/kcm/kcm_bluetooth/ForgetDeviceDialog.qml:75: TypeError: Cannot read property 'adapter' of null
Feb 28 12:22:57 teo-vivobook systemsettings[2884]: qrc:/kcm/kcm_bluetooth/ForgetDeviceAction.qml:17: TypeError: Cannot read property 'name' of null
Feb 28 14:13:45 teo-vivobook bluetoothd[596]: Controller resume with wake event 0x0
Feb 28 14:13:50 teo-vivobook NetworkManager[595]: <info> [1740748430.1684] device (wlo1): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "Sixty-Seven 5G"
Feb 28 14:19:49 teo-vivobook bluetoothd[596]: No matching connection for device
Feb 28 14:19:51 teo-vivobook wireplumber[817]: spa.bluez5.native: RFCOMM receive command but modem not available: AT+NREC=0
Feb 28 14:19:51 teo-vivobook bluedevil-wizard[4072]: kf.notifications: Had queued notifications on destruction. Was the eventloop running?
Feb 28 14:19:51 teo-vivobook systemd[709]: app-org.kde.bluedevilwizard@b76141b5f9104e76b24ed87d1cea9bc6.service: Main process exited, code=exited, status=1/FAILURE
Feb 28 14:19:51 teo-vivobook systemd[709]: app-org.kde.bluedevilwizard@b76141b5f9104e76b24ed87d1cea9bc6.service: Failed with result 'exit-code'.
Feb 28 14:19:51 teo-vivobook systemd[709]: app-org.kde.bluedevilwizard@b76141b5f9104e76b24ed87d1cea9bc6.service: Consumed 1.148s CPU time, 27.7M memory peak.
Feb 28 14:22:13 teo-vivobook wireplumber[817]: wp-event-dispatcher: <WpAsyncEventHook:0x55f76b044f60> failed: <WpSiStandardLink:0x55f76b266c30> link failed: 1 of 1 PipeWire links failed to activate
Feb 28 14:22:13 teo-vivobook wireplumber[817]: wp-event-dispatcher: <WpAsyncEventHook:0x55f76b044f60> failed: <WpSiStandardLink:0x55f76b2aac60> link failed: 1 of 1 PipeWire links failed to activate
Feb 28 14:25:39 teo-vivobook wireplumber[817]: wp-event-dispatcher: <WpAsyncEventHook:0x55f76b044f60> failed: <WpSiStandardLink:0x55f76b11d5f0> link failed: some node was destroyed before the link was created
Feb 28 14:54:23 teo-vivobook wireplumber[817]: wp-event-dispatcher: <WpAsyncEventHook:0x55f76b044f60> failed: <WpSiStandardLink:0x55f76b0585a0> link failed: 1 of 1 PipeWire links failed to activate
Feb 28 14:54:23 teo-vivobook wireplumber[817]: wp-event-dispatcher: <WpAsyncEventHook:0x55f76b044f60> failed: <WpSiStandardLink:0x55f76af8f540> link failed: 1 of 1 PipeWire links failed to activate
Feb 28 14:54:23 teo-vivobook wireplumber[817]: wp-event-dispatcher: <WpAsyncEventHook:0x55f76b044f60> failed: <WpSiStandardLink:0x55f76b1fb8b0> link failed: 1 of 1 PipeWire links failed to activate
Feb 28 14:54:23 teo-vivobook wireplumber[817]: wp-event-dispatcher: <WpAsyncEventHook:0x55f76b044f60> failed: <WpSiStandardLink:0x55f76b1fc090> link failed: some node was destroyed before the link was created
Feb 28 14:54:24 teo-vivobook wireplumber[817]: wp-event-dispatcher: <WpAsyncEventHook:0x55f76b044f60> failed: <WpSiStandardLink:0x55f76b25dbe0> link failed: some node was destroyed before the link was created
Feb 28 14:55:19 teo-vivobook spectacle[6418]: kpipewire_vaapi_logging: VAAPI: Failed to initialize display
Feb 28 14:55:19 teo-vivobook spectacle[6418]: kpipewire_vaapi_logging: DRM device not found
Feb 28 14:57:34 teo-vivobook spectacle[6520]: kpipewire_vaapi_logging: VAAPI: Failed to initialize display
Feb 28 14:57:34 teo-vivobook spectacle[6520]: kpipewire_vaapi_logging: DRM device not found
Feb 28 14:58:25 teo-vivobook spectacle[6576]: kpipewire_vaapi_logging: VAAPI: Failed to initialize display
Feb 28 14:58:25 teo-vivobook spectacle[6576]: kpipewire_vaapi_logging: DRM device not found
Feb 28 14:59:04 teo-vivobook spectacle[6625]: kpipewire_vaapi_logging: VAAPI: Failed to initialize display
Feb 28 14:59:04 teo-vivobook spectacle[6625]: kpipewire_vaapi_logging: DRM device not found
Feb 28 15:05:27 teo-vivobook wireplumber[817]: wp-event-dispatcher: <WpAsyncEventHook:0x55f76b044f60> failed: <WpSiStandardLink:0x55f76b1009b0> link failed: 1 of 1 PipeWire links failed to activate
Feb 28 15:09:13 teo-vivobook bluetoothd[596]: src/profile.c:ext_io_disconnected() Unable to get io data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected (107)
Feb 28 16:07:32 teo-vivobook bluetoothd[596]: Controller resume with wake event 0x0
Feb 28 16:07:35 teo-vivobook NetworkManager[595]: <info> [1740755255.8964] device (wlo1): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "Sixty-Seven 5G"
Feb 28 16:16:54 teo-vivobook spectacle[7756]: kpipewire_vaapi_logging: VAAPI: Failed to initialize display
Feb 28 16:16:54 teo-vivobook spectacle[7756]: kpipewire_vaapi_logging: DRM device not found
Feb 28 16:17:05 teo-vivobook spectacle[7795]: kpipewire_vaapi_logging: VAAPI: Failed to initialize display
Feb 28 16:17:05 teo-vivobook spectacle[7795]: kpipewire_vaapi_logging: DRM device not found
Feb 28 16:17:49 teo-vivobook bluetoothd[596]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Connection refused
Feb 28 16:17:49 teo-vivobook bluetoothd[596]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 94:4B:F8:47:2A:B4: Connection refused (111)
Feb 28 16:17:49 teo-vivobook plasmashell[964]: kf.bluezqt: PendingCall Error: "br-connection-refused"
Feb 28 16:18:02 teo-vivobook wireplumber[817]: spa.bluez5.native: RFCOMM receive command but modem not available: AT+NREC=0
Feb 28 16:18:58 teo-vivobook systemd[709]: app-org.pulseaudio.pavucontrol@e4824f7f5d22497087f81ff91c8b0ac2.service: Consumed 6.998s CPU time, 71.5M memory peak.
Feb 28 16:20:01 teo-vivobook wireplumber[817]: wp-event-dispatcher: <WpAsyncEventHook:0x55f76b044f60> failed: <WpSiStandardLink:0x55f76b09c030> link failed: 1 of 1 PipeWire links failed to activate
Feb 28 16:20:01 teo-vivobook wireplumber[817]: wp-event-dispatcher: <WpAsyncEventHook:0x55f76b044f60> failed: <WpSiStandardLink:0x55f76b1fb530> link failed: 1 of 1 PipeWire links failed to activate
Feb 28 16:22:16 teo-vivobook wireplumber[817]: wp-event-dispatcher: <WpAsyncEventHook:0x55f76b044f60> failed: <WpSiStandardLink:0x55f76b25b9b0> link failed: 1 of 1 PipeWire links failed to activate
Feb 28 17:14:50 teo-vivobook wireplumber[817]: wp-event-dispatcher: <WpAsyncEventHook:0x55f76b044f60> failed: <WpSiStandardLink:0x55f76b017890> link failed: 1 of 1 PipeWire links failed to activate
Feb 28 17:16:06 teo-vivobook wireplumber[817]: wp-event-dispatcher: <WpAsyncEventHook:0x55f76b044f60> failed: <WpSiStandardLink:0x55f76af87530> link failed: 1 of 1 PipeWire links failed to activate
Feb 28 17:18:14 teo-vivobook wireplumber[817]: wp-event-dispatcher: <WpAsyncEventHook:0x55f76b044f60> failed: <WpSiStandardLink:0x55f76b103ba0> link failed: 1 of 1 PipeWire links failed to activate
Feb 28 17:27:17 teo-vivobook wireplumber[817]: wp-event-dispatcher: <WpAsyncEventHook:0x55f76b044f60> failed: <WpSiStandardLink:0x55f76b098c10> link failed: 1 of 1 PipeWire links failed to activate
Feb 28 17:56:47 teo-vivobook spectacle[12991]: kpipewire_vaapi_logging: VAAPI: Failed to initialize display
Feb 28 17:56:47 teo-vivobook spectacle[12991]: kpipewire_vaapi_logging: DRM device not found
Feb 28 17:58:08 teo-vivobook wireplumber[817]: wp-event-dispatcher: <WpAsyncEventHook:0x55f76b0510f0> failed: failed to activate item: Object activation aborted: proxy destroyed
Feb 28 18:00:17 teo-vivobook spectacle[13153]: kpipewire_vaapi_logging: VAAPI: Failed to initialize display
Feb 28 18:00:17 teo-vivobook spectacle[13153]: kpipewire_vaapi_logging: DRM device not found
Feb 28 18:10:11 teo-vivobook bluetoothd[596]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
Feb 28 18:10:11 teo-vivobook plasmashell[964]: kf.bluezqt: PendingCall Error: "br-connection-page-timeout"
Feb 28 18:10:22 teo-vivobook bluetoothd[596]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
Feb 28 18:10:22 teo-vivobook plasmashell[964]: kf.bluezqt: PendingCall Error: "br-connection-page-timeout"
Feb 28 18:10:37 teo-vivobook wireplumber[817]: spa.bluez5.native: RFCOMM receive command but modem not available: AT+NREC=0
Feb 28 18:11:35 teo-vivobook wireplumber[817]: wp-event-dispatcher: <WpAsyncEventHook:0x55f76b044f60> failed: <WpSiStandardLink:0x55f76b0b1e10> link failed: some node was destroyed before the link was created
Feb 28 18:12:38 teo-vivobook bluetoothd[596]: No matching connection for device
Feb 28 18:12:49 teo-vivobook wireplumber[817]: wp-event-dispatcher: <WpAsyncEventHook:0x55f76b044f60> failed: <WpSiStandardLink:0x55f76b15f850> link failed: 1 of 1 PipeWire links failed to activate
Feb 28 18:21:25 teo-vivobook wireplumber[817]: wp-event-dispatcher: <WpAsyncEventHook:0x55f76b044f60> failed: <WpSiStandardLink:0x55f76b082e80> link failed: 1 of 1 PipeWire links failed to activate
Feb 28 18:21:36 teo-vivobook spectacle[13688]: kpipewire_vaapi_logging: VAAPI: Failed to initialize display
Feb 28 18:21:36 teo-vivobook spectacle[13688]: kpipewire_vaapi_logging: DRM device not found
Feb 28 18:21:44 teo-vivobook wireplumber[817]: wp-event-dispatcher: <WpAsyncEventHook:0x55f76b044f60> failed: <WpSiStandardLink:0x55f76b0be080> link failed: 1 of 1 PipeWire links failed to activate
Feb 28 18:21:44 teo-vivobook wireplumber[817]: wp-event-dispatcher: <WpAsyncEventHook:0x55f76b044f60> failed: <WpSiStandardLink:0x55f76afd6e20> link failed: 1 of 1 PipeWire links failed to activate
Feb 28 18:26:17 teo-vivobook wireplumber[817]: wp-event-dispatcher: <WpAsyncEventHook:0x55f76b044f60> failed: <WpSiStandardLink:0x55f76b098600> link failed: 1 of 1 PipeWire links failed to activate
Feb 28 18:29:18 teo-vivobook wireplumber[817]: wp-event-dispatcher: <WpAsyncEventHook:0x55f76b044f60> failed: <WpSiStandardLink:0x55f76afd6e00> link failed: 1 of 1 PipeWire links failed to activate
Feb 28 18:34:21 teo-vivobook wireplumber[817]: wp-event-dispatcher: <WpAsyncEventHook:0x55f76b044f60> failed: <WpSiStandardLink:0x55f76b1b36e0> link failed: some node was destroyed before the link was created
Feb 28 18:41:34 teo-vivobook wireplumber[817]: wp-event-dispatcher: <WpAsyncEventHook:0x55f76b044f60> failed: <WpSiStandardLink:0x55f76b165c30> link failed: 1 of 1 PipeWire links failed to activate
Feb 28 18:41:36 teo-vivobook wireplumber[817]: wp-event-dispatcher: <WpAsyncEventHook:0x55f76b044f60> failed: <WpSiStandardLink:0x55f76af8add0> link failed: 1 of 1 PipeWire links failed to activate
Feb 28 19:06:00 teo-vivobook wireplumber[817]: wp-event-dispatcher: <WpAsyncEventHook:0x55f76b044f60> failed: <WpSiStandardLink:0x55f76b25b330> link failed: 1 of 1 PipeWire links failed to activate
Feb 28 19:06:00 teo-vivobook wireplumber[817]: wp-event-dispatcher: <WpAsyncEventHook:0x55f76b044f60> failed: <WpSiStandardLink:0x55f76b250dc0> link failed: 1 of 1 PipeWire links failed to activate
Feb 28 19:06:01 teo-vivobook wireplumber[817]: wp-event-dispatcher: <WpAsyncEventHook:0x55f76b044f60> failed: <WpSiStandardLink:0x55f76b0584c0> link failed: 1 of 1 PipeWire links failed to activate
Feb 28 19:10:29 teo-vivobook wireplumber[817]: wp-event-dispatcher: <WpAsyncEventHook:0x55f76b044f60> failed: <WpSiStandardLink:0x55f76b05ca30> link failed: 1 of 1 PipeWire links failed to activate
Feb 28 19:13:07 teo-vivobook wireplumber[817]: wp-event-dispatcher: <WpAsyncEventHook:0x55f76b044f60> failed: <WpSiStandardLink:0x55f76b153150> link failed: some node was destroyed before the link was created
Feb 28 19:18:20 teo-vivobook wireplumber[817]: wp-event-dispatcher: <WpAsyncEventHook:0x55f76b044f60> failed: <WpSiStandardLink:0x55f76af94a90> link failed: 1 of 1 PipeWire links failed to activate
Feb 28 19:42:48 teo-vivobook wireplumber[817]: wp-event-dispatcher: <WpAsyncEventHook:0x55f76b044f60> failed: <WpSiStandardLink:0x55f76b1a8490> link failed: some node was destroyed before the link was created
Feb 28 19:44:24 teo-vivobook wireplumber[817]: wp-event-dispatcher: <WpAsyncEventHook:0x55f76b044f60> failed: <WpSiStandardLink:0x55f76b25dbe0> link failed: some node was destroyed before the link was created
Feb 28 19:44:46 teo-vivobook wireplumber[817]: wp-event-dispatcher: <WpAsyncEventHook:0x55f76b044f60> failed: <WpSiStandardLink:0x55f76b00db70> link failed: 1 of 1 PipeWire links failed to activate
Feb 28 19:48:56 teo-vivobook wireplumber[817]: wp-event-dispatcher: <WpAsyncEventHook:0x55f76b044f60> failed: <WpSiStandardLink:0x55f76b01a8c0> link failed: 1 of 1 PipeWire links failed to activate
Feb 28 19:51:34 teo-vivobook wireplumber[817]: wp-event-dispatcher: <WpAsyncEventHook:0x55f76b044f60> failed: <WpSiStandardLink:0x55f76b24b880> link failed: 1 of 1 PipeWire links failed to activate
Feb 28 19:52:55 teo-vivobook wireplumber[817]: wp-event-dispatcher: <WpAsyncEventHook:0x55f76b044f60> failed: <WpSiStandardLink:0x55f76b1791c0> link failed: 1 of 1 PipeWire links failed to activate
Feb 28 19:53:58 teo-vivobook wireplumber[817]: wp-event-dispatcher: <WpAsyncEventHook:0x55f76b044f60> failed: <WpSiStandardLink:0x55f76b25dbe0> link failed: 1 of 1 PipeWire links failed to activate
Feb 28 19:58:38 teo-vivobook spectacle[17738]: kpipewire_vaapi_logging: VAAPI: Failed to initialize display
Feb 28 19:58:38 teo-vivobook spectacle[17738]: kpipewire_vaapi_logging: DRM device not found
Feb 28 19:58:55 teo-vivobook spectacle[17788]: kpipewire_vaapi_logging: VAAPI: Failed to initialize display
Feb 28 19:58:55 teo-vivobook spectacle[17788]: kpipewire_vaapi_logging: DRM device not found
Feb 28 20:04:03 teo-vivobook wireplumber[817]: wp-event-dispatcher: <WpAsyncEventHook:0x55f76b044f60> failed: <WpSiStandardLink:0x55f76b05ca30> link failed: 1 of 1 PipeWire links failed to activate
Feb 28 20:04:08 teo-vivobook wireplumber[817]: wp-event-dispatcher: <WpAsyncEventHook:0x55f76b044f60> failed: <WpSiStandardLink:0x55f76b103ba0> link failed: 1 of 1 PipeWire links failed to activate
Feb 28 20:04:10 teo-vivobook wireplumber[817]: wp-event-dispatcher: <WpAsyncEventHook:0x55f76b044f60> failed: <WpSiStandardLink:0x55f76af92660> link failed: 1 of 1 PipeWire links failed to activate
Feb 28 20:04:51 teo-vivobook wireplumber[817]: wp-event-dispatcher: <WpAsyncEventHook:0x55f76b044f60> failed: <WpSiStandardLink:0x55f76afd6e00> link failed: 1 of 1 PipeWire links failed to activate
Feb 28 20:04:56 teo-vivobook wireplumber[817]: spa.bluez5.native: RFCOMM receive command but modem not available: AT+NREC=0
Feb 28 20:04:58 teo-vivobook bluetoothd[596]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 94:4B:F8:47:2A:B4: Device or resource busy
Feb 28 20:05:08 teo-vivobook bluetoothd[596]: profiles/audio/avdtp.c:cancel_request() Discover: Connection timed out (110)
Feb 28 20:05:21 teo-vivobook bluetoothd[596]: src/profile.c:ext_io_disconnected() Unable to get io data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected (107)
Feb 28 20:05:27 teo-vivobook bluetoothd[596]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
Feb 28 20:05:34 teo-vivobook bluetoothd[596]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
Feb 28 20:05:43 teo-vivobook bluetoothd[596]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
Feb 28 20:05:57 teo-vivobook bluetoothd[596]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
Feb 28 20:06:19 teo-vivobook bluetoothd[596]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
Feb 28 20:06:57 teo-vivobook bluetoothd[596]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
Feb 28 20:08:07 teo-vivobook bluetoothd[596]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
Feb 28 20:15:55 teo-vivobook wireplumber[817]: spa.bluez5.native: RFCOMM receive command but modem not available: AT+NREC=0
Feb 28 20:15:57 teo-vivobook bluetoothd[596]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 94:4B:F8:47:2A:B4: Device or resource busy
Feb 28 20:16:43 teo-vivobook bluetoothd[596]: src/profile.c:ext_io_disconnected() Unable to get io data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected (107)
Feb 28 21:56:23 teo-vivobook bluetoothd[596]: Controller resume with wake event 0x0
Feb 28 21:56:26 teo-vivobook NetworkManager[595]: <info> [1740776186.6411] device (wlo1): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "Sixty-Seven 5G"
Mar 01 18:34:05 teo-vivobook bluetoothd[596]: Controller resume with wake event 0x0
Mar 01 18:34:09 teo-vivobook NetworkManager[595]: <info> [1740850449.2703] device (wlo1): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "Sixty-Seven 5G"
Mar 01 18:42:25 teo-vivobook wireplumber[817]: wp-event-dispatcher: <WpAsyncEventHook:0x55f76b044f60> failed: <WpSiStandardLink:0x55f76b150920> link failed: some node was destroyed before the link was created
Mar 01 18:50:26 teo-vivobook wireplumber[817]: spa.bluez5.native: RFCOMM receive command but modem not available: AT+NREC=0
I have now installed manjaro-pipewire (I had to remove a couple of packages that I had installed related to Jack) and that has fixed the issue. After restart (I did have to restart though, despite the fact that Pamac didnât tell me a restart was needed - where should I report that bug?) the earbuds connected automatically, sound output automatically switched to them and they are visible in the volume settings, everything as expected.
It seems that this has happened to basically everybody who has had similar problems.
If I understand correctly, however, this shouldnât be necessary in order to have bluetooth audio working, right?
Tell me if I understand correctly:
pulseaudio and pipewire can coexist, and they do by default in Manjaro+KDE, where pulseaudio acts as a sound server and pipewire acts as a media server, whatever that means.
Thereâs a common misconception that they are not supposed to be installed together but thatâs not true
pipewire can however replace pulseaudio (and thatâs what installing manjaro-pipewire does)
Manjaroâs default combination of pulseaudio+pipewire is supposed to support bluetooth audio, right? (*).
(*) If so, itâs utterly broken. Are the Manjaro maintainers aware of that?
Since we released Uranos in October 2023 we worked hard to get the next release of Manjaro out there. We call it Vulcan. This is also our first release on which we switch over to Pipewire 1.0.
Restart is not necessary if pipewire-pulse.service is started, but service is started automatically if system is restarted
ALSA clients
Install pipewire-alsa (and remove pulseaudio-alsa if it was installed) to route all applications using the ALSA API through PipeWire.
PulseAudio clients
Install pipewire-pulse. It will replace pulseaudio and pulseaudio-bluetooth.
Reboot, re-login or stop pulseaudio.service and start the pipewire-pulse.serviceuser unit to see the effect.
Bluetooth devices
PipeWire handles Bluetooth audio devices if the pipewire-audio package is installed.
Data in post #5 shows pipewire-alsa installed to replace pulseaudio-alsa,
but pipewire-pulse not installed to replace pulseaudio