-
Bug
-
Resolution: Fixed
-
Major
-
None
-
None
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:
Jan 12 21:07:32 h3ulcb dbus-daemon[737]: qml: onSts_guideChanged Jan 12 21:07:33 h3ulcb dbus-daemon[737]: "No carrier" Jan 12 21:07:35 h3ulcb dbus-daemon[761]: Setting pipeline to PAUSED ... Jan 12 21:07:35 h3ulcb dbus-daemon[761]: ERROR: Pipeline doesn't want to pause. Jan 12 21:07:35 h3ulcb dbus-daemon[761]: ERROR: from element /GstPipeline:pipeline0/GstPipeWireSink:pipewiresink0: Failed to connect Jan 12 21:07:35 h3ulcb dbus-daemon[761]: Additional debug info: Jan 12 21:07:35 h3ulcb dbus-daemon[761]: ../git/src/gst/gstpipewiresink.c(750): gst_pipewire_sink_open (): /GstPipeline:pipeline0/GstPipeWireSink:pipewiresink0 Jan 12 21:07:35 h3ulcb dbus-daemon[761]: Setting pipeline to NULL ... Jan 12 21:07:35 h3ulcb dbus-daemon[761]: Freeing pipeline ... Jan 12 21:07:36 h3ulcb dbus-daemon[786]: Setting pipeline to PAUSED ... Jan 12 21:07:36 h3ulcb dbus-daemon[786]: ERROR: Pipeline doesn't want to pause. Jan 12 21:07:36 h3ulcb dbus-daemon[786]: ERROR: from element /GstPipeline:pipeline0/GstPipeWireSink:pipewiresink0: Failed to connect Jan 12 21:07:36 h3ulcb dbus-daemon[786]: Additional debug info: Jan 12 21:07:36 h3ulcb dbus-daemon[786]: ../git/src/gst/gstpipewiresink.c(750): gst_pipewire_sink_open (): /GstPipeline:pipeline0/GstPipeWireSink:pipewiresink0 Jan 12 21:07:36 h3ulcb dbus-daemon[786]: Setting pipeline to NULL ... Jan 12 21:07:36 h3ulcb dbus-daemon[786]: Freeing pipeline ... Ja
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. gkiagia may have some thoughts on this, as he did the tweaking previous to make things work with the old app framework.