[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: X protocol error
From: |
Po Lu |
Subject: |
Re: X protocol error |
Date: |
Thu, 18 Aug 2022 10:30:11 +0800 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/28.0.91 (gnu/linux) |
Robert Pluim <rpluim@gmail.com> writes:
> BTW, this is bug#57261. The following fixes it for me:
>
> diff --git a/src/xterm.c b/src/xterm.c
> index a40440e0da..a329ca59d0 100644
> --- a/src/xterm.c
> +++ b/src/xterm.c
> @@ -27654,6 +27654,8 @@ xi_select_hierarchy_events (struct x_display_info
> *dpyinfo)
> memset (m, 0, l);
> mask.mask_len = l;
>
> + mask.deviceid = XIAllDevices;
> +
> XISetMask (m, XI_PropertyEvent);
> XISetMask (m, XI_HierarchyChanged);
> XISetMask (m, XI_DeviceChanged);
Right, thanks... In retrospect, that was pretty obvious.
Now fixed on master.
- X protocol error, Colin Baxter, 2022/08/17
- Re: X protocol error, Po Lu, 2022/08/17
- Re: X protocol error, Colin Baxter, 2022/08/17
- Re: X protocol error, Robert Pluim, 2022/08/17
- Re: X protocol error, Robert Pluim, 2022/08/17
- Re: X protocol error, Colin Baxter, 2022/08/17
- Message not available
- Re: bug#57261: 29.0.50; X protocol error: XI_BadDevice (invalid Device parameter) on protocol request 131, Re: X protocol error, Robert Pluim, 2022/08/17
- Re: bug#57261: 29.0.50; X protocol error: XI_BadDevice (invalid Device parameter) on protocol request 131, Lars Ingebrigtsen, 2022/08/18
- Re: X protocol error,
Po Lu <=
- Re: X protocol error, Colin Baxter, 2022/08/18