[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-discuss] Mouse cursor invisible after version 2.8->3.1 and sdl->gt

From: halfdog
Subject: [Qemu-discuss] Mouse cursor invisible after version 2.8->3.1 and sdl->gtk update
Date: Thu, 10 Jan 2019 15:44:41 +0000

Hello list,

After upgrading from Debian Stretch to Buster, thus changing
the qemu version on host, I had to switch from "-display sdl"
to "gtk" as "sdl" is not available with Buster any more.

Since that switch the mouse behaviour changed, making guest machines
(also Debian Buster) very hard to use. Following two options

a) Using "Grab input" and "fullscreen", the mouse position is
correct, but I do not see any guest mouse pointer. Only changes
in hilighting or menu popups (when clicking) indicate the current
mouse position.

b) Using "fullscreen" and then "grab input" does show the mouse
pointer but mouse positions near the screen edge are not submitted
to the guest, those events seem to be consumed on host before that.

c) Not using fullscreen: fonts are harder to read due to scaling
on quite small mobile display (that's why the fullscreen preference
to avoid pixel-rot). The mouse pointer is shown and edge detection
would work theoretically, but it usually should happen in some
undistinguishable area where the guest-screen-background color
changes to the same color gtk-window-background, thus it is very
hard to hit it with the pointer.

So essentially I can decide beween working mouse cursor display
or working mouse pointer position, but I cannot have both. My
current workaround is to switch between a) and b) requiring 8
multi-key strokes and one mouse gesture instead of having just
to move the mouse pointer to the edge of the screen (old behaviour
with sdl).

Has anyone experienced a similar problem and knows how to fix it?

Alternatively, does someone know, how guest mouse pointer displaying
is working? I assume, that the graphics card has some feature
for that, so that the guest does not render the cursor pixels
into graphics memory but instructs the (virtual) card to do that.
If as assumed, is it possible to "break" that feature, e.g. dumb
down the guest (e.g. blacklisting modules, kernel command line)?

As I prefer usability over performance or styling, a solution with
c) could also be to override the gtk background color from black
to something greyish to see at least the screen edges (and have
somehow blurred fonts in the guest).

Any ideas?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]