From: avinashkrishna07 <avinashkrishna07@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] pipewire: assure rw permissions in run directories in case its missing
Date: Sat, 30 Jul 2022 19:40:30 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38376@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 936 bytes --]
There is a new pull request by avinashkrishna07 against master on the void-packages repository
https://github.com/avinashkrishna07/void-packages master
https://github.com/void-linux/void-packages/pull/38376
pipewire: assure rw permissions in run directories in case its missing
Sometimes `/run/pulse` has `rwx------` permission somehow due to old pulseaudio package if installed.
This was causing `pactl info` return
```
Connection failure: Connection refused
pa_context_connect() failed: Connection refused
```
and applets showing `No audio devices`...
Because users in group `_pipewire` were not able to read/open the directory. This PR would ensure that it has 755 permissions if the directory already exists and not readable by `_pipewire` group.
#### Testing the changes
- I tested the changes in this PR: **YES**
A patch file from https://github.com/void-linux/void-packages/pull/38376.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-master-38376.patch --]
[-- Type: text/x-diff, Size: 966 bytes --]
From 494365db1b4243f689af9a273065155d45607e40 Mon Sep 17 00:00:00 2001
From: avinashkrishna07 <krishnaavinash98@gmail.com>
Date: Sat, 30 Jul 2022 22:59:54 +0530
Subject: [PATCH] pipewire: assure rw permissions in run directories in case
its missing
---
srcpkgs/pipewire/files/pipewire-pulse/run | 1 +
1 file changed, 1 insertion(+)
diff --git a/srcpkgs/pipewire/files/pipewire-pulse/run b/srcpkgs/pipewire/files/pipewire-pulse/run
index ea0520e44cd2..66d88e84aeb6 100644
--- a/srcpkgs/pipewire/files/pipewire-pulse/run
+++ b/srcpkgs/pipewire/files/pipewire-pulse/run
@@ -2,6 +2,7 @@
# this service is experimental and most setups should start pipewire as a user,
# for further information, please refer to the handbook
! [ -d /run/pulse ] && install -m 755 -g _pipewire -o _pipewire -d /run/pulse
+[ $(stat -c %a /run/pulse) -ne 755 ] && chmod 755 /run/pulse
umask 002
export PULSE_RUNTIME_PATH=/run/pulse
exec chpst -u _pipewire:_pipewire pipewire-pulse
next reply other threads:[~2022-07-30 17:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-30 17:40 avinashkrishna07 [this message]
2022-07-30 18:25 ` [PR REVIEW] " paper42
2022-07-30 18:38 ` paper42
2022-10-29 2:13 ` github-actions
2022-10-30 17:30 ` [PR PATCH] [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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38376@inbox.vuxu.org \
--to=avinashkrishna07@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).