public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jack <ostroffjh@users.sourceforge.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] wireplumper for pipewire 0.3.39 startup problems
Date: Sat, 06 Nov 2021 18:54:41 -0400	[thread overview]
Message-ID: <PP2R5QEZ.JLP55EEA.OOFUN23U@DX5KYFJX.CKQPHUPR.JEPHO2PU> (raw)
In-Reply-To: <246193f7-573e-023c-7a8c-36248ac83e3f@googlemail.com>

On 2021.11.06 18:00, Tamer Higazi wrote:
> Hi people,
> 
> I got a problem getting "wireplumper" for pipewire to run.
> 
> tamer@tux ~ $ systemctl --user status wireplumber.service
> 
> tells me that it failed to start
> 
> × wireplumber.service - Multimedia Service Session Manager
>      Loaded: loaded (/usr/lib/systemd/user/wireplumber.service;  
> enabled; vendor preset: enabled)
>      Active: failed (Result: exit-code) since Sat 2021-11-06 22:46:02  
> CET; 2min 53s ago
>     Process: 1380 ExecStart=/usr/bin/wireplumber (code=exited,  
> status=70)
>    Main PID: 1380 (code=exited, status=70)
> 
> Nov 06 22:46:02 tux systemd[1244]: wireplumber.service: Failed with  
> result 'exit-code'.
> Nov 06 22:46:02 tux systemd[1244]: wireplumber.service: Scheduled  
> restart job, restart counter is at 5.
> Nov 06 22:46:02 tux systemd[1244]: Stopped Multimedia Service Session  
> Manager.
> Nov 06 22:46:02 tux systemd[1244]: wireplumber.service: Start request  
> repeated too quickly.
> Nov 06 22:46:02 tux systemd[1244]: wireplumber.service: Failed with  
> result 'exit-code'.
> Nov 06 22:46:02 tux systemd[1244]: Failed to start Multimedia Service  
> Session Manager.
> 
> Executing "wireplumper" gives out an error that it failed to start  
> "wireplumper":
> 
> tamer@tux ~ $ /usr/bin/wireplumber
> failed to start systemd logind monitor: -2 (No such file or directory)
> M 22:46:16.429961        wireplumber  
> ../wireplumber-0.4.4/src/main.c:328:on_disconnected: disconnected  
> from pipewire
> 
> 
> by the way, according the pipewire gentoo guide, the ~/.xinitrc file  
> should look like this:
> 
> if which dbus-launch >/dev/null && test -z  
> "$DBUS_SESSION_BUS_ADDRESS"; then
>        eval `dbus-launch --sh-syntax --exit-with-session`
> fi
> 
> /usr/bin/gentoo-pipewire-launcher
> 
> ...but "/usr/bin/gentoo-pipewire-launcher" simply does not exist ...
> 
> 
> pipewire is on 0.3.39:
> 
> tamer@tux ~ $ LANG=C pactl info | grep "Server Name"
> Server Name: PulseAudio (on PipeWire 0.3.39)
> 
> 
> emerge --info:
> https://pastebin.com/raw/Ya6LmipC
> 
> (emerge -uDN @world) had been executed today ....

Your post has a mix of "wireplumper" and "wireplumber".  Hopefully  
there is just a repeated typo, and in fact, all should be the same?


  reply	other threads:[~2021-11-06 22:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-06 22:00 [gentoo-user] wireplumper for pipewire 0.3.39 startup problems Tamer Higazi
2021-11-06 22:54 ` Jack [this message]
2021-11-06 23:18   ` [gentoo-user] wireplumber " Tamer Higazi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=PP2R5QEZ.JLP55EEA.OOFUN23U@DX5KYFJX.CKQPHUPR.JEPHO2PU \
    --to=ostroffjh@users.sourceforge.net \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox