Re: [PATCH 2/3] qemu: Generate cmd line for pipewire audio backend

2023-05-16 Thread Martin Kletzander
On Tue, May 16, 2023 at 12:49:02PM +0200, Michal Prívozník wrote: On 5/16/23 11:52, Martin Kletzander wrote: On Thu, May 11, 2023 at 02:14:51PM +0200, Michal Privoznik wrote: This is mostly straightforward, except for a teensy-weensy detail: usually, there's no system wide daemon running, no sy

Re: [PATCH 2/3] qemu: Generate cmd line for pipewire audio backend

2023-05-16 Thread Michal Prívozník
On 5/16/23 11:52, Martin Kletzander wrote: > On Thu, May 11, 2023 at 02:14:51PM +0200, Michal Privoznik wrote: >> This is mostly straightforward, except for a teensy-weensy >> detail: usually, there's no system wide daemon running, no system >> wide available socket that anybody could connect to. P

Re: [PATCH 2/3] qemu: Generate cmd line for pipewire audio backend

2023-05-16 Thread Martin Kletzander
On Thu, May 11, 2023 at 02:14:51PM +0200, Michal Privoznik wrote: This is mostly straightforward, except for a teensy-weensy detail: usually, there's no system wide daemon running, no system wide available socket that anybody could connect to. PipeWire uses a per user daemon approach instead. But

[PATCH 2/3] qemu: Generate cmd line for pipewire audio backend

2023-05-11 Thread Michal Privoznik
This is mostly straightforward, except for a teensy-weensy detail: usually, there's no system wide daemon running, no system wide available socket that anybody could connect to. PipeWire uses a per user daemon approach instead. But this in turn means, that the socket location floats between various