The problem is evidently between gvim (vim-X11), GTK, and Wayland. I cannot be sure where it is. Setting component to "vim", because no other applicaon appears to suffer from this. The symptom is this: if I resize the gvim window, it acquires a permanent damage, which application level refresh does not cure. Usually the damage corresponds to vertical lines where the window decorations were when resizing. In the attached screencal, I used a selection on purpose in order to identify the problem. Reproducible: Always Steps to Reproduce: 1. run gvim 2. resize 3. observe permanent damage to the canvas Actual Results: Text in editor is unreadable. Expected Results: Text is readable as before, in F38. The problem is actually a regression in F39. I hoped the F40 would fix it, but it didn't. Still happens. Observe that the system screenshot function saves the damage as "transparency". I attach 2 screenshot: with a camera (as I see it) and with system capture. vim-X11-9.1.354-1.fc40.x86_64
Created attachment 2032257 [details] As seen by human or camera
Created attachment 2032258 [details] As captured by the screen capture
Hi Pete, I'm sorry, I was not able to see the screen issues in GVim which you mentioned - neither with my vimrc or without any vimrc or plugins. I have Fedora 40 Gnome with Wayland, resized the window by mouse and didn't get the issue. Is there another way how to resize Gvim window? Or can you share the file you made screenshot on, so I could try to look into those specific lines?
The file does not matter. But the system has to do something for this to crop up. Just now when I received a NEEDINFO from Bugzilla, there was no problem for me either. I opened a few windows, resized them, and nothing. So I started OpenSCAD, browsed YouTube, and then it appeared. One other thing, the resize has to be somewhat brisk. It will not appear if I drag the decoration slowly.
Do let me know if you have steps which trigger the issue every time, ideally in clean VM. Otherwise I'm not able to do much about it, sorry. Closing for now, we can reopen once there are the steps which trigger the issue every time.