Package Details: pipewire-jack-dropin 3-1

Git Clone URL: (read-only, click to copy)
Package Base: pipewire-dropin
Description: Use pipewire as drop-in replacement for JACK
Upstream URL: None
Licenses: LGPL2.1
Submitter: hexchain
Maintainer: hexchain
Last Packager: hexchain
Votes: 10
Popularity: 5.29
First Submitted: 2020-09-04 22:04
Last Updated: 2020-11-22 00:29

Required by (21)

Sources (2)

Pinned Comments

hexchain commented on 2020-11-01 00:18

Upon install, this package:

  • installs /etc/ to change the linker search path, so dynamically linked applications will find PipeWire's library before original ones;

If it does not work for you, please check if there is any file under /etc/ has /usr/lib in it:

grep -Hi ^/usr/lib/$ /etc/*

For Bluetooth audio devices to work, please also edit /etc/pipewire/pipewire.conf and change the last line to:

exec /usr/bin/pipewire-media-session -e bluez5

Please comment if something goes wrong for you!

Latest Comments

« First ‹ Previous 1 2 3 4 Next › Last »

OJFord commented on 2020-11-14 02:45

I have it working in Firefox, but not Spotify - play button greyed out even after restart and running through pw-pulse. (pipewire v0.3.15 and -e bluez,pulse-bridge from pinned comment.)

tinywrkb commented on 2020-11-12 17:21

Pipewire's libpulse was killed off

pix3l commented on 2020-11-09 10:04

@hexchain: please add this command to the pinned post about grep -Hi ^/usr/lib/$ /etc/*

hexchain commented on 2020-11-09 09:45

@oxalin: Please check if you have /usr/lib in any of the files under /etc/ Also, you need to enable bluez5 and pulse-bridge for a fully functional PA replacement. I've updated the pinned comment with the instruction.

oxalin commented on 2020-11-09 08:30

Since moving from symlinks to, this dropin solution stopped working for me. Using Gnome as my main WM.

Where should I be looking. Obviously, pulseaudio.service and socket are masked (as expected) as you point out in your pinned comment. "pactl info" gives me a connection refused.

It's as if the listener was not listening, "ldd /usr/bin/pactl | grep -i pulse" doesn't point to " => /usr/lib/pipewire-0.3/pulse/". Instead, it points to the native

pix3l commented on 2020-11-07 23:33

@hexchain: You seems highly knowledgable in this materia. Are you Pipewire dev?

After enabling bluez5 module, bluettoh receivers and headsets works, but sometimes laggy

I also do wonder (could not find it), how to allow other users to play sounds on this machine (like it was possible with pulseaudio). I would prefer most relaxed security settings over localhost

Things I miss from PulseAudio is possiblity to swatch automatically to new sinks, and possibility to output to multiple outputs.

hexchain commented on 2020-11-07 22:17

@pix3l: It does, but mostly for containerized apps (e.g. flatpak) that cannot have their libpulse replaced.

pix3l commented on 2020-11-07 22:14

@hexchain: thx for help. I've upgraded system, commented /usr/lib/ in, installed dropin and now everything works in KDE Plasama with pipewire, except bluetooth:

It's probably related:

Will try enabling pulse-bridge and bluez5 modules in pipewire and report back I wonder if pulse-bridge provides native pulseaudio protocol support(unlike this dropin that forces apps using pulse libs to talk using pipewire, if I understand good)

hexchain commented on 2020-11-05 11:48

@pix3l: No, kded5 isn't crashing for me. I'm not using AppMenu, and the volume mixer is just regular plasma-pa. If you happen to have KMix installed at the same time there might be some conflict that causes some things to crash. Could you try disabling AppMenu and see if the problem still exists? Also, could you give a backtrace with "coredumpctl info kded5"?

pix3l commented on 2020-11-05 11:41

@hexchain: Ouch, you are Godsend to me! Could you check journalctl | grep kded5 for any problems? (if you have fast enough machine and not using appmenu, then it might be invisible for you it's crashing in loop) Are you using AppMenu or/and firefox-kde-opensuse? What about volume mixers in Plasma?

Maybe the problem lies in my machine, because some incompatible plasma applet, qt plugins or something...

But after logging to Plasma some instances of Konsole got menu in panel(appmenu) and some inline(in-app), depending of the state of kded5 at starting. It's barely visible until I start firefox-kde-opensuse, then menu keeps switching between in-app and in-panel(appmenu), depending on the state of kded5 multiple times a second (hundred time per minute, reformating window every time and spiking cpu) But before running firefox, it's somehow usable (only not working appmenu sometimes). I was thining it's general KDE Plasma incompatibility with Pipewire, but it seems probably I'm wrong. Waiting for reply from you.

Also found the potential offenders:

grep -Hi usr/lib/$

50-ffmpeg2.8.conf:/usr/lib/ 50-libva1.conf:/usr/lib/