On Fri, Feb 26, 2021 at 02:28:24PM -0000, Marton Danko wrote: >Hi Coiby, > >Thanks, it seems that correctly telling which hardware button do I press. >Right: >-event18 POINTER_BUTTON +0.174s BTN_RIGHT (273) pressed, seat count: 1 > event18 POINTER_BUTTON +0.318s BTN_RIGHT (273) released, seat count: 0 >Middle: > event18 POINTER_BUTTON +3.086s BTN_MIDDLE (274) pressed, seat count: 1 > event18 POINTER_BUTTON +3.362s BTN_MIDDLE (274) released, seat count: 0 >Left: > event18 POINTER_BUTTON +5.132s BTN_LEFT (272) pressed, seat count: 1 > event18 POINTER_BUTTON +5.271s BTN_LEFT (272) released, seat count: 0 > >And in the mentioned bug report the following resolution works: >"Apparently it's a change they did in GNOME 3.28 and can be fixed by switching to Area mouse click emulation in GNOME Tweaks." >
Good to know that:)
>Thanks for your help, and now I need to go to the corner to cry again, >why such a stupid default configuration is shipped with the system... >
You are welcome!
On Fri, Feb 26, 2021 at 02:28:24PM -0000, Marton Danko wrote:
>Hi Coiby,
>
>Thanks, it seems that correctly telling which hardware button do I press.
>Right:
>-event18 POINTER_BUTTON +0.174s BTN_RIGHT (273) pressed, seat count: 1
> event18 POINTER_BUTTON +0.318s BTN_RIGHT (273) released, seat count: 0
>Middle:
> event18 POINTER_BUTTON +3.086s BTN_MIDDLE (274) pressed, seat count: 1
> event18 POINTER_BUTTON +3.362s BTN_MIDDLE (274) released, seat count: 0
>Left:
> event18 POINTER_BUTTON +5.132s BTN_LEFT (272) pressed, seat count: 1
> event18 POINTER_BUTTON +5.271s BTN_LEFT (272) released, seat count: 0
>
>And in the mentioned bug report the following resolution works:
>"Apparently it's a change they did in GNOME 3.28 and can be fixed by switching to Area mouse click emulation in GNOME Tweaks."
>
Good to know that:)
>Thanks for your help, and now I need to go to the corner to cry again,
>why such a stupid default configuration is shipped with the system...
>
You are welcome!