On 7/12/21 7:22 AM, Ed Greshko wrote:
On 12/07/2021 20:34, ToddAndMargo via users wrote:
On 7/12/21 5:29 AM, ToddAndMargo via users wrote:
On 7/12/21 5:03 AM, ToddAndMargo via users wrote:
On 7/12/21 4:55 AM, Patrick O'Callaghan wrote:
On Mon, 2021-07-12 at 04:12 -0700, ToddAndMargo via users wrote:
How do I stop this behavour in KDE? I need to mouse
not to be confined.
Ctrl-Alt (without the L) works for me.
poc
Hi Patrick,
AWESOME!!! Thank you!
The writing on the top of the vm still says the L
-T
It does let me out without triggering KDE's screen lock,
but getting back into KDE and the mouse gets confined again.
So one step forward, one to go!
Is the VM running full-screen or in a window? If the latter, click
anywhere outside the window and you should be in KDE. If the former,
switch to a different virtual desktop, or exit the full-screen mode
first (hover over the centre top of the screen and you should see a
pop-up). Alternatively, use a keyboard shortcut to switch virtual
desktops.
poc
In a window. I run EVERYTHING in a window.
And everything seems to be working if I manually
start spcie-vdagent
Something is stopping systemctl from creating
the start up link
# systemctl enable spice-vdagentd
The unit files have no installation config (WantedBy=, RequiredBy=,
Also=,
Alias= settings in the [Install] section, and DefaultInstance= for
template
units). This means they are not meant to be enabled using systemctl.
Possible reasons for having this kind of units are:
• A unit may be statically enabled by being symlinked from another
unit's
.wants/ or .requires/ directory.
• A unit's purpose may be to act as a helper for some other unit
which has
a requirement dependency on it.
• A unit may be started when needed via activation (socket, path, timer,
D-Bus, udev, scripted systemctl call, ...).
• In case of template units, the unit is meant to be enabled with some
instance name specified.
I just posted:
KDE: Something is stopping systemctl from creating the start up link
https://bugzilla.redhat.com/show_bug.cgi?id=1981338
If you have a properly installed KDE system you'd find the following
when you logged in.
I installed to a blank hard drive (love gparted) directly
from the ISO. I did not do ANYTHING to the installer other
than run it. Something must be wrong installer. And I
let the ISO boot do its check thing too. It passed
[egreshko@f34k2 ~]$ systemctl 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 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 20:44:10 CST; 1h
19min ago
Triggers: ● spice-vdagentd.service
Listen: /run/spice-vdagentd/spice-vdagent-sock (Stream)
CGroup: /system.slice/spice-vdagentd.socket
Jul 12 20:44:10 f34k2.greshko.com systemd[1]: Listening on Activation
socket for spice guest agent daemon.
Take note of what your "enable" message is telling you.
The issue with the clipboard and KDE is that unlike GNOME there is no
startup of spice-vdagent when the user
logs in.
vdagent is running is gnome or I would have noticed in
very, very short order.
If you run that command from the command line in konsole you will find
your clipboard working just fine between
host and guest.
`# systemctl start spice-vdagent` does indeed fix the mouse and the
clipboard problem.
And after starting it, the status does match what you
copied me above.
I played with kconsole a bit. It is just really slow
copying to the host's clipboard. If I want to speed
things up, I copy from kconsole to a leafpad in the
client, then I can copy to a leafpad in the host.
:-)
Got to have my clipboard!
You should withdraw your BZ.
Not until `# systemctl enable spice-vdagent` stops crashing.
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Computers are like air conditioners.
They malfunction when you open windows
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
_______________________________________________
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
