On 7/12/21 9:33 PM, Ed Greshko wrote:
On 13/07/2021 12:03, ToddAndMargo via users wrote:
> $ systemctl status spice-vdagentd
> ○ spice-vdagentd.service - Agent daemon for Spice guests
> Loaded: loaded (/usr/lib/systemd/system/spice-vdagentd.service;
> indire>
> Active: inactive (dead)
> TriggeredBy: ● spice-vdagentd.socket
>
> From kconsole
> $ /usr/bin/spice-vdagent
>
> and the mouse is unconfined and the clipboard
> work, in kconsole as well.
>
> Must better. kconsole is no longer irritating either!
>
> :-)
>
> Now how to autostart spice-vdagentd (in KDE)?
No need to start spice-vdagentd! I think I said that more than once.
You can see from above, and better yet the one with the full output,
that spice-vdagentd.service is
"enabled" AND "TriggeredBy: ● spice-vdagentd.socket"
Further more, you can see that spice-vdagentd.socket is "listening"
When you run spice-vdagent it connects to the default port/socket. That
then "triggers" spice-vdagentd.service.
So the mouse or the clipboard should trigger it? They don't.
You question should really be. How do I start /usr/bin/spice-vdagent at
login without having to type it or run it
after login.
I gave you one way. That is to put /usr/bin/spice-vdagent as a line in
your .bashrc file.
tried that. Didn't work. Only from kconsole worked
Assuming, of course,
you are using bash as your default shell as defined in /etc/passwd.
The other way is to write a systemd --user unit
Either way works just fine.
systemd would be a workaround. But it should work properly on its own
and not require my intervention.
For now, I will just trigger it manually.
Thank you! You know you have a gift.
:-)
-T