Open diniamo opened 2 months ago
Is it actually being killed, or is it crashing? Do you have a core dump?
pipewire-pulse.service: Main process exited, code=killed, status=9/KILL
Try running it along with killsnoop
from bcc
, that should tell you what is killing every process.
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 thinkpad
host (which I should rename because as it turns out, it's not a actually a thinkpad).
Relevant parts (?):
It's very hard to figure out what is going on there. What does echo $LD_PRELOAD
output?
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?
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 :+1: reaction to issues you find important.