As I mentioned on the dev call, the one application ported to the new application launching framework so far that does audio (the nav app) sees failures. This is what I see in the journal when it tries to play a voice prompt:
As I mentioned on the call, I suspect this is due to the setup of the agl-driver user session versus the old app framework. When I look at "systemctl status", PipeWire and Wireplumber are running in the system slice as root, which I suspect either needs to be changed to per-user to match how the user session works now, or something needs to be done wrt permissions (or socket location) so the agl-driver user can access things. may have some thoughts on this, as he did the tweaking previous to make things work with the old app framework.
As I mentioned on the dev call, the one application ported to the new application launching framework so far that does audio (the nav app) sees failures. This is what I see in the journal when it tries to play a voice prompt:
As I mentioned on the call, I suspect this is due to the setup of the agl-driver user session versus the old app framework. When I look at "systemctl status", PipeWire and Wireplumber are running in the system slice as root, which I suspect either needs to be changed to per-user to match how the user session works now, or something needs to be done wrt permissions (or socket location) so the agl-driver user can access things. may have some thoughts on this, as he did the tweaking previous to make things work with the old app framework.