Bug 1963935 - Missing /etc/pipewire after upgrade to F34
Summary: Missing /etc/pipewire after upgrade to F34
Keywords:
Status: CLOSED DUPLICATE of bug 1963939
Alias: None
Product: Fedora
Classification: Fedora
Component: pipewire
Version: 34
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Wim Taymans
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-05-24 12:30 UTC by Tomáš Trnka
Modified: 2021-05-24 18:42 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2021-05-24 18:42:51 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Tomáš Trnka 2021-05-24 12:30:12 UTC
Description of problem:
My F34 machine does not have the /etc/pipewire directory at all, making it really hard to configure PipeWire. This is on my work laptop which I recently upgraded from F32 to F34. I need to apply the workaround for https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/838 to make Teams work  again, but there's currently no place to put the configuration into.

As far as I can see, pipewire reads the default config from /usr/share, so it doesn't really mind /etc/pipewire being missing. However, shouldn't it provide at least the skeleton directory structure in /etc as well, so that users don't have to create it all by hand when they want to configure something?

Version-Release number of selected component (if applicable):
pipewire-alsa-0.3.28-1.fc34.x86_64
pipewire-jack-audio-connection-kit-0.3.28-1.fc34.x86_64
pipewire-libs-0.3.28-1.fc34.x86_64
pipewire-pulseaudio-0.3.28-1.fc34.x86_64
pipewire0.2-libs-0.2.7-5.fc34.x86_64
pipewire-0.3.28-1.fc34.x86_64

Actual results:
ls: cannot access '/etc/pipewire': No such file or directory

Expected results:
/etc/pipewire present including necessary subdirectories and possibly template config files.

Comment 1 Bruno Vernay 2021-05-24 18:24:46 UTC
I guess it duplicates https://bugzilla.redhat.com/show_bug.cgi?id=1963939

Comment 2 Tomáš Trnka 2021-05-24 18:42:51 UTC

*** This bug has been marked as a duplicate of bug 1963939 ***


Note You need to log in before you can comment on or make changes to this bug.