Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
P
pipewire
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 135
    • Issues 135
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 3
    • Merge Requests 3
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • PipeWire
  • pipewire
  • Issues
  • #555

Closed
Open
Opened Jan 10, 2021 by Laurențiu Nicola@lnicola

Volume keys affect wrong device in GNOME

GNOME 3.38, pipewire 0.3.19, Arch Linux, Wayland

I have a couple of problems:

  • after a reboot or if my display goes to sleep, the volume keys sometimes change the volume on the wrong (i.e. not the one selected as fallback in pavucontrol or default in GNOME Settings
  • my monitor's volume is not remembered, as after a reboot it's at maximum, while pavucontrol shows the last value that was set (i.e. the correct volume); it starts working if I nudge it a bit from pavucontrol (#402?)
Edited Jan 10, 2021 by Laurențiu Nicola
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: pipewire/pipewire#555