[Spice-devel] [PATCH spice-gtk 0/2] Allow to disable syncing modifiers

[Marc-André Lureau]

Hi

----- Original Message -----
> Hi Marc-André,
> 
> On Tue, 2016-05-03 at 20:15 +0200, Marc-André Lureau wrote:
> > Hi
> > 
> > On Tue, May 3, 2016 at 3:41 PM, Pavel Grunt <pgrunt at redhat.com> wrote:
> > > This patches introduces and uses a spice-gtk-session property
> > > for disabling automatic modifiers sync. It can be useful in cases
> > > where syncing currently fails - eg not working leds on the guest side,
> > > missmatch between client's and guest's keyboard layout.
> > 
> > Is this a guest configuration issue?
> 
> It is a server/client/guest issue.
> 
> Guest issue:
> Checking the led state for modifiers does not always work (it doesn't work in
> vte in RHEL7) -> causes server to send "requests to sync modifiers" ->
> capslock is on for few seconds, then is off, then is on...

That's a guest bug then, is there a bug for it?

> Server:
> Server sends the "hw value" of the capslock key to the guest, but for example
> Japanese layout has "shift+capslock" to turn on capslock. So the server
> should send "shift + capslock" instead.

ok, that sound like a server bug for japanese keyboard

> Client:
> It just keeps syncing, it is not great if everything works ok. But maybe
> would be reasonable to stop trying to sync when it does not work.

You mean "it is great", right? ;)

> I plan to implement some solution involving the agent (gdk can tell us the
> state of capslock, keycombo for its activation etc). But for some users may
> be reasonable to just disable syncing.
> 
> >  How are you going to expose this
> > property to the user? It would look bad to add some weird tweaks like
> > that to the UI.
> > 
> I added the checkbox to spicy just to test it. We have more options - a
> configuration file, the settings file...
> 
> Pavel
> 
> 
> _______________________________________________
> Spice-devel mailing list
> Spice-devel at lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/spice-devel
>