Workaround is functional on Ubuntu 18.04 daily build - without it, BOOT PROCESS WILL FREEZE! after install spice-vdagent package on starting spice-vdagent(d) service.
But as spice-vdagentd in result hasn't information about sessions, so there is (in man documented) limitation on one instance of spice-vdagent client. And there are two instances running - one for gdm, one for each user. Service spice-vdagent is complaining: spice-vdagentd[540]: multiple agents in o ne session, disabling agent to avoid potential information leak spice-vdagentd[540]: closed vdagent virtio channel Workaround is to sudo killall spice-vdagent and then run spice-vdagent as a current user. It would be very helpful to fix spice-vdagentd collision with systemd- logind, because it is destroying Ubuntu guest experience (seemingly unbootable system and even then very tricky to get decent interaction with vm working). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1633609 Title: spice-vdagentd does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spice-vdagent/+bug/1633609/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
