[vim/vim] gvim 9.1: resizing the window create transparent rows and columns (Issue #14233)
Victor Stinner
Steps to reproduce
- Open a text file which is larger than the window
- Edit the text, if possible near the bottom-right (or at least near the center)
- Then resize the window to marge it larger. If possible, larger than the open dialog (see step 3, it's just make the bug easier to spot)
- Click on the File menu > Open
- See that some rows and lines are transparents
Expected behaviour
Text is renderer properly
Version of Vim
vim-X11-9.1.158-1.fc39.x86_64
Environment
- OS: Fedora 39
- Tterminal: GNOME Terminal 3.50.1 (but I'm using gvim)
- Value of $TERM: xterm-256color
- Shell: bash-5.2.26-1.fc39.x86_64
- Xwayland: xorg-x11-server-Xwayland-23.2.4-1.fc39.x86_64
- Gtk: gtk3-3.24.41-1.fc39.x86_64 (gvim is linked to /lib64/libgtk-3.so.0)
Logs and stack traces
No response
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
Christian Brabandt
can you please share a screen shot of the issue?
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
Victor Stinner
Screenshot showing light rows and columns which are in fact my GNOME background since the gvim windows became partially transparent!
Capture.d.ecran.du.2024-03-19.16-54-05.png (view on web)
After a few edits + resize, gvim becomes completely unusuable, I cannot read text anymore :-(
Capture.d.ecran.du.2024-03-19.16-55-38.png (view on web)
Note: on my screen, it's rendered differently. Photo with my phone camera:
Sorry for the bad photo quality. It's just to show that it's very different on screen than using GNOME screenshot tool.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
Christian Brabandt
Is this wayland or X11 environment? Does it happen in the other one?
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
Victor Stinner
Is this wayland or X11 environment? Does it happen in the other one?
gvim is using X11, GNOME and all other applications are using Wayland. That's why I mentioned Xwayland which is started to run gvim.
Is there a way to run gvim with Wayland?
I started to have this issue after a Fedora update, but I don't know when exactly. "In February". I know for sure that I had this issue at February 20, 2024 since I posted my bug on my Mastodon profile :-)
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
Victor Stinner
Oh, to check if gvim or another app is used X11 or not, I run import screenshot in a terminal: if the mouse cursor changes on an app, it uses X11, since import is a X11 app :-)
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
Victor Stinner
Closed #14233 as completed.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
Victor Stinner
Sorry, the bug is not in gvim but somewhere lower, such as Mesa.
- If I run vim with
GVIM_ENABLE_WAYLAND=1, I cannot reproduce the bug anymore (gvim using Wayland). - If I put
XWAYLAND_NO_GLAMOR=1in/etc/environment, I cannot reproduce the bug anymore (gvim using X11, Xwayland no longer uses hardware optimizations).
I downgraded my Linux kernel from 6.7.9-200.fc39.x86_64 to kernel-6.7.1-200.fc39.x86_64, I can still reproduce the bug. So the kernel should not be in the kernel driver on my "Intel Comet Lake GT2" GPU (IGP?).
It may be a Mesa regression. Anyway, I close this vim bug report.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
Olivier Fourdan
That seems to be a regression in GLAMOR, see https://gitlab.freedesktop.org/xorg/xserver/-/issues/1655
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
Christian Brabandt
thansk for updating here!
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
Victor Stinner
Workarounds:
- Run gvim with
GVIM_ENABLE_WAYLAND=1environmenet variable. - or: Put
XWAYLAND_NO_GLAMOR=1in/etc/environment.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
Vineet Gupta
Run gvim with GVIM_ENABLE_WAYLAND=1 environmenet variable.
Unfortunately this doesn't help.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
Enno Gröper
egroeper left a comment (vim/vim#14233)I suppose GVIM_ENABLE_WAYLAND=1 doesn't work with Ubuntu 24.04, since it was introduced with 9.1.0064 and Ubuntu 24.04 ships with 9.1.0016 (9.1.0016-1ubuntu7.7).
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
Christian Brabandt
chrisbra left a comment (vim/vim#14233)well, compile your own version then
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
Vineet Gupta
vineetgarc left a comment (vim/vim#14233)I tried building vim - making it build for gui is a reckoning of its own. Even if you figure out the magic incantations, there's a high change installing the various X dev packages will hose your existing working desktop env which is what exactly happened to me. Perhaps need to do this in a sandbox.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
Fausto B
fausterix left a comment (vim/vim#14233)Hi!
Any workaround?
I'm on Ubuntu 24.04.3 LTS and XDG_SESSION_TYPE=wayland
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.