From: FollieHiyuki <FollieHiyuki@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Pamixer not working with pipewire-pulse
Date: Tue, 28 Sep 2021 20:50:27 +0200 [thread overview]
Message-ID: <20210928185027.BERqyaVhcTBb0npxTC17Rb36LyrRYe3Cj4bxs8-wZuo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33167@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 962 bytes --]
New comment by FollieHiyuki on void-packages repository
https://github.com/void-linux/void-packages/issues/33167#issuecomment-929531677
Comment:
You can set it to anything, as long as it satisfies these:
> $XDG_RUNTIME_DIR defines the base directory relative to which user-specific non-essential runtime files and other file objects (such as sockets, named pipes, ...) should be stored. The directory MUST be owned by the user, and he MUST be the only one having read and write access to it. Its Unix access mode MUST be 0700.
> It is automatically created the first time a user logs in and removed on the user's final logout. If a user logs in twice at the same time, both sessions will see the same $XDG_RUNTIME_DIR and the same contents. If a user logs in once, then logs out again, and logs in again, the directory contents will have been lost in between, but applications should not rely on this behavior and must be able to deal with stale files.
next prev parent reply other threads:[~2021-09-28 18:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-28 15:48 [ISSUE] " timsofteng
2021-09-28 16:56 ` FollieHiyuki
2021-09-28 18:38 ` timsofteng
2021-09-28 18:39 ` timsofteng
2021-09-28 18:50 ` FollieHiyuki [this message]
2021-09-29 8:26 ` timsofteng
2021-09-29 8:26 ` [ISSUE] [CLOSED] " timsofteng
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=20210928185027.BERqyaVhcTBb0npxTC17Rb36LyrRYe3Cj4bxs8-wZuo@z \
--to=folliehiyuki@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).