[kde] [Bug 461417] spice-vdagentd not running at startup and cannot be enabled to do it
https://bugs.kde.org/show_bug.cgi?id=461417 --- Comment #6 from Sebastian Gauna --- Sorry, I'm not a Linux expert, I don't understand exactly how it works, because spice has 2 executables: /usr/bin/spice-vdagent /usr/sbin/spice-vdagentd There is no .desktop file as far as I can see, it runs as a service It just comes preinstalled out of the box in Ubuntu, Kubuntu and Neon but in Neon the service is not enabled... if you throw a 'sudo service spice-vdagent status' or 'sudo service spice-vdagentd status' in a fresh and clean installation of Ubuntu or Kubuntu you get: Loaded: loaded (/lib/systemd/system/spice-vdagentd.service; indirect; vendor preset: enabled) Active: active (running) since Sat 2022-11-05 10:51:41 -03; 1h 26min ago TriggeredBy: ● spice-vdagentd.socket Process: 1162 ExecStart=/usr/sbin/spice-vdagentd $SPICE_VDAGENTD_EXTRA_ARGS (code=exited, status=0/SUCCESS) Main PID: 1164 (spice-vdagentd) Tasks: 2 (limit: 4551) Memory: 960.0K CPU: 3.711s CGroup: /system.slice/spice-vdagentd.service └─1164 /usr/sbin/spice-vdagentd ^^ Now if you do the same in a fresh install of Neon you get: ○ spice-vdagentd.service - Agent daemon for Spice guests Loaded: loaded (/lib/systemd/system/spice-vdagentd.service; indirect; vendor preset: enabled) Active: inactive (dead) TriggeredBy: ● spice-vdagentd.socket ^^ And in Neon if you try to enable the service, you get the error I posted... The file /lib/systemd/system/spice-vdagentd.service has de the same content in the three distros I really don't know what else to look for. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 461417] spice-vdagentd not running at startup and cannot be enabled to do it
https://bugs.kde.org/show_bug.cgi?id=461417 --- Comment #5 from Nate Graham --- What app provides the spice-vdagent.desktop autostart file? If it's not QEMU, it has to be something else. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 461417] spice-vdagentd not running at startup and cannot be enabled to do it
https://bugs.kde.org/show_bug.cgi?id=461417 --- Comment #4 from Sebastian Gauna --- I can confirm you that this is a Neon specific problem since I just installed a Kubuntu 22.04 VM guest and spice-vdagentd starts just fine by default. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 461417] spice-vdagentd not running at startup and cannot be enabled to do it
https://bugs.kde.org/show_bug.cgi?id=461417 --- Comment #3 from Sebastian Gauna --- I mean, I installed nothing form QEMU in the Neon guest as I didn't either in the Ubuntu guest. In a fresh installation of Ubuntu service spice-vdagentd is installed and started by default. In a fresh installation of Neon it's not even enabled. There's no QEMU involved here as far as I can tell, QEMU is in my host. Besides, being that KDE Neon is Ubuntu, it seems to me that something was modified in Neon. Sorry, I don't understand why I should report this to QEMU... -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 461417] spice-vdagentd not running at startup and cannot be enabled to do it
https://bugs.kde.org/show_bug.cgi?id=461417 --- Comment #2 from Sebastian Gauna --- (In reply to Nate Graham from comment #1) > As that error message shows, the systemd service file is misconfigured. > You'll need to report this to the QEMU people. Sorry if I didn't explain myself well, the error happens inside the VM within the guest, not in the host, besides it works just fine in Ubuntu 22.04 guests... -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 461417] spice-vdagentd not running at startup and cannot be enabled to do it
https://bugs.kde.org/show_bug.cgi?id=461417 Nate Graham changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DOWNSTREAM CC||n...@kde.org --- Comment #1 from Nate Graham --- As that error message shows, the systemd service file is misconfigured. You'll need to report this to the QEMU people. -- You are receiving this mail because: You are watching all bug changes.
