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 415
    • Issues 415
    • 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
  • #1500

Closed
Open
Created Aug 10, 2021 by Eric Blau@eblau

Continuous "Connection reset by peer" log messages

I'm running pipewire 0.3.33 as a PulseAudio replacement. I use the i3 window manager with i3blocks which runs ponymix (https://github.com/falconindy/ponymix) periodically to get/set the current volume, change profiles, etc.

I'm constantly seeing pipewire complain about "Connection reset by peer" like the following multiple times per minute in the systemd journal:

Aug 10 07:13:49 eric-thinkpad-home pipewire[1407096]: connection 0x55ada7447fd0: could not recvmsg on fd:99: Connection reset by peer
Aug 10 07:13:49 eric-thinkpad-home pipewire[1407096]: protocol-native 0x55ada72ef620: client 0x55ada7603230 error -104 (Connection reset by peer)

When I check with pw-mon, I see this is due to ponymix starting, retrieving the current volume through the PulseAudio interface and terminating.

I've tried copying pipewire.conf into $HOME/.config/pipewire and modifying log.level to level 1 or 0 but it has no effect. Is there any way to suppress these messages?

It's not very helpful to know that a transient program like ponymix has terminated and torn down the connection it's using on its fd when that is the expected behavior.

Assignee
Assign to
Time tracking