I would like to set up a Pulse server on my Fedora 36 system so that a second desktop user can access it.
To do this, I copied the file pipewire-pulse to the directory of the first user martin and made adjustments in it.
You should not have copied that into the users config.
Each user should be able to access the audio and pipewire will write its own new config file for that user when they first start up audio. Copying things between users in that way is sure to leave something that may point in the wrong way instead of cleanly configuring it for the new user.
Knowing a bit more about the setup would help.
Are you running a remote server to provide media for playback?
Are you both using the same PC for access to the media?
Are you on 2 different PCs and both want access at the same time?
Is the media on your PC and you want to allow a user on another PC to have access?
The user vdr is the user that runs a system tool and should require NO CHANGES in its home directory to do its job.
Have you tried the command groups vdr to see what groups that user is a member of? Have you compared that to the output of groups to see what groups you may be a member of that may apply to the vdr user? Have you done any other trouble shooting or did you just start arbitrarily changing configs for the system tools?
On my system I have full access to all the audio tools by being a member of the ‘audio’ group, though I doubt that is needed for vdr.
Did you follow instructions from somewhere? If so please link the reference. If not then changes certainly seem arbitrary.
Was vdr installed from a fedora supporting repo or from some other source? Does vdr support use with pipeware/wireplumber or is it still tied to pulse audio?
Looking at those audio changes that have occurred with fedora in recent releases might point you in the proper direction. Fedora does not use pulse audio at the present (and has not since either F32 or F33). Pipewire has replaced it and if vdr is dependent upon pulse then it will require some adjustments, possibly even some reprogramming of vdr to support the new audio system in use today.
While this is all conjecture, I did the following to see if vdr was available for fedora 36 and with it available from fedora there really should be no need for changes to the config.
$ sudo dnf install vdr
Last metadata expiration check: 3:50:18 ago on Tue 05 Jul 2022 08:59:37 AM CDT.
Dependencies resolved.
==================================================================================================================================
Package Architecture Version Repository Size
==================================================================================================================================
Installing:
vdr x86_64 2.6.1-1.fc36 fedora 1.2 M
Installing dependencies:
vdrsymbol-fonts noarch 20100612-22.fc36 fedora 496 k
Transaction Summary
==================================================================================================================================
Install 2 Packages
Total download size: 1.7 M
Installed size: 5.2 M
Is this ok [y/N]:
Operation aborted.
I also get a sound output, but not always, as Pulseaudio has the alsa device in access,
and so I wanted to set up a Pulseaudio server to determine if it works better with that.
Why does i get the pulseserver running on my virtual fedora test system ?
[martin@fc36 ~]$ pactl info
Server String: tcp:127.0.0.1:4713
Library Protocol Version: 35
Server Protocol Version: 35
Is Local: no
Client Index: 68
Tile Size: 65472
User Name: martin
Host Name: fc36
Server Name: PulseAudio (on PipeWire 0.3.53)
Server Version: 15.0.0
Default Sample Specification: float32le 2ch 44100Hz
Default Channel Map: front-left,front-right
Default Sink: alsa_output.pci-0000_02_01.0.analog-stereo
Default Source: alsa_input.pci-0000_02_01.0.analog-stereo
Cookie: 712a:c78f
While I do not use pulseaudio, but instead am quite happy with the default pipewire, I have seen several posts about how to replace pipewire with pulseaudio.
IIRC it can be done with something similar to dnf swap --allowerasing pipewire pulseaudio . Then a reboot will start the system with pulseaudio server running.
It also seems that pulse can be emulated by pipewire if the pipewire-pulseaudio package is installed
