Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • pipewire pipewire
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 404
    • Issues 404
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • PipeWire
  • pipewirepipewire
  • Issues
  • #207

Closed
Open
Created Jan 28, 2020 by Sergey Kondakov@fox

Properly handle configuration files

It seems that right now PW only reads config from /etc/pipewire/pipewire.conf and fatally fails on any inconsistency. It should read all possible config locations in proper order (built-in/shipped defaults, system-wide /etc, site-wide /usr/local/etc, user-wide ~/.config) with overrides and don't bail out on obvious misconfiguration, potentially leaving system without audio support or more.

It may even have dbus runtime configuration interface for GUI managers that would not need to handle its files by themselves.

Assignee
Assign to
Time tracking