Re: Qemu-kvm KDE VM steels my mouse

[ToddAndMargo]

On 7/12/21 5:04 AM, ToddAndMargo wrote:
> On 7/12/21 4:45 AM, ToddAndMargo wrote:
> > On 7/12/21 4:25 AM, ToddAndMargo wrote:
> > > On 7/12/21 4:11 AM, ToddAndMargo wrote:
> > > > On 7/11/21 8:13 PM, ToddAndMargo wrote:
> > > > > Hi All,
> > > > >
> > > > > Host
> > > > >    Fedora 34
> > > > >    Xfce 4.14
> > > > >    qemu-kvm-5.2.0-8.fc34.x86_64
> > > > >
> > > > > Guest:
> > > > >    Fedora-KDE-Live-x86_64-34-1.2.iso
> > > > >
> > > > > Problem:  my mouse is confined to the VM, unless
> > > > > I throw <ctrl><alt><L>.  But when I do so, KDE also
> > > > > logs me out and I have to log back into KDE
> > > > > every time and my mouse gets re-confined.
> > > > >
> > > > > This behavior is unique to KDE's VM, as it does not
> > > > > do it on Windows 7, Windows 10, Windows 11,
> > > > > Fedora 34 Xfce, or (weird old) Fedora Gnome VM's.
> > > > >
> > > > > How do I stop this behavior with KDE?   I need to mouse
> > > > > not to be confined.
> > > > >
> > > > >
> > > > > Many thanks,
> > > > > -T
> > > >
> > > > Found a workaround.  alt-clt un-confines the mouse.
> > > > But it still stays confined once you get back into
> > > > KDE.
> > >
> > > Spcie-vdagent is installed.
> > >
> > > Also, the clipboard does to work between the host
> > > and the client, if that help troubleshoot
> >
> > manually running spice-vdagent fixes the confinement
> > problem, but not the clipboard.  Now to find out how
> > to start spice-vdagent at boot
>
> I take that back, the clipboard goes back and forth,
> except for kconsole.

Something is stopping systemctl from creating
the start up link


# systemctl enable spice-vdagentd

The unit files have no installation config (WantedBy=, RequiredBy=, Also=,
Alias= settings in the [Install] section, and DefaultInstance= for template
units). This means they are not meant to be enabled using systemctl.

Possible reasons for having this kind of units are:
• A unit may be statically enabled by being symlinked from another unit's
  .wants/ or .requires/ directory.
• A unit's purpose may be to act as a helper for some other unit which has
  a requirement dependency on it.
• A unit may be started when needed via activation (socket, path, timer,
  D-Bus, udev, scripted systemctl call, ...).
• In case of template units, the unit is meant to be enabled with some
  instance name specified.