Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Why is FC34 's KDE spice-vdagent.socket not triggering the service?

272 views
Skip to first unread message

T

unread,
Jul 13, 2021, 1:55:51 AM7/13/21
to
Hi All,

Host:
Fedora 34
Xfce 4.14
qemu-kvm-5.2.0-8.fc34.x86_64

Virtual Machine (VM):
KDE installed from ISO:
Fedora-KDE-Live-x86_64-34-1.2.iso

I am running KDE in X11 mode as Wayland really stinks
on KDE.

spice-vdagentd.service is not running on my VM of KDE.
Runs on all my other VM's though. This kills
clipboard sharing and confines the mouse into the VM's
window (<alt><ctl> jail breaks you.)

I can start spice-vdagent manually from kconsole
by running
/usr/bin/spice-agent

The thing is, it should start automatically,
but does not.

from the .socket below, spice-vdagentd is listening to
ListenStream=/run/spice-vdagentd/spice-vdagent-sock

Apparently it is not hearing it and not triggering
the .service

Any idea how to troubleshoot this?

-T


$ systemctl status spice-vdagentd.service
○ 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


$ systemctl 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 Mon 2021-07-12 22:35:53 PDT; 1min
36s>
Triggers: ● spice-vdagentd.service
Listen: /run/spice-vdagentd/spice-vdagent-sock (Stream)
CGroup: /system.slice/spice-vdagentd.socket

# cat /usr/lib/systemd/system/spice-vdagentd.service

[Unit]
Description=Agent daemon for Spice guests
After=dbus.target
Requires=spice-vdagentd.socket

[Service]
Type=forking
EnvironmentFile=-/etc/sysconfig/spice-vdagentd
ExecStart=/usr/sbin/spice-vdagentd $SPICE_VDAGENTD_EXTRA_ARGS
PIDFile=/run/spice-vdagentd/spice-vdagentd.pid
PrivateTmp=true
Restart=on-failure

[Install]
Also=spice-vdagentd.socket




# cat /usr/lib/systemd/system/spice-vdagentd.socket
[Unit]
Description=Activation socket for spice guest agent daemon

[Socket]
ListenStream=/run/spice-vdagentd/spice-vdagent-sock



$ systemctl status spice-vdagentd.service
○ 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


$ systemctl 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 Mon 2021-07-12 22:35:53 PDT; 1min
36s>
Triggers: ● spice-vdagentd.service
Listen: /run/spice-vdagentd/spice-vdagent-sock (Stream)
CGroup: /system.slice/spice-vdagentd.socket


T

unread,
Jul 15, 2021, 9:22:20 PM7/15/21
to
It has been tagged on the Red Hat Bugzilla

spice-vdagent does not start in plasma session
https://bugzilla.redhat.com/show_bug.cgi?id=1951580

So I will stop trying to figure it out on my own.

T

unread,
Jul 17, 2021, 11:54:17 PM7/17/21
to
And ... they fixed it. Would never, never, ever, ever
have happened with that operating system whose name we
shall not mention

0 new messages