LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
Reload this Page [SOLVED] pipewire-1.0.1 bluetooth problem
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
Page 2 of 3 1 2 3
  Search this Thread
Old 01-29-2024, 06:36 PM   #16
alex14641
Member
 
Registered: Feb 2016
Distribution: Slackware64_14.2, Slackware 15.0, Slackware64_current
Posts: 324

Rep: Reputation: Disabled

@mistfire

Please post output from
Code:
pgrep -af '/daemon|blue|pulse'
 
Old 01-29-2024, 06:45 PM   #17
mistfire
Member
 
Registered: Jun 2021
Posts: 45

Original Poster
Rep: Reputation: Disabled
@alex14641

here is the output

Code:
3138 /usr/lib64/xfce4/panel/wrapper-2.0 /usr/lib64/xfce4/panel/plugins/libpulseaudio-plugin.so 7 16777228 pulseaudio PulseAudio Plugin Adjust the audio volume of the PulseAudio sound system
3191 /usr/bin/python3 /usr/bin/blueman-applet
3500 /usr/libexec/bluetooth/obexd
3502 /usr/bin/python3 /usr/bin/blueman-tray
9131 /usr/sbin/bluetoothd
I installed the second rebuilt of pipewire-1.0.1 still the same error that I encountered
Last edited by mistfire; 01-29-2024 at 06:46 PM.
 
Old 01-29-2024, 07:15 PM   #18
alex14641
Member
 
Registered: Feb 2016
Distribution: Slackware64_14.2, Slackware 15.0, Slackware64_current
Posts: 324

Rep: Reputation: Disabled
Strange. I get
Code:
1309 /usr/sbin/bluetoothd
1731 /usr/bin/daemon -frB --pidfiles=~/.run --name=pipewire /usr/bin/pipewire
1737 /usr/bin/python3 /usr/bin/blueman-applet
1750 /usr/bin/daemon -frB --pidfiles=~/.run --name=wireplumber /usr/bin/wireplumber
1758 /usr/bin/daemon -frB --pidfiles=~/.run --name=pipewire-pulse /usr/bin/pipewire-pulse
1761 pipewire-pulse: /usr/bin/pipewire-pulse
1893 /usr/libexec/bluetooth/obexd
1897 /usr/bin/python3 /usr/bin/blueman-tray
Are you in a graphical session?
 
Old 01-29-2024, 07:30 PM   #19
mistfire
Member
 
Registered: Jun 2021
Posts: 45

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by alex14641 View Post
Strange. I get
Code:
1309 /usr/sbin/bluetoothd
1731 /usr/bin/daemon -frB --pidfiles=~/.run --name=pipewire /usr/bin/pipewire
1737 /usr/bin/python3 /usr/bin/blueman-applet
1750 /usr/bin/daemon -frB --pidfiles=~/.run --name=wireplumber /usr/bin/wireplumber
1758 /usr/bin/daemon -frB --pidfiles=~/.run --name=pipewire-pulse /usr/bin/pipewire-pulse
1761 pipewire-pulse: /usr/bin/pipewire-pulse
1893 /usr/libexec/bluetooth/obexd
1897 /usr/bin/python3 /usr/bin/blueman-tray
Are you in a graphical session?
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
 
Old 01-29-2024, 08:03 PM   #20
alex14641
Member
 
Registered: Feb 2016
Distribution: Slackware64_14.2, Slackware 15.0, Slackware64_current
Posts: 324

Rep: Reputation: Disabled
I don't see the pipewire or wireplumber daemons. Also it looks like bluetoothd was started after everything else. What is starting blueman-mechanism?
 
Old 01-29-2024, 08:50 PM   #21
mistfire
Member
 
Registered: Jun 2021
Posts: 45

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by alex14641 View Post
I don't see the pipewire or wireplumber daemons.
wireplumber was running directly. Not under daemon
bluetoothd was running on bootup as sysvinit service

I restarted bluetoothd but still the same error message when connecting to a bluetooth device
 
Old 01-30-2024, 12:17 PM   #22
rizitis
Member
Contributing Member
 
Registered: Mar 2009
Location: Greece,Crete
Distribution: Slackware64-current, Slint
Posts: 722
Blog Entries: 2

Rep: Reputation: 533Reputation: 533Reputation: 533Reputation: 533Reputation: 533Reputation: 533
I found in fedora forum same issues, it looks like a wireplumber/piperwire driver issue, so we may have to wait for the fix they said...
We affected from this bug for me solution is pulse or downgrade pipewire.
Last edited by rizitis; 01-30-2024 at 12:20 PM.
 
Old 01-30-2024, 06:48 PM   #23
alex14641
Member
 
Registered: Feb 2016
Distribution: Slackware64_14.2, Slackware 15.0, Slackware64_current
Posts: 324

Rep: Reputation: Disabled
@mistfire,

Try this:

Shut down bluetooth:
Code:
/etc/rc.d/rc.bluetooth stop
Stop pipewire and wireplumber.

Then

Start bluetoothd
Code:
/etc/rc.d/rc.bluetooth start
then in this order, pipewire and wireplumber
 
Old 01-31-2024, 05:28 PM   #24
mistfire
Member
 
Registered: Jun 2021
Posts: 45

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by alex14641 View Post
@mistfire,

Try this:

Shut down bluetooth:
Code:
/etc/rc.d/rc.bluetooth stop
Stop pipewire and wireplumber.

Then

Start bluetoothd
Code:
/etc/rc.d/rc.bluetooth start
then in this order, pipewire and wireplumber
I tried that and still doesn't work. Also I tried to run pipewire and wireplumber them in debug mode and still doesn't show the root cause why bluetooth device does not connect with pipewire
 
Old 01-31-2024, 07:03 PM   #25
alex14641
Member
 
Registered: Feb 2016
Distribution: Slackware64_14.2, Slackware 15.0, Slackware64_current
Posts: 324

Rep: Reputation: Disabled
Pipewire 1.0.2 is now available.
 
Old 02-01-2024, 07:04 AM   #26
mistfire
Member
 
Registered: Jun 2021
Posts: 45

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by alex14641 View Post
Pipewire 1.0.2 is now available.
I tried it now but still the same error message. I wonder why bluetooth does not work when it reached version 1.0.1 onwards.

I found an interesting output when pipewire-pulse was started manually.

Code:
$ pipewire-pulse
[D] pw.context [pipewire.c:231 load_spa_handle()] load lib:'support/libspa-support' factory-name:'support.log'
[D] pw.context [pipewire.c:129 open_plugin()] loaded plugin:'/usr/lib64/spa-0.2/support/libspa-support.so'
Failure: Unknown error code
I'm running out of ideas on how to fix this bluetooth connection on pipewire
 
Old 02-01-2024, 04:04 PM   #27
murdo
Member
 
Registered: Aug 2021
Location: Scotland
Distribution: Slackware64-Current
Posts: 91

Rep: Reputation: 28
I'm also having problems with Pipewire 1.0.1 and above, with reverting to 1.0.0 fixing it, but in my case the problem is that I get no sound of any kind.

@mistfire, do you have alienbob's pipewire compat32 package installed? I do, and I was wondering if them being out of sync (1.0.0 for compat32 vs 1.0.2 for current) might be causing the issues.
 
Old 02-02-2024, 07:46 AM   #28
rizitis
Member
Contributing Member
 
Registered: Mar 2009
Location: Greece,Crete
Distribution: Slackware64-current, Slint
Posts: 722
Blog Entries: 2

Rep: Reputation: 533Reputation: 533Reputation: 533Reputation: 533Reputation: 533Reputation: 533
Quote:
Originally Posted by murdo View Post
I'm also having problems with Pipewire 1.0.1 and above, with reverting to 1.0.0 fixing it, but in my case the problem is that I get no sound of any kind.

@mistfire, do you have alienbob's pipewire compat32 package installed? I do, and I was wondering if them being out of sync (1.0.0 for compat32 vs 1.0.2 for current) might be causing the issues.
@murdo i have exactly same problems with you and I DONT have alienbob's pipewire compat32 package installed. We must compare our hardware infos, are you on intel sound card?
Code:
aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: NVidia [HDA NVidia], device 8: HDMI 2 [HDMI 2]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: NVidia [HDA NVidia], device 9: HDMI 3 [HDMI 3]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: sofhdadsp [sof-hda-dsp], device 0: HDA Analog (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: sofhdadsp [sof-hda-dsp], device 3: HDMI1 (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: sofhdadsp [sof-hda-dsp], device 4: HDMI2 (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: sofhdadsp [sof-hda-dsp], device 5: HDMI3 (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: sofhdadsp [sof-hda-dsp], device 31: HDA Analog Deep Buffer (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
(Fri Feb-2 3:44:10pm)-(CPU 1.1%:0:Net 9)-(omen:~)-(142G:155)
> lspci | grep -i audio
00:1f.3 Multimedia audio controller: Intel Corporation Alder Lake PCH-P High Definition Audio Controller (rev 01)
01:00.1 Audio device: NVIDIA Corporation Device 2291 (rev a1)
(Fri Feb-2 3:44:25pm)-(CPU 1.1%:0:Net 9)-(omen:~)-(142G:155)
> cat /proc/asound/modules
 0 snd_hda_intel
 1 snd_soc_skl_hda_dsp
Fri Feb-2 3:45:21pm)-(CPU 1.1%:0:Net 9)-(omen:~)-(142G:155)
> cat /proc/asound/cards
 0 [NVidia         ]: HDA-Intel - HDA NVidia
                      HDA NVidia at 0x76080000 irq 17
 1 [sofhdadsp      ]: sof-hda-dsp - sof-hda-dsp
                      HP-OMENbyHPLaptop16_b1xxx--8A15
 
Old 02-02-2024, 08:23 AM   #29
BrunoLafleur
Member
 
Registered: Apr 2020
Location: France
Distribution: Slackware
Posts: 428

Rep: Reputation: 389Reputation: 389Reputation: 389Reputation: 389
There is a new 1.0.3 version which solve an alsa plugin problem. Just dated half an hour ago.
 
1 members found this post helpful.
Old 02-02-2024, 08:37 AM   #30
marav
LQ Sage
 
Registered: Sep 2018
Location: Gironde
Distribution: Slackware
Posts: 5,467

Rep: Reputation: 4226Reputation: 4226Reputation: 4226Reputation: 4226Reputation: 4226Reputation: 4226Reputation: 4226Reputation: 4226Reputation: 4226Reputation: 4226Reputation: 4226
Pipewire 1.0.3

Code:
    - Fix ALSA version check. This should allow the alsa plugin to work again.
    - Some small fixes and improvements.
 
  


Reply
Page 2 of 3 1 2 3

Tags
audio, bluetooth, bluez, pipewire



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
LXer: PipeWire 1.0 -- An interview with PipeWire creator Wim Taymans LXer Syndicated Linux News 0 11-28-2023 04:50 AM
LXer: Using a Raspberry Pi as a Bluetooth speaker with PipeWire LXer Syndicated Linux News 0 09-03-2022 03:02 PM
LXer: PipeWire: Bluetooth® support status update LXer Syndicated Linux News 0 04-30-2022 02:24 PM
[SOLVED] [current] slackpkg-15.0.2-noarch-1 has /etc/pipewire/pipewire.conf.new j12i Slackware 3 04-27-2021 01:08 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 07:46 AM.

Contact Us - Advertising Info - Rules - Privacy - LQ Merchandise - Donations - Contributing Member - LQ Sitemap -
Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration