Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • aports aports
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Graph
    • Compare
  • Issues 657
    • Issues 657
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 338
    • Merge requests 338
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • alpinealpine
  • aportsaports
  • Merge requests
  • !31641

community/pipewire: kill previous instance before launch

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged mailinglist-bot requested to merge patches/3966 into master Mar 04, 2022
  • Overview 0
  • Commits 1
  • Pipelines 2
  • Changes 2

Patchset from Pranjal Kole pranjal.kole7@gmail.com via aports #3966:

/usr/bin/pipewire was not being killed previously.

The order in which the processes are killed has been
changed to avoid this error message from pipewire-media-session:

[W][77952.698669] ms.core      | [ media-session.c: 2211 core_error()] error id:0 seq:799 res:-32 (Broken pipe): connection error

Additionally, pipewire-pulse is now started with the /usr/bin/ prefix,
since a user may have another binary named pipewire in their $PATH.
Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: patches/3966