

2·
1 month agoSorry for the series of edits. Yeah, just starting timers.target
or graphical.target
again when you’re done without using isolate seems like a pretty good strategy!
Sorry for the series of edits. Yeah, just starting timers.target
or graphical.target
again when you’re done without using isolate seems like a pretty good strategy!
I think if you switch back to the original target that depends on those services they should start again?
Like systemctl isolate yourtarget.target
and then a systemctl isolate graphical.target
to return to normal operation
Isolate will stop any services that aren’t required by the dependency chain.
Some of these might be user services though, in which case you’d need to create a user target
It’s possible that you don’t need to use isolate though, and can just start a target that conflicts and then instead of stopping it, start graphical.target
If you haven’t seen it, the open source driver for 3d connexion stuff is also pretty good, and I believe might be necessary for blender to work with it. It’s also probably packaged in the distro repositories.
https://github.com/FreeSpacenav/spacenavd