On Wed, Nov 9, 2016 at 6:44 PM, Marek Marczykowski-Górecki <[email protected]> wrote: > /tmp/qubes-session-env isn't sourced second time, at least in theory > (QUBES_ENV_SOURCED=1). How could it work? In older version (Qubes 3.0?) > it was indeed sourced at each shell startup.
Ah, you are correct. I had further modified my gui-agent-linux/appvm-scripts/usrbin/qubes-session in ways which are not suitable for upstream. My changes introduced an obvious race condition in which it is possible for the qubes session env to be "made ready" (mv /tmp/qubes-session-env.tmp ...env) before things started from xdg wrote to the env.tmp, potentially leading to vars from xdg failing to propagate. It always worked in practice, but that does not make it ok. One thing to clarify is what env var propagation dependency relations we should allow: - Should xdg-autostart be able to somehow propagate vars to other xdg-autostart entries? (allowing gnome-keychain -> nm-applet case) - only xdg-autostart -> qrexec-fork-server? - something else? -- You received this message because you are subscribed to the Google Groups "qubes-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-devel/CABQWM_A4wVyTw5NOS50rcwmd3v0Oeyjbo8yHuCoLbf9gf2XenA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
