I'm running the latest everything from git and have that commit
On Wed, 4 Apr 2018 at 12:50 Emil Velikov <emil.l.veli...@gmail.com> wrote:
> Hi Mike,
> On 4 April 2018 at 09:12, Mike Lothian <m...@fireburn.co.uk> wrote:
> > Hi
> > Kwin doesn't seem to start with the following commit:
> > commit abb9b58d1af9a0286162e52ef9db390d0c950fc1
> > Author: Thierry Reding <tred...@nvidia.com>
> > Date: Fri Mar 16 14:24:21 2018 +0100
> > present: Advertise protocol version 1.2
> > Everything is implemented to support protocol version 1.2. Make it
> > official.
> > Reviewed-by: Daniel Stone <dani...@collabora.com>
> > Signed-off-by: Thierry Reding <tred...@nvidia.com>
> > Reviewed-by: Emil Velikov <emil.veli...@collabora.com>
> > Though I think the issue may lie in commit:
> > commit 6a5d51e0823b43280e3646b7a0c919a3b76146ea
> > Author: Emil Velikov <emil.veli...@collabora.com>
> > Date: Mon Mar 19 16:04:43 2018 +0000
> > present: cap the version returned to the client
> > As per the protocol, the server should not return version greater
> > the one supported by the client.
> > Add a spec quote and tweak the numbers accordingly.
> > I realise that Kwin will probably need to be modified to work with
> > Present 1.2, but I don't think we should be seeing breakage unti that
> > happens
> AFAICT Kwin does not directly use the present extension, does it?
> Can you ensure that you have mesa commit
> It addresses some hunky stuff with the version handling.
firstname.lastname@example.org: X.Org development