Re: [PATCH] Flush buffer in time for global (un)lock xserver operation

2019-12-13 Thread Chen Gang
On 2019/12/12 下午7:01, walter harms wrote: > > short version, > can you provide an example works.c vs. not_works.c ? > > re, > wh > Excuse me, I did not write any example .c files. Originally, I directly fixed the gui quiting issue by adding _XFlush() after GetEmptyReq() for XUngrabServer in

Re: [PATCH] Flush buffer in time for global (un)lock xserver operation

2019-12-12 Thread Chen Gang
> On Wed, 2019-12-04 at 18:24 +0800, cheng...@emindsoft.com.cn wrote: >> From: Chen Gang >> >> The global (un)lock xserver operations will have effect to the whole >> system, and all the other gui apps have to be blocked, so the operations >> should not be buffe

[PATCH] libx11-1.6.7: Flush buffer in time for global (un)lock xserver operation

2019-11-27 Thread Chen Gang
The global (un)lock xserver operations will have effect to the whole system, and all the other gui apps have to be blocked, so the operations should not be buffered, or may cause sync issue, e.g. reboot machine. Signed-off-by: Chen Gang --- src/GrServer.c | 1 + src/UngrabSvr.c | 1 + 2 files

Re: [PATCH] libx11-1.6.7: Flush buffer in time for global (un)lock xserver operation

2019-11-27 Thread Chen Gang
Oh, sorry, XFlush should be replaced by _XFlush. On 2019/11/27 上午11:47, Chen Gang wrote: > The global (un)lock xserver operations will have effect to the whole > system, and all the other gui apps have to be blocked, so the operations > should not be buffered, or may cause sync issue, e.