noise-suppression-for-voice icon indicating copy to clipboard operation
noise-suppression-for-voice copied to clipboard

Pipewire does not run properly and there is no input source created.

Open Pragmer opened this issue 11 months ago • 6 comments

I am using Linux Mint 21.2, Kernel version is 5.19.0-46-generic, Desktop Environment is Cinnamon. I will try to provide more info upon request.

Going to describe what I did to install it in case I was being dumb and misunderstood the instructions, causing the issue. I downloaded the .zip, extracted the folder to my Home folder, created /home/leaderofthe00fkins/.config/pipewire/pipewire.conf.d/99-input-denoising.conf and pasted the configuration. I altered the path in the config to /home/leaderofthe00fkins/linux-rnnoise/ladspa/librnnoise_ladspa.so and left the VAD settings as default. I continued with "systemctl restart --user pipewire.service" as instructed. From the text in the guide it seems like, essentially, a new audio input device should have been created with the name "Noise Canceling source".

My issue is that no Input device was created after following the instructions. There was no output in the terminal when using the pipewire restart command. I tried looking at certain things I had seen other users check, like using the command "journalctl -b | grep pipewire" and trying to run the config directly with "pipewire -c ~/.config/pipewire/pipewire.conf.d/99-input-denoising.conf". The outputs of these are the following:

journalctl -b | grep pipewire
Jul 19 19:19:04 pejassupercomputer dbus-daemon[1327]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.33' (uid=112 pid=1830 comm="/usr/bin/pipewire " label="unconfined")
Jul 19 19:58:52 pejassupercomputer sudo[16172]: leaderofthe00fkins : TTY=pts/0 ; PWD=/home/leaderofthe00fkins ; USER=root ; COMMAND=/usr/local/bin/apt search pipewire
Jul 19 20:35:32 pejassupercomputer sudo[18349]: leaderofthe00fkins : TTY=pts/0 ; PWD=/home/leaderofthe00fkins ; USER=root ; COMMAND=/usr/local/bin/apt install pipewire
Jul 19 20:41:57 pejassupercomputer pipewire[21995]: mod.protocol-native: server 0x55ba80c129f0: unable to lock lockfile '/run/user/1000/pipewire-0.lock': Resource temporarily unavailable (maybe another daemon is running)
Jul 19 20:41:57 pejassupercomputer pipewire[21995]: pw.conf: 0x55ba80bf7130: could not load mandatory module "libpipewire-module-protocol-native": Resource temporarily unavailable
Jul 19 20:41:57 pejassupercomputer pipewire[21995]: default: failed to create context: Resource temporarily unavailable
Jul 19 20:42:02 pejassupercomputer pipewire[22008]: mod.protocol-native: server 0x55a321a839f0: unable to lock lockfile '/run/user/1000/pipewire-0.lock': Resource temporarily unavailable (maybe another daemon is running)
Jul 19 20:42:02 pejassupercomputer pipewire[22008]: pw.conf: 0x55a321a68130: could not load mandatory module "libpipewire-module-protocol-native": Resource temporarily unavailable
Jul 19 20:42:02 pejassupercomputer pipewire[22008]: default: failed to create context: Resource temporarily unavailable
Jul 19 20:43:00 pejassupercomputer pipewire[22042]: mod.protocol-native: server 0x556699f469f0: unable to lock lockfile '/run/user/1000/pipewire-0.lock': Resource temporarily unavailable (maybe another daemon is running)
Jul 19 20:43:00 pejassupercomputer pipewire[22042]: pw.conf: 0x556699f2b130: could not load mandatory module "libpipewire-module-protocol-native": Resource temporarily unavailable
Jul 19 20:43:00 pejassupercomputer pipewire[22042]: default: failed to create context: Resource temporarily unavailable
Jul 19 20:48:19 pejassupercomputer pipewire[22231]: mod.protocol-native: server 0x557a6b1a8a20: unable to lock lockfile '/run/user/1000/pipewire-0.lock': Resource temporarily unavailable (maybe another daemon is running)
Jul 19 20:48:19 pejassupercomputer pipewire[22231]: pw.conf: 0x557a6b18d160: could not load mandatory module "libpipewire-module-protocol-native": Resource temporarily unavailable
Jul 19 20:48:19 pejassupercomputer pipewire[22231]: default: failed to create context: Resource temporarily unavailable
pipewire -c ~/.config/pipewire/pipewire.conf.d/99-input-denoising.conf
[E][09231.036044] pw.core      | [          core.c:  382 core_new()] 0x565116967350: can't find protocol 'PipeWire:Protocol:Native': Operation not supported
[E][09231.036067] mod.filter-chain | [module-filter-ch: 1782 pipewire__module_init()] can't connect: Operation not supported
[E][09231.036103] pw.conf      | [          conf.c:  560 load_module()] 0x565116938190: could not load mandatory module "libpipewire-module-filter-chain": Operation not supported
[E][09231.036124] default      | [      pipewire.c:  123 main()] failed to create context: Operation not supported

Another command I saw, which was to check the running instances of pipewire I think, "ps ax | grep pipewire". This command returned the following before the config execution.

  24068 ?        S<sl   0:00 /usr/bin/pipewire
  24204 pts/0    S+     0:00 grep --color=auto pipewire

The same command returned this after manually running pipewire with -c and the config path.

  24068 ?        S<sl   0:00 /usr/bin/pipewire
  26562 ?        Sl     0:00 xed /home/leaderofthe00fkins/.config/pipewire/pipewire.conf.d/99-input-denoising.conf
  27052 pts/0    S+     0:00 grep --color=auto pipewire

As far as I can tell they are at least running, just not doing what is supposed to be done. Not sure what else to say, I don't really know where to go from here.

Pragmer avatar Jul 20 '23 05:07 Pragmer