Bug ID | 1175822 |
---|---|
Summary | systemd isolate forgets about SYSTEMD_WANTS from udev rules |
Classification | openSUSE |
Product | openSUSE Tumbleweed |
Version | Current |
Hardware | Other |
OS | Other |
Status | NEW |
Severity | Normal |
Priority | P5 - None |
Component | Basesystem |
Assignee | systemd-maintainers@suse.de |
Reporter | fvogt@suse.com |
QA Contact | qa-bugs@suse.de |
Found By | --- |
Blocker | --- |
+++ This bug was initially created as a clone of Bug #1173749 +++ spice-vdagent.service 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. Is there anything that can be done to make udev triggered units stay across isolate? Maybe spice-vdagentd.socket needs IgnoreOnIsolate=true?