At present if modesetting ever fails to set a hardware cursor it
switches back to a software one and stays that way until it is unloaded.
The following patch should fix that. I say "should" because I had
difficulties testing it - the cursor simply disappeared when it should
have been
Currently if modesetting ever fails to set a hardware cursor it will switch
to using a software cursor and never go back. Change this to try a hardware
cursor first every time a new one is set.
Signed-off-by: Michael Thayer
---
On 01/03/2016 16:03, Olivier Fourdan wrote:
git commit f175cf45:
vidmode: move to a separate library of its own
introduced a regression where the xserver would not build when
xf86vidmodeproto is not installed even if the configure option
"--disable-xf86vidmode" is specified.
Fix build
On Tue, 2016-03-01 at 21:30 +0100, Julien Cristau wrote:
> On Tue, Mar 1, 2016 at 14:09:30 -0500, Adam Jackson wrote:
>
> > Signed-off-by: Adam Jackson
> > ---
> > hw/xfree86/dri/dri.c | 8 +---
> > 1 file changed, 5 insertions(+), 3 deletions(-)
> >
> Kind of silly that
On Tue, 2016-03-01 at 21:39 +0100, Julien Cristau wrote:
> XvdiDestroyVideoNotifyList already frees the list if AddResource fails,
> so don't do it twice. And set tpn->client to NULL explicitly to avoid
> confusing uninitialized memory with a valid value.
remote: I: patch #75511 updated using