From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Pipewire and Pipewire Pulse Not Properly Configured for Autostarting
Date: Tue, 09 Aug 2022 01:03:24 +0200 [thread overview]
Message-ID: <20220808230324.FbD4HGHAEnT5VER0OxFCjLvYB24gwSbPVNrK8hyKz-0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38541@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1232 bytes --]
New comment by paper42 on void-packages repository
https://github.com/void-linux/void-packages/issues/38541#issuecomment-1208705788
Comment:
> The package places its autostart files in the XDG standard location /etc/xdg/autostart and thus start automatically without intervention by the user when installed.
Automatically starting pipewire on behalf of the user is a bad idea and we won't do it.
> However, this would require the pipewire-pulse desktop file (and ideally the binary and other configuration tools, for organization sake) to be placed in separate, conflicting package since pipewire can also be used alongside pulseaudio.
That's not pretty and would be confusing to new users coming from other distributions. We chose to not enable pipewire (and pipewire-pulse) automatically for the user and we document a common way to start pipewire here: https://docs.voidlinux.org/config/media/pipewire.html.
> The two autostart files pipewire.desktop and pipewire-pulse.desktop are located in /usr/share/applications which has nothing to do with auto-starting applications, only listing them in menus and application runners.
They are have `NoDisplay=true` set, so they shouldn't show up in application runners.
next prev parent reply other threads:[~2022-08-08 23:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-08 22:24 [ISSUE] " TrueTechie
2022-08-08 23:03 ` paper42 [this message]
2022-08-09 1:45 ` TrueTechie
2022-08-09 8:43 ` paper42
2022-08-09 8:43 ` [ISSUE] [CLOSED] " paper42
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=20220808230324.FbD4HGHAEnT5VER0OxFCjLvYB24gwSbPVNrK8hyKz-0@z \
--to=paper42@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).