Install rtkit when using PulseAudio or PipeWire - #4696
Open
Dk000t wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PR Description:
Install
rtkitwhenever either the PulseAudio or PipeWire audio profile is selected.rtkitis optional for both backends, but it enables realtime scheduling through RealtimeKit when available.Installing it avoids runtime warnings such as:
The package is added once in the common audio installation flow, avoiding duplication between the PulseAudio and PipeWire package lists.
Tests and Checks
Tested in a virtual machine:
rtkitis installed correctly, starts on demand as expected, and the RTKit-related errors are no longer present.