Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
pipewire
pipewire
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 225
    • Issues 225
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 7
    • Merge Requests 7
  • 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
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • PipeWire
  • pipewirepipewire
  • Issues
  • #733

Closed
Open
Created Feb 14, 2021 by Michał Zegan@webczat

Sound not working after log in

I have installed pipewire 0.3.21 on archlinux. I am a screenreader user, so sound starts playback for me immediately on the log in screen when screenreader starts up. Then, after I log in, there is no sound, and screenreader restart does not help (I have it set for automatic start). To fix sound, I have to systemctl --user restart pipewire then possibly restart screenreader. The only thing I see in logs from the first pipewire launch is messages like "no node found for xxx" where xxx is different node ids. I had the suspicion that the cause is a failure to handover devices between gdm and user sessions, as in pipewire not handling this correctly. I still believe it is the case, because pw-dump from the first pipewire launch shows no playback device, while capture device is present. I am aware of the fact the issue related to pipewire not detecting acl changes has been fixed, however it may be racing with gdm pipewire that didn't close the device in time.

Edited Feb 14, 2021 by Michał Zegan
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None