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 405
    • Issues 405
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 9
    • Merge requests 9
  • 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
  • #813

Closed
Open
Created Feb 25, 2021 by Florian Hülsmann@cbixContributor

alsa-pcm (USB) device not available sometimes until PW is restarted

Version, Distribution, Desktop Environment: Arch Linux, PipeWire 0.3.24, GNOME 3.38.3 + Wayland

Description of Problem: I have my main USB audio interface (Behringer XR18) connected to my laptop docking station and it's usually very convenient to just disconnect and connect the laptop sometimes. However I noticed that after it's not connected for maybe > 1-2 hours, PipeWire won't automatically activate the XR18 anymore until I restart.

How Reproducible: This problem is quite hard to reproduce because it only seems to start happening after some time. Restarting PipeWire temporarily solves the problem.

Steps to Reproduce:

  1. disconnect USB audio interface
  2. do something else for several hours???
  3. connect the USB interface again

Actual Results: The device is not activated and can't be used e.g. with pipewire-pulse. However it shows up in aplay -l and the MIDI ports of the interface seem to be usable in PW, but not the audio ports. See output of aplay -l, udevadm monitor, pw-dump -N and journalctl --user -fu pipewire attached. I finally managed to get PW logs with PIPEWIRE_DEBUG=4 which I think could be more useful for debugging.

Expected Results: The device should be active and usable. See output of pw-dump -N and journalctl --user -fu pipewire of successfully connecting the device after restarting pipewire.

Additional Info Eg. pw-dump > file (As Attachment Please): (see attachments)

aplay-l journalctl-xr18-connect udevadm-monitor-xr18-connect pw-dump-xr18-connected pw-dump-xr18-success journalctl-xr18-connect-success udevadm-monitor-xr18-success

Edited Mar 19, 2021 by Florian Hülsmann
Assignee
Assign to
Time tracking