xserver merge requestshttps://gitlab.freedesktop.org/xorg/xserver/-/merge_requests2020-07-20T15:08:38Zhttps://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/479xwayland: Do not use a default seat2020-07-20T15:08:38ZOlivier Fourdanxwayland: Do not use a default seatIf the device does not have an Xwayland seat, we would pick the default
seat of the screen for cursor warping and confinement.
But there is no guarantee that there is a default seat anyway, with e.g.
with weston's headless backend.
So ...If the device does not have an Xwayland seat, we would pick the default
seat of the screen for cursor warping and confinement.
But there is no guarantee that there is a default seat anyway, with e.g.
with weston's headless backend.
So instead of trying the default seat as a fallback, simply ignore
requests for devices where a seat is not set.
Signed-off-by: Olivier Fourdan <ofourdan@redhat.com>https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/672.gitlab-ci: Install xorgproto 2021.4.99.1 from git2021-05-17T08:33:08ZPovilas Kanapickas.gitlab-ci: Install xorgproto 2021.4.99.1 from gitThis is required for the support of upcoming XI 2.4 protocol. See https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/530.
cc @whot
Signed-off-by: Povilas Kanapickas <povilas@radix.lt>This is required for the support of upcoming XI 2.4 protocol. See https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/530.
cc @whot
Signed-off-by: Povilas Kanapickas <povilas@radix.lt>https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/734Draft: xkb don't need SendNewKeyboardNotify event when keyboard devices changed2021-11-06T17:48:22Zzhang haoDraft: xkb don't need SendNewKeyboardNotify event when keyboard devices changedWhen switching input between two different input devices, xorg-server
will call CopyKeyClass function and SendNewKeyboardNotify event, this
behavier cause client receive newKeyboardNotify.
In fact, xogr-server will send the xkbMapNotify...When switching input between two different input devices, xorg-server
will call CopyKeyClass function and SendNewKeyboardNotify event, this
behavier cause client receive newKeyboardNotify.
In fact, xogr-server will send the xkbMapNotify event when
switching the input, and the client will update the keymap after
receiving the xkbMapNotify event.
this commit aim to solve this issue: https://gitlab.freedesktop.org/xorg/xserver/-/issues/1214https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/1391hw/xwayland: fix absolute and relative pointer event flags being flipped2024-03-21T13:23:01ZXaver Huglhw/xwayland: fix absolute and relative pointer event flags being flippedI'm not quite 100% sure if this is correct, but
- "raw" sounds like Wayland relative pointer events to me
- the commit message that introduced the flag, c5c5322ad69b0751f16c785a479b2989b8794235, uses `POINTER_RAWONLY` for relative moveme...I'm not quite 100% sure if this is correct, but
- "raw" sounds like Wayland relative pointer events to me
- the commit message that introduced the flag, c5c5322ad69b0751f16c785a479b2989b8794235, uses `POINTER_RAWONLY` for relative movement elsewhere, so `NORAW` sounds wrong for relative movements here
- this fixes https://bugs.kde.org/show_bug.cgi?id=458233 for me, where the game interprets the compositor side warping from a no-longer locked cursor as relative movement.
Signed-off-by: Xaver Hugl <xaver.hugl@kde.org>