Re: [PATCH weston] xwayland: Fix X11 lock file size confusion

2016-11-17 Thread Daniel Stone
Hi, On 17 November 2016 at 12:03, Eric Engestrom wrote: > On Thursday, 2016-11-17 11:35:53 +, Daniel Stone wrote: >> diff --git a/xwayland/launcher.c b/xwayland/launcher.c >> index 97d7c6e..56b949e 100644 >> --- a/xwayland/launcher.c >> +++ b/xwayland/launcher.c >> @@ -148,13 +148,19 @@ bind_

Re: [PATCH weston] xwayland: Fix X11 lock file size confusion

2016-11-17 Thread Pekka Paalanen
On Thu, 17 Nov 2016 11:35:53 + Daniel Stone wrote: > The X11 lock file was somewhat opaque. Into a sized array of 16 > characters, we previously read 11 bytes. 61beda653b fixed the parsing of > this input to ensure that we only considered the first 10 bytes: this > has the effect of culling a

Re: [PATCH weston] xwayland: Fix X11 lock file size confusion

2016-11-17 Thread Eric Engestrom
On Thursday, 2016-11-17 11:35:53 +, Daniel Stone wrote: > The X11 lock file was somewhat opaque. Into a sized array of 16 > characters, we previously read 11 bytes. 61beda653b fixed the parsing of > this input to ensure that we only considered the first 10 bytes: this > has the effect of cullin

Re: [PATCH weston] xwayland: Fix X11 lock file size confusion

2016-11-17 Thread Daniel Stone
On 17 November 2016 at 11:35, Daniel Stone wrote: > The X11 lock file was somewhat opaque. Into a sized array of 16 > characters, we previously read 11 bytes. 61beda653b fixed the parsing of > this input to ensure that we only considered the first 10 bytes: this > has the effect of culling a LF by

[PATCH weston] xwayland: Fix X11 lock file size confusion

2016-11-17 Thread Daniel Stone
The X11 lock file was somewhat opaque. Into a sized array of 16 characters, we previously read 11 bytes. 61beda653b fixed the parsing of this input to ensure that we only considered the first 10 bytes: this has the effect of culling a LF byte at the end of the string. This commit more explicitly N