Rendering glitch while scrolling results on Wayland/Hyprland during deceleration

[daniel-g-carrasco]

Summary

Walker shows a rendering glitch while scrolling results with the mouse wheel or touchpad on Wayland/Hyprland.

This is not just a small overscroll drift: during scroll deceleration, list rows visually split/duplicate in a strange way. Text and icons appear briefly redrawn in the wrong position while the scrolling slows down to a stop.

Environment

• OS: Arch Linux
• Session: Wayland
• Compositor: Hyprland 0.54.3-2
• Walker: 2.16.0-1
• Elephant: 2.21.0-1
• GTK4: 4.22.2-1
• Kernel package installed: linux 6.19.12.arch1-1
• Running kernel during reproduction:
  • Linux fw13daniel 6.19.11-arch1-1 #1 SMP PREEMPT_DYNAMIC Thu, 02 Apr 2026 23:33:01 +0000 x86_64 GNU/Linux

Reproduction

1. Open Walker.
2. Scroll the results list using the touchpad or mouse wheel.
3. Release the scroll gesture and let the scrolling decelerate naturally.
4. During deceleration, rows/icons/text visibly glitch, split, or duplicate briefly.

Expected behavior

Smooth scrolling until stop, with no duplicated or displaced rows/text/icons.

Actual behavior

During scroll slowdown/deceleration, Walker redraws parts of the list incorrectly:

• icons briefly appear duplicated or displaced
• text appears split / redrawn in the wrong place
• the issue happens repeatedly, not only at the very end of the list

What I already ruled out

I tested all of the following and the glitch still happens:

1. Custom themed Walker

   • custom CSS/layout/theme

2. Clean Walker with isolated config/cache

   • separate XDG_CONFIG_HOME
   • separate XDG_CACHE_HOME
   • no local theme/config overrides

3. Different GTK renderer path

   • forced GSK_RENDERER=cairo

4. ScrolledWindow theme/layout tweaks

   • overlay-scrolling=false
   • kinetic-scrolling=false
   • propagate-natural-height=false
   • propagate-natural-width=false

The glitch persists in all cases above.

That strongly suggests this is not caused by my local Walker theme/config, but by Walker itself or its GTK/list rendering path under this stack.

Additional context

• fuzzel on the same machine does not show this kind of problem.
• I have a screen recording showing the issue and can attach it to the issue.

[daniel-g-carrasco]

Above the screen recording:

2026-04-19_23-06-36.small.mp4

[abenz1267]

this falls strongly under the "i couldn't care less"-category ngl. i've never once scrolled through walker using my mouse.