On 13/07/2021 12:51, ToddAndMargo via users wrote:
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.
No, they have no connection. Zero, nada, none.
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
Then you need to check to see why by getting the status of the spice-vdagent.service and spice-vdagent.socket.
Let me illustrate one again with an F34KDE system which is using an systemd --user unit. I'm using this since
I didn't put logic in my .bashrc to check the environment in which it is started and this causes misleading log
entries.
I will reboot and then first login via ssh.
[egreshko@f34k2 ~]$ uptime
13:12:33 up 1 min, 1 user, load average: 1.19, 0.53, 0.20
[egreshko@f34k2 ~]$ systemctl --no-pager -l status spice-vdagentd.service
○ spice-vdagentd.service - Agent daemon for Spice guests
Loaded: loaded (/usr/lib/systemd/system/spice-vdagentd.service; indirect; vendor preset: enabled)
Active: inactive (dead)
TriggeredBy: ● spice-vdagentd.socket
[egreshko@f34k2 ~]$ systemctl --no-pager -l status spice-vdagentd.socket
● spice-vdagentd.socket - Activation socket for spice guest agent daemon
Loaded: loaded (/usr/lib/systemd/system/spice-vdagentd.socket; static)
Active: active (listening) since Tue 2021-07-13 13:11:17 CST; 1min 49s ago
Triggers: ● spice-vdagentd.service
Listen: /run/spice-vdagentd/spice-vdagent-sock (Stream)
CGroup: /system.slice/spice-vdagentd.socket
Jul 13 13:11:17 f34k2.greshko.com systemd[1]: Listening on Activation socket for spice guest agent daemon.
[egreshko@f34k2 ~]$ ps -eaf | grep spice
egreshko 1856 1825 0 13:13 pts/0 00:00:00 grep --color=auto spice
No spice-vdagentd is running. There is a socket established.
[egreshko@f34k2 ~]$ ll /run/spice-vdagentd/spice-vdagent-sock
srw-rw-rw-. 1 root root 0 Jul 13 13:11 /run/spice-vdagentd/spice-vdagent-sock
Now, I will login to Plasma Xorg on the console.
And, again from the ssh session, we now see....
[egreshko@f34k2 ~]$ ps -eaf | grep spice
egreshko 2057 1814 0 13:17 ? 00:00:00 /usr/bin/spice-vdagent -x
root 2065 1 0 13:17 ? 00:00:00 /usr/sbin/spice-vdagentd
The spice-vdagent was started via a user unit placed as
[egreshko@f34k2 ~]$ ll .config/systemd/user/spice-vdagent.service
-rw-r--r--. 1 egreshko egreshko 259 Jul 13 08:28 .config/systemd/user/spice-vdagent.service
The unit contains....
[egreshko@f34k2 ~]$ cat .config/systemd/user/spice-vdagent.service
[Unit]
Description=TestMe
After=plasma-core.target
[Service]
ExecStart=/usr/bin/spice-vdagent -x
[Install]
WantedBy=plasma-core.target
And after login shows....
[egreshko@f34k2 ~]$ systemctl --no-pager -l --user status spice-vdagent.service
● spice-vdagent.service - TestMe
Loaded: loaded (/home/egreshko/.config/systemd/user/spice-vdagent.service; enabled; vendor preset: disabled)
Active: active (running) since Tue 2021-07-13 13:17:21 CST; 4min 18s ago
Main PID: 2057 (spice-vdagent)
Tasks: 3 (limit: 2328)
Memory: 3.9M
CPU: 56ms
CGroup: /user.slice/user-1026.slice/user@1026.service/app.slice/spice-vdagent.service
└─2057 /usr/bin/spice-vdagent -x
as well as some other stuff that I need to check at some point but don't seem to have an negative effect.
For completeness
[egreshko@f34k2 ~]$ grep greshko /etc/passwd
egreshko:x:1026:65536:Ed Greshko:/home/egreshko:/bin/bash
So, why it doesn't work for you from the .bashrc file is unknown without diagnostic output.
--
Remind me to ignore comments which aren't germane to the thread.
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
