Re: [qubes-users] Circumventing autostart of apps when updating the appVM by `salt`?

2022-05-12 Thread 'Johannes Graumann' via qubes-users



On Thu, 2022-05-12 at 06:27 -0400, Demi Marie Obenour wrote:
> On Thu, May 12, 2022 at 11:26:53AM +0200, Qubes OS Users Mailing List
> wrote:
> > I have a setup with appVMs that are configured to autostart a
> > subset of
> > apps when they get fired up - one example is `app-privcom` that
> > runs
> > `evolution`, `signal-desktop` (from a user level installed flatpak
> > just
> > in that VM) and `liferea` (also a flatpak) when coming online.
> > 
> > Given the user-level flatpaked nature of some of the apps, the
> > appVMs
> > themselves have to be maintained (`flatpak update` etc.), which I
> > do
> > using `salt`. 
> > 
> > As a side effect of the convenient autostarting this results in
> > apps
> > popping up left and right when my fleet of appVMs is being updated
> > by
> > `salt` - which is a nuisance.
> > 
> > Can anyone think of a way to circumvent app autostart in the
> > context of
> > firing up the the appVMs via `salt`?
> 
> I don’t think this is possible right now.  This would require that
> the
> VM know that it is being started via Salt, which it currently does
> not.
> Feel free to submit an enhancement request on GitHub.
> 

Just thinking out loud here: traditional run level trickery in the
context of starting a VM is that something feasible?

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/4416e16d2482f9871a05b00ffab0fa91e1c286ee.camel%40graumannschaft.org.


Re: [qubes-users] Circumventing autostart of apps when updating the appVM by `salt`?

2022-05-12 Thread Demi Marie Obenour
On Thu, May 12, 2022 at 11:26:53AM +0200, Qubes OS Users Mailing List wrote:
> I have a setup with appVMs that are configured to autostart a subset of
> apps when they get fired up - one example is `app-privcom` that runs
> `evolution`, `signal-desktop` (from a user level installed flatpak just
> in that VM) and `liferea` (also a flatpak) when coming online.
> 
> Given the user-level flatpaked nature of some of the apps, the appVMs
> themselves have to be maintained (`flatpak update` etc.), which I do
> using `salt`. 
> 
> As a side effect of the convenient autostarting this results in apps
> popping up left and right when my fleet of appVMs is being updated by
> `salt` - which is a nuisance.
> 
> Can anyone think of a way to circumvent app autostart in the context of
> firing up the the appVMs via `salt`?

I don’t think this is possible right now.  This would require that the
VM know that it is being started via Salt, which it currently does not.
Feel free to submit an enhancement request on GitHub.

-- 
Sincerely,
Demi Marie Obenour (she/her/hers)
Invisible Things Lab

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/YnzhC7Vhi/yK1wYv%40itl-email.


signature.asc
Description: PGP signature