Github messages for voidlinux
 help / color / mirror / Atom feed
From: antaxiom <antaxiom@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: wireplumber: request for bundling runit service with the package
Date: Thu, 31 Mar 2022 04:20:41 +0200	[thread overview]
Message-ID: <20220331022041.jz_IvAEAutwggP3Q5-xk3mbQm2qQHmIxzUIFvmGaqVE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36393@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 2136 bytes --]

New comment by antaxiom on void-packages repository

https://github.com/void-linux/void-packages/issues/36393#issuecomment-1083995852

Comment:
I got wireplumber working without needing to add any dbus variables (though
this would've been good to know), but I did have to start the script
through my DE (I'm currently using gnome and therefore
xdg-desktop-portal-gtk, but I tried on wlr compositors as well) as opposed
to running it as a service. I actually had to run pipewire and desktop
portal through the script as well to get them all playing nicely. I'll keep
this in mind if I do ever have to set this up again, but hopefully a
service will make this irrelevant.

Edit: Well that was interesting timing for my reply. I'll have to try this sometime one it all gets pushed.

On Wed, Mar 30, 2022 at 10:15 PM Gabriel Sanches ***@***.***>
wrote:

> +1 for this issue, I had to get wire plumber running and it was a royal
> pain. Pipewire worked as a service, but wire plumber was unhappy unless
> everything was run as my user. If someone were able to write a good service
> (and ideally add a pipewire section to the handbook detailing how all of
> this and desktop portal worked together) it would be a dream.
>
> I couldn't make wireplumber work (while pipewire-media-session works
> flawlessly), but maybe I can help with the desktop portal you mentioned, in
> case you're using xdg-desktop-portal-wlr.
>
> Basically you only need to install it and make sure you import the correct
> variables to the dbus session. I've got this in my WM's init script:
>
> dbus-update-activation-environment WAYLAND_DISPLAY XDG_CURRENT_DESKTOP
>
> Here both WAYLAND_DISPLAY and XDG_CURRENT_DESKTOP are previously set to
> something that makes sense Wayland-wise.
>
> —
> Reply to this email directly, view it on GitHub
> <https://github.com/void-linux/void-packages/issues/36393#issuecomment-1083993934>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AJRW3AWAXXVBFAUQXVU74VDVCUDFZANCNFSM5R337JDA>
> .
> You are receiving this because you commented.Message ID:
> ***@***.***>
>


  parent reply	other threads:[~2022-03-31  2:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-28 17:39 [ISSUE] " Animeshz
2022-03-31  0:10 ` antaxiom
2022-03-31  2:15 ` gbrlsnchs
2022-03-31  2:17 ` subnut
2022-03-31  2:19 ` [ISSUE] [CLOSED] " ahesford
2022-03-31  2:19 ` antaxiom
2022-03-31  2:20 ` antaxiom [this message]
2022-03-31  2:22 ` ahesford

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=20220331022041.jz_IvAEAutwggP3Q5-xk3mbQm2qQHmIxzUIFvmGaqVE@z \
    --to=antaxiom@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).