mouse event for unknown monitor - uinput?
Hi Fi
https://bugzilla.redhat.com/show_bug.cgi?id=1269667
Guys, can you help clarify, can this be a problem of the uinput after all?
Hi,
Quoted 6 lines · poma
Hi Fi
https://bugzilla.redhat.com/show_bug.cgi?id=1269667
Guys, can you help clarify, can this be a problem of the uinput after all?
There was a regression in uinput code, you need to make sure you have commit 72d4736253af74147b1fa68145b2f4c61d1f37e1
Thanks.
Signature · 1 line
Dmitry
Quoted 10 lines · Dmitry Torokhov
Hi,
Quoted 6 lines · poma
Hi Fi
https://bugzilla.redhat.com/show_bug.cgi?id=1269667
Guys, can you help clarify, can this be a problem of the uinput after all?
Quoted 7 lines
There was a regression in uinput code, you need to make sure you have commit
72d4736253af74147b1fa68145b2f4c61d1f37e1Thanks.
--
Dmitry
Thanks for reply.
Yes, I know it, and it has already been settled with 4.3.0-0.rc4.git0.1.fc24.x86_64
Meanwhile on Rawhide, newer kernels emerged
4.3.0-0.rc4.git1.1.fc24.x86_64
4.3.0-0.rc4.git2.1.fc24.x86_64
4.3.0-0.rc4.git3.1.fc24.x86_64
I patched the kernel 4.3.0-0.rc4.git3.1.fc24.x86_64 with this patch:
https://bugzilla.redhat.com/show_bug.cgi?id=1269667#c17
which is actually a revert to ba4e9a6
as it is in 4.3.0-0.rc0.git7.1.fc24.x86_64
the last working kernel, in this context.
The problem is loss of display, causing loss of mouse functionality, via SPICE remote computing protocol - if "vga=" higher than standard 80x25 mode (0F00) is used.