Skip to content
GitLab
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 574
    • Issues 574
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 24
    • Merge requests 24
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • PipeWirePipeWire
  • pipewirepipewire
  • Issues
  • #800
Closed
Open
Issue created Feb 23, 2021 by Jakub Łukasiewicz@Jorengarenar

`~/.config/pipewire/media-session.d` created even though XDG_CONFIG_HOME is set to other location

Version, Distribution, Desktop Environment: 0.3.22, Arch Linux, i3

Description of Problem:

I'm setting XDG_CONFIG_HOME to ~/.local/config in the profile file, but PipeWire ignores it completely and instead creates .config/pipewire/media-session.d in $HOME. There is no $XDG_CONFIG_HOME/pipewire at all.

I was suspecting that service could be being launched before the variable is set, but it doesn't seem like it, as I'm already in i3 before PulseWire is started.

PS. Shouldn't media-session.d be stored in XDG_DATA_HOME?

Assignee
Assign to
Time tracking