[SOLVED] pipewire-1.0.1 bluetooth problem

rizitis · 02-02-2024, 09:47 AM

I just builded and install it using slackware stock scripts, still having the same issue

marav · 02-02-2024, 11:04 AM

Quote:

Originally Posted by rizitis

I just builded and install it using slackware stock scripts, still having the same issue

And are you 100% sure that your issue is pipewire related?

rizitis · 02-03-2024, 01:57 AM

I m never 100% sure for something...
For sure I m not sure about my build, maybe when Pat build it will work, i hope...
What we have is pipewire-1.0.0 working 100% and all versions after that not working at all.
Its not only an issue in my end but in several users for slackware-current and fedora, as I found in google searching.
The problem I think is this:

Code:

- Fix ALSA version check. This should allow the alsa plugin to work again.

Which means that ether my build was not ok, which I hope, or they didnt fix it...
I will try rebuild again today following https://gitlab.freedesktop.org/pipew...releases/1.0.3 to see if something change or if I can found something...

EDIT: they say

Code:

    PipeWire 1.0.3 (2024-02-02)

    This is a quick bugfix release that is API and ABI compatible with previous 1.0.x releases.

    Highlights

    Fix ALSA version check. This should allow the alsa plugin to work again.

    Some small fixes and improvements.

    PipeWire

    Escape DEFAULT_SINK in the conf files.

    Modules

    Improve logging in module-pipe-tunnel.

    SPA

    Always recheck rate matching in ALSA when moving drivers. This fixes a potential issue where the adaptive resampler would not be activated in some cases.

    ALSA

    Fix version check. This should allow the alsa plugin to work again with version 1.0.2.

That supposed that previous version should worked.. so actually I dont think its the fix for this issue

murdo · 02-03-2024, 05:35 AM

Oddly, 1.0.3 appears to have fixed my issue. I'm running it right now with no problems.

@rizitis my hardware info is as follows:

Code:

bash-5.2$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: HDMI [HDA ATI HDMI], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: HDMI [HDA ATI HDMI], device 7: HDMI 1 [HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: HDMI [HDA ATI HDMI], device 8: HDMI 2 [HDMI 2]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: HDMI [HDA ATI HDMI], device 9: HDMI 3 [HDMI 3]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: HDMI [HDA ATI HDMI], device 10: HDMI 4 [HDMI 4]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: Generic [HD-Audio Generic], device 0: ALC1220 Analog [ALC1220 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: Generic [HD-Audio Generic], device 1: ALC1220 Digital [ALC1220 Digital]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 2: AT2020USB [AT2020USB+], device 0: USB Audio [USB Audio]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
bash-5.2$ lspci | grep -i audio
09:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Navi 21/23 HDMI/DP Audio Controller
0b:00.4 Audio device: Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD Audio Controller
bash-5.2$ cat /proc/asound/modules
 0 snd_hda_intel
 1 snd_hda_intel
 2 snd_usb_audio
 3 snd_usb_audio
bash-5.2$ cat /proc/asound/cards
 0 [HDMI           ]: HDA-Intel - HDA ATI HDMI
                      HDA ATI HDMI at 0xfca20000 irq 84
 1 [Generic        ]: HDA-Intel - HD-Audio Generic
                      HD-Audio Generic at 0xfc800000 irq 86
 2 [AT2020USB      ]: USB-Audio - AT2020USB+
                      audio-technica AT2020USB+ at usb-0000:0b:00.3-1, full speed
 3 [Camera         ]: USB-Audio - USB 2.0 Camera
                      Sonix Technology Co., Ltd. USB 2.0 Camera at usb-0000:0b:00.3-4.2, high speed

Possibly a difference there could be the reason 1.0.3 works for me but not you?

rizitis · 02-03-2024, 10:50 AM

Ok just update my system and sound works!

alex14641 · 02-03-2024, 04:09 PM

Quote:

Originally Posted by mistfire

Yes. Im using XFCE. Sorry for my previous output that's wrong output. Here is correct one

Code:

2002 pipewire-pulse
2092 /usr/lib64/xfce4/panel/wrapper-2.0 /usr/lib64/xfce4/panel/plugins/libpulseaudio-plugin.so 7 20971532 pulseaudio PulseAudio Plugin Adjust the audio volume of the PulseAudio sound system
2146 /usr/bin/python3 /usr/bin/blueman-applet
2439 /usr/bin/python3 /usr/libexec/blueman-mechanism
2446 /usr/libexec/bluetooth/obexd
2448 /usr/bin/python3 /usr/bin/blueman-tray
9131 /usr/sbin/bluetoothd

@mistfire,

How is blueman-mechanism being started on your system? If I understand correctly, that's only supposed to be started on a SystemD distro.

mistfire · 02-03-2024, 11:05 PM

Hello, It seems I finally find a breakthrough. I Installed the latest pipewire version 1.0.3, however I downgraded the wireplumber by extracting the wireplumber from pipewire-1.0.0 slackware package, and replace the wireplumber files installed by pipewire 1.0.3, and I successfully connected to a bluetooth device with latest pipewire version. Then I reverted the wireplumber from the stock pipewire-1.0.3, the bluetooth device failed to connect. I wonder how to debug the latest wireplumber version included in pipewire-1.0.1 onwards in order to find why it unable to connect on bluetooth.

I compared logs made by wireplumber-0.4.16 (from pipewire 1.0.0) and wireplumber-0.4.81 (from pipewire 1.0.3). I found that this log was present on version 0.4.16 but missing in 0.4.81 when the wireplumber was started but bluetoothd was turned off

Code:

W 13:12:18.420200         spa.bluez5 ../spa/plugins/bluez5/bluez5-dbus.c:5332:get_managed_objects_reply: GetManagedObjects() failed: org.freedesktop.DBus.Error.NameHasNoOwner

mistfire · 02-07-2024, 08:25 AM

SOLUTION FOUND!

The culprit why bluetooth devices does not work on pipewire is because of wireplumber 0.4.81, That wireplumber version looks for active logind session in order to make the bluetooth work. If the logind/elogind was not active, the bluetooth wont work. It order to make it work without active session, you need to put a wireplumber conf file on /etc/pipewire/wireplumber.conf.d/<filename>.conf that contain this configuration

Code:

wireplumber.profiles = {
  main = {
    monitor.bluez.seat-monitoring = disabled
  }
}

Then restart the wireplumber

source: https://gitlab.freedesktop.org/pipew.../-/issues/3828

volkerdi · 02-07-2024, 01:22 PM

Quote:

Originally Posted by mistfire

SOLUTION FOUND!

The culprit why bluetooth devices does not work on pipewire is because of wireplumber 0.4.81, That wireplumber version looks for active logind session in order to make the bluetooth work. If the logind/elogind was not active, the bluetooth wont work. It order to make it work without active session, you need to put a wireplumber conf file on /etc/pipewire/wireplumber.conf.d/<filename>.conf that contain this configuration

Code:

wireplumber.profiles = {
  main = {
    monitor.bluez.seat-monitoring = disabled
  }
}

Then restart the wireplumber

source: https://gitlab.freedesktop.org/pipew.../-/issues/3828

Wow, thanks very much for this!

Not sure why upstream said that "Also, slackware probably should not have 0.4.81 in the first place, as it's supposed to be 0.5 prerelease."... pipewire will pull wireplumber from git if it's not available under the subprojects directory, and it pulls git HEAD just like my fetch-wireplumber script does.

Qury · 02-08-2024, 02:25 PM

Quote:

Originally Posted by mistfire

SOLUTION FOUND!

The culprit why bluetooth devices does not work on pipewire is because of wireplumber 0.4.81, That wireplumber version looks for active logind session in order to make the bluetooth work. If the logind/elogind was not active, the bluetooth wont work. It order to make it work without active session, you need to put a wireplumber conf file on /etc/pipewire/wireplumber.conf.d/<filename>.conf that contain this configuration

Code:

wireplumber.profiles = {
  main = {
    monitor.bluez.seat-monitoring = disabled
  }
}

Then restart the wireplumber

source: https://gitlab.freedesktop.org/pipew.../-/issues/3828

Works nicely with my GOJI GTCNCTW22 headphones!!
Thanks for this!