https://bugs.kde.org/show_bug.cgi?id=472622
--- Comment #15 from zaris...@forexnews.bg ---
spice-vdagent added a workaround for this problem because GNOME had this exact
problem (https://bugzilla.redhat.com/show_bug.cgi?id=1750120) --- in short, it
sets the session type (not neccessarily
https://bugs.kde.org/show_bug.cgi?id=472622
--- Comment #14 from zaris...@forexnews.bg ---
Nope, that wasn't why (XFCE also doesn't set XDG_SESSION_TYPE). However, what
is different between the two DEs is the cgroup hierarchy --- in XFCE, almost
all user-level processes are uner the
https://bugs.kde.org/show_bug.cgi?id=472622
--- Comment #13 from zaris...@forexnews.bg ---
I just found out that this is due to KDE not automatically setting
XDG_SESSION_TYPE=x11 in systemd-logind upon executing startplasma-x11 (I'm
using startx instead of a display manager).
--
You are
https://bugs.kde.org/show_bug.cgi?id=472622
zaris...@forexnews.bg changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|UPSTREAM
https://bugs.kde.org/show_bug.cgi?id=472622
--- Comment #11 from zaris...@forexnews.bg ---
Oh, I learned something --- If you manually run xclip on the guest, the
guest->host starts working. If you run pbpaste on the host, host->guest starts
working. I'm not sure why it doesn't activate by itself
https://bugs.kde.org/show_bug.cgi?id=472622
Zamundaaa changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=472622
zaris...@forexnews.bg changed:
What|Removed |Added
Resolution|NOT A BUG |---
Status|RESOLVED
https://bugs.kde.org/show_bug.cgi?id=472622
--- Comment #8 from zaris...@forexnews.bg ---
I also seem to require vte-common.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=472622
--- Comment #7 from zaris...@forexnews.bg ---
I'm still not sure it's a problem on SPICE's side --- if I downgrade to 5.24,
it worked without installing anything.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=472622
--- Comment #6 from Zamundaaa ---
the portal probably implements some interface that spice-vdagentd prefers over
whatever failed before. So please still report this upstream.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=472622
zaris...@forexnews.bg changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=472622
--- Comment #4 from zaris...@forexnews.bg ---
I noticed that spice-vdagent (the one that runs as your user dies whenever you
try to run it, with
```
spice-vdagent[428319]: vdagent started
spice-vdagent[428319]: 0xd276cbd0 connected to
https://bugs.kde.org/show_bug.cgi?id=472622
zaris...@forexnews.bg changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|UPSTREAM
https://bugs.kde.org/show_bug.cgi?id=472622
Zamundaaa changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=472622
--- Comment #1 from zaris...@forexnews.bg ---
Upon further reflection, the difference between 455992 and this bug is that
this time, spice-vdagentd does start, it's just that now there's an error.
As before, other DEs work as expected.
The exact
15 matches
Mail list logo
