Rocksolid Light

Welcome to novaBBS (click a section below)

mail  files  register  newsreader  groups  login

Message-ID:  

1 + 1 = 3, for large values of 1.


computers / comp.os.linux.misc / Why is FC34 's KDE spice-vdagent.socket not triggering the service?

SubjectAuthor
* Why is FC34 's KDE spice-vdagent.socket not triggering the service?T
`* Re: Why is FC34 's KDE spice-vdagent.socket not triggering theT
 `- Re: Why is FC34 's KDE spice-vdagent.socket not triggering theT

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

<scj9t1$243$1@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=5341&group=comp.os.linux.misc#5341

 copy link   Newsgroups: comp.os.linux.misc
Path: i2pn2.org!i2pn.org!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From: T...@invalid.invalid (T)
Newsgroups: comp.os.linux.misc
Subject: Why is FC34 's KDE spice-vdagent.socket not triggering the service?
Date: Mon, 12 Jul 2021 22:55:43 -0700
Organization: A noiseless patient Spider
Lines: 108
Message-ID: <scj9t1$243$1@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable
Injection-Date: Tue, 13 Jul 2021 05:55:45 -0000 (UTC)
Injection-Info: reader02.eternal-september.org; posting-host="a6f1d4586c1382eb3511abb1bcf91622";
logging-data="2179"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/xChWGuZtJPHRvMjRFNgEIei2Yy7NXwFg="
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101
Thunderbird/78.11.0
Cancel-Lock: sha1:IQQqH2Ity8WnMC0QEL3vCC76HAs=
Content-Language: en-DE
X-Mozilla-News-Host: news://news.eternal-september.org:119
 by: T - Tue, 13 Jul 2021 05:55 UTC

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

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

<scqn07$ovb$1@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=5342&group=comp.os.linux.misc#5342

 copy link   Newsgroups: comp.os.linux.misc
Path: i2pn2.org!i2pn.org!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From: T...@invalid.invalid (T)
Newsgroups: comp.os.linux.misc
Subject: Re: Why is FC34 's KDE spice-vdagent.socket not triggering the
service?
Date: Thu, 15 Jul 2021 18:22:15 -0700
Organization: A noiseless patient Spider
Lines: 124
Message-ID: <scqn07$ovb$1@dont-email.me>
References: <scj9t1$243$1@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable
Injection-Date: Fri, 16 Jul 2021 01:22:15 -0000 (UTC)
Injection-Info: reader02.eternal-september.org; posting-host="45359cb820cf0176b7212de92720dc5d";
logging-data="25579"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX187abRVZ16vbMnrJM82IcobEjf6VLzLBpU="
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101
Thunderbird/78.11.0
Cancel-Lock: sha1:LI/xNS+S+XcitIn76hN4gCBMzro=
In-Reply-To: <scj9t1$243$1@dont-email.me>
Content-Language: en-DE
 by: T - Fri, 16 Jul 2021 01:22 UTC

On 7/12/21 10:55 PM, T wrote:
> 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
>
>

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.

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

<sd08l4$5h4$1@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=5355&group=comp.os.linux.misc#5355

 copy link   Newsgroups: comp.os.linux.misc
Path: i2pn2.org!i2pn.org!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From: T...@invalid.invalid (T)
Newsgroups: comp.os.linux.misc
Subject: Re: Why is FC34 's KDE spice-vdagent.socket not triggering the
service?
Date: Sat, 17 Jul 2021 20:54:12 -0700
Organization: A noiseless patient Spider
Lines: 135
Message-ID: <sd08l4$5h4$1@dont-email.me>
References: <scj9t1$243$1@dont-email.me> <scqn07$ovb$1@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable
Injection-Date: Sun, 18 Jul 2021 03:54:12 -0000 (UTC)
Injection-Info: reader02.eternal-september.org; posting-host="e3064dbb5c3b329b2d08ca99fa714a65";
logging-data="5668"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/r8i70FbF2pxLpLjQ5JxCQi+3FW9CBZro="
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101
Thunderbird/78.11.0
Cancel-Lock: sha1:hpl+TKIatznxXrjtwKY7fstwNgQ=
In-Reply-To: <scqn07$ovb$1@dont-email.me>
Content-Language: en-DE
 by: T - Sun, 18 Jul 2021 03:54 UTC

On 7/15/21 6:22 PM, T wrote:
> On 7/12/21 10:55 PM, T wrote:
>> 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
>>
>>
>
> 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.
>

And ... they fixed it. Would never, never, ever, ever
have happened with that operating system whose name we
shall not mention

1
server_pubkey.txt

rocksolid light 0.9.7
clearnet tor