My setup runs pipewire-pulse. Occasionally I would see messages from wireplumber:
wp-proc-utils: failed to get status for PID 1027: Failed to open file “/proc/1027/status”: No such file or directory
GLib: GError set over the top of a previous GError or uninitialized memory.
This indicates a bug in someone's code. You must ensure an error is NULL before it's set.
The overwriting error message was: Failed to open file “/proc/1027/cgroup”: No such file or directory
wp-proc-utils: failed to get cgroup for PID 1027: Failed to open file “/proc/1027/status”: No such file or directory
wp-proc-utils: failed to get cmdline for PID 1027: No such file or directory
Where 1027 is the client pid in its pid namespace.
I currently do not have time to investigate the protocol any further. Working around this likely requires a PulseAudio proxy (which is good for security either way).
My setup runs `pipewire-pulse`. Occasionally I would see messages from `wireplumber`:
```
wp-proc-utils: failed to get status for PID 1027: Failed to open file “/proc/1027/status”: No such file or directory
GLib: GError set over the top of a previous GError or uninitialized memory.
This indicates a bug in someone's code. You must ensure an error is NULL before it's set.
The overwriting error message was: Failed to open file “/proc/1027/cgroup”: No such file or directory
wp-proc-utils: failed to get cgroup for PID 1027: Failed to open file “/proc/1027/status”: No such file or directory
wp-proc-utils: failed to get cmdline for PID 1027: No such file or directory
```
Where `1027` is the client pid in its pid namespace.
I currently do not have time to investigate the protocol any further. Working around this likely requires a PulseAudio proxy (which is good for security either way).
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
My setup runs
pipewire-pulse. Occasionally I would see messages fromwireplumber:Where
1027is the client pid in its pid namespace.I currently do not have time to investigate the protocol any further. Working around this likely requires a PulseAudio proxy (which is good for security either way).
Superseded by #21.