Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Pipewire broken after connecting to a bluetooth sink

Fixed

Description

During the regular test run for master after pairing and connecting to a bluetooth device Pipewire ceases operation and becomes stuck, unable to output any playback.

Radio, navigation and local media playback are running fine prior to connecting a bluetooth device.

Prior to connecting a bluetooth device "wpctl status" reports as usual :

root@h3ulcb:~# wpctl status PipeWire 'pipewire-0' [0.3.67, pipewire@h3ulcb, cookie:2413324545]  └─ Clients:         30. WirePlumber Bluetooth               [0.3.67, pipewire@h3ulcb, pid:666]         31. WirePlumber                         [0.3.67, pipewire@h3ulcb, pid:665]         32. WirePlumber [export]                [0.3.67, pipewire@h3ulcb, pid:665]         34. WirePlumber Policy                  [0.3.67, pipewire@h3ulcb, pid:667]        121. agl-service-audiomixer              [0.3.67, root@h3ulcb, pid:717]        122. wpctl                               [0.3.67, root@h3ulcb, pid:873]Audio  ├─ Devices:  │      35. Built-in Audio                      [alsa:pcm]  │    ├─ Sinks:  │  *   36. Built-in Audio                      [vol: 1.00]  │      38. Built-in Audio (rsnd-dai.1-i2s-hifi i2s-hifi-1) [vol: 1.00]  │      39. Speech-High Playback Endpoint       [vol: 1.00]  │      40. Speech-Low Playback Endpoint        [vol: 1.00]  │      41. Custom-Low Playback Endpoint        [vol: 1.00]  │      42. Multimedia Playback Endpoint        [vol: 1.00]  │      43. Custom-High Playback Endpoint       [vol: 1.00]  │      45. Communication Playback Endpoint     [vol: 1.00]  │      46. Navigation Playback Endpoint        [vol: 1.00]  │      47. Emergency Playback Endpoint         [vol: 1.00]  │    ├─ Sink endpoints:  â      48. Playback: Speech-High               [vol: 1.00]  │      49. Playback: Speech-Low                [vol: 1.00]  │      50. Playback: Custom-Low                [vol: 1.00]  │      51. Playback: Multimedia                [vol: 1.00]  │      52. Playback: Custom-High               [vol: 1.00]  │      54. Playback: Communication             [vol: 1.00]  │      55. Playback: Navigation                [vol: 1.00]  │      56. Playback: Emergency                 [vol: 1.00]  │    ├─ Sources:  │  *   37. Built-in Audio                      [vol: 1.00]  │      44. Capture Capture Endpoint            [vol: 1.00]  │    ├─ Source endpoints:  │      53. Capture: Capture                    [vol: 1.00]  │    └─ Streams:Video  ├─ Devices:  │    ├─ Sinks:  │    ├─ Sink endpoints:  │    ├─ Sources:  │    ├─ Source endpoints:  │    └─ Streams:Settings  └─ Default Configured Node Names:

After connecting a device over bluetooth, "wpctl status" hangs indefinitely.

An excerpt is attached from a rolling journal taken prior connecting to a bluetooth device.

 

Environment

None

Attachments

2

Activity

Show:

Walt Miner 
May 11, 2023 at 3:49 PM

Close for OO 15.0.1

Ashok Sidipotu 
April 13, 2023 at 4:36 PM

Ashok Sidipotu 
April 7, 2023 at 9:07 AM

I took out the build that I tested on and first time the bt pairing went through but on repeated attemps the pipewire is hanging. Thanks I will check this forward in my env.

Edi Feschiyan 
April 7, 2023 at 7:06 AM
(edited)

You might consider updating the software on your workstation - the certificates bundle in particular, revising your browser certificate list &| browser version or trying another browser overall.

You should be able to download the images via 

h3-kf builds : wget --no-check-certificate https://transfer.sh/get/IuEPr0/agl-demo-platform-h3ulcb-kf-20230405094128.rootfs.wic.xz

h3-refhw : wget --no-check-certificate https://transfer.sh/get/PuWaxw/agl-demo-platform-h3ulcb-20230405101252.rootfs.wic.xz

Ashok Sidipotu 
April 7, 2023 at 1:31 AM

Hi Edi,

I think I've AGL reference hardware board based on [table|https://docs.automotivelinux.org/en/octopus/#01_Getting_Started/02_Building_AGL_Image/09_Building_for_Supported_Renesas_Boards/#14-making-sure-your-build-environment-is-correct] and I tested it there by connecting the external BT dongle.

Is it possible to point me to the corresponding image for this hardware?

The image that you gave was not accessible to me, browser threw the following error, is there a way around this?

Details

Assignee

Reporter

Fix versions

Labels

Contract ID

Components

Affects versions

Priority

Created April 6, 2023 at 11:04 AM
Updated May 11, 2023 at 3:49 PM
Resolved May 10, 2023 at 8:27 PM

Flag notifications