-
-
Notifications
You must be signed in to change notification settings - Fork 14.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pipewire-pulse gets killed whenever something tries to use it #334140
Comments
Is it actually being killed, or is it crashing? Do you have a core dump? |
|
Try running it along with |
Doesn't give me anything for pipewire-pulse, works for other programs though. |
That is very strange. Actually, are you using the hardened profile or anything like that? |
Hardened profile where? |
In your NixOS config. Can you post your entire configuration, actually? |
https://github.com/diniamo/niqs - The bug happens on the Relevant parts (?): |
It's very hard to figure out what is going on there. What does |
It's empty. |
At this point the only idea I can think of is to run it under a debugger and observe. |
I'm not sure why a debugger would give me anything when it's just killed. Either way running it under gdb does, in fact, not give me anything. Otherwise, what did you mean? |
Bumping this to share a fix. For some reason, enabling {
security.rtkit.enable = true;
} |
I didn't though? |
I think I misread your conf, in |
I wonder if this may have any relation to #348155 |
In my case the socket succeeds to launch |
@AhuracMusic That module isn't enabled on my laptop. |
I am having a similar bug on hyprland enabled via home-manager, and I expect the same issue to be present if hyprland was enabled in nixos: |
Once again, this has nothing to do with Hyprland. |
Describe the bug
The title says everything, by "whenever something tries to use it", I mean when something tries to play audio, or query data (eg.: control programs like pavucontrol or pulsemixer).
Steps To Reproduce
I have no idea, I haven't opened an issue, because with my luck, this could have been one of a kind, but I found someone else who has this.
Expected behavior
Pipewire-pulse and applications that use the pulse backend work fine.
Additional context
Dmesg doesn't contain any messages about the OOM killer being the culprit.
Is there any way to figure out what's killing it?
Notify maintainers
@K900 (I know you've tried to help, but tagging nonetheless)
Metadata
Add a 👍 reaction to issues you find important.
The text was updated successfully, but these errors were encountered: