CHIRP

Yup. CHIRP uses wxwidgets for cross-platform UI compatibility and wxGTK has always been a bit problematic on Wayland. On 24.04 it seems worse (but still usable, IMHO). You can try setting GDK_BACKEND in the environment:

$ GDK_BACKEND=x11 chirp

Which seems to make it less chunky for me, but maybe also not as responsive.

Also, I don't think it's a "refresh fast enough" problem as in my experience you can drag the scroll bar on the right at pretty high speed and it responds just fine, it's the scroll wheel input that gets delayed, batched, or whatever.

Ah okay, yeah I definitely don't see that corrupted redrawing on my system, just the slowness. Does it still happen with the GDK_BACKEND override I described above? That forces GTK to use the older x11 renderer.

Either way, CHIRP isn't involved in the low-level drawing or scrolling at all, that's all handled by the widget toolkit (wx) and the drawing engine it uses (gtk) so I'm not sure there's anything I can do about it.

Dan Smith wrote in #note-4:

Ah okay, yeah I definitely don't see that corrupted redrawing on my system, just the slowness. Does it still happen with the GDK_BACKEND override I described above? That forces GTK to use the older x11 renderer.

Either way, CHIRP isn't involved in the low-level drawing or scrolling at all, that's all handled by the widget toolkit (wx) and the drawing engine it uses (gtk) so I'm not sure there's anything I can do about it.

The override seems to fix it.

And about wx, do you know where one could report this issue?

Cool, if the override fixes it then it's almost definitely wx/GTK related I think. Technically chirp tries to set that internally but it no longer seems to be doing it early enough to matter. Can you try running chirp with --no-linux-gdk-backend to make sure it's not a problem of that being internally set halfway through initializing GTK or something? I should probably remove that hack altogether now that it doesn't seem to work.

I assume report here:

https://github.com/wxWidgets/wxWidgets

There are other wayland-related bugs, like this close to the top of the stack:

https://github.com/wxWidgets/wxWidgets/issues/24443

So there may be another bug you can find that is relevant.

Please be mindful that those people generally want a standalone reproducer (or to show that it happens on one of the demo apps they provide). They can't be expected to install and try CHIRP, dig through the code, etc. Just...please avoid asking them to support CHIRP :)

chirp --no-linux-gdk-backend still has the problem.

Okay, that's "good". I was able to move the initialization around a bit so that the current attempt to set GDK_BACKEND=x11 internally works again. So I'll queue that for a future build, which will make it default to x11 mode unless you pass that flag, which will make it wayland-native.