https://bugzilla.suse.com/show_bug.cgi?id=1173749
https://bugzilla.suse.com/show_bug.cgi?id=1173749#c1
Fabian Vogt changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |systemd-maintainers@suse.de
Flags| |needinfo?(systemd-maintaine
| |rs@suse.de)
--- Comment #1 from Fabian Vogt ---
Meh, it's not quite that simple.
This works fine when booting into graphical.target, but fails when booting into
multi-user.target and switching to graphical.target with "systemctl isolate
graphical.target" or "init 5".
There is /usr/lib/udev/rules.d/70-spice-vdagentd.rules, which enables the
socket once the virtio port appears. Apparently this is not part of the state
which is kept across isolate.
@security: Has this service not been audited before due to ^ evading the usual
triggers?
@systemd-maintainers:
Is there anything that can be done to make udev triggered units stay across
isolate?
Maybe spice-vdagentd.socket needs IgnoreOnIsolate=true?
--
You are receiving this mail because:
You are on the CC list for the bug.
