[vim/vim] gvim does not draw status line reliably on hidpi (Issue #19631)

Petr Menšík

unread,

Mar 10, 2026, 2:24:59 PMMar 10

to vim/vim, Subscribed

pemensik created an issue (vim/vim#19631)

Steps to reproduce

have 3 monitors. One fullHD, one with 2560x1440, another one with 2560x1600.
start gvim in windowed mode, vim-X11-9.2.112-2.fc43.x86_64 on Fedora 43.
switch insert modes by insert key or type : commands. They are not rendered
when gvim is maximized, status bar rendering is reliable.

Expected behaviour

status bar is always visible and rendered. When I have maximized mode, it seems to work well. But I need to write something related to other windows.

Version of Vim

9.2.112-2

Environment

OS: Fedora
Desktop: Gnome with wayland
Shell: bash 5.3.0(1)-release

Logs and stack traces

Turned out attempts to trace it by:

- ``ltrace -l libgdk\* gvim -f test.sh``
- ``ltrace -l libwayland\* gvim -f test.sh``

Made it for some reason working. It seems it might be some race condition. I could try to use gdb, but do not know what to try to watch. I can read C code, but not familiar with vim code base.

—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.

Petr Menšík

unread,

Mar 10, 2026, 2:26:37 PMMar 10

to vim/vim, Subscribed

pemensik left a comment (vim/vim#19631)

I can reproduce it reliably, but not sure how to debug it more and narrow the responsible parts. It is broken since I updated to Fedora 43. It works find under terminal vim.

—
Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.

Christian Brabandt

unread,

Mar 10, 2026, 2:27:59 PMMar 10

to vim/vim, Subscribed

chrisbra left a comment (vim/vim#19631)

and it only happens on the hidpi monitors? Did this work with a previous fedora package?

—
Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.

Petr Menšík

unread,

Mar 10, 2026, 2:28:50 PMMar 10

to vim/vim, Subscribed

pemensik left a comment (vim/vim#19631)

it did not happen on previous Fedora releases. It is not a new problem, happens couple of months already, at minimum.

—
Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.

Petr Menšík

unread,

Mar 10, 2026, 2:29:55 PMMar 10

to vim/vim, Subscribed

pemensik left a comment (vim/vim#19631)

There is also Fedora bug for it, if that can help: https://bugzilla.redhat.com/show_bug.cgi?id=2413040

—
Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.

Petr Menšík

unread,

Mar 10, 2026, 2:34:31 PMMar 10

to vim/vim, Subscribed

pemensik left a comment (vim/vim#19631)

if you can help me locating some functions I can watch under gdb, I could try to find a root of the problem. But I am not even sure of terminology for the vim command/status line, how is it called in the code?

—
Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.

Christian Brabandt

unread,

Mar 10, 2026, 3:44:09 PMMar 10

to vim/vim, Subscribed

chrisbra left a comment (vim/vim#19631)

so it does not happen with the non hidpi monitor? And you are using X11 backend? What was the previous version of gvim on Fedora?

—
Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.

Petr Menšík

unread,

Mar 10, 2026, 4:17:54 PMMar 10

to vim/vim, Subscribed

pemensik left a comment (vim/vim#19631)

I think I have used Fedora 41 before. Fedora bug reports starts with version vim-X11-9.1.1818-1.fc42.x86_64. I do not have old enough installation anymore. When I closed the lid with 2560x1600 display and reopened it again, it seems to started drawing status bar correctly. Even not maximized. This is confusing and not reliable enough. But sadly it does happen often.

—
Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.

Petr Menšík

unread,

Mar 11, 2026, 6:39:57 AMMar 11

to vim/vim, Subscribed

pemensik left a comment (vim/vim#19631)

It might be noted my built-in display has aspect ration 16:10, but external displays have 16:9. It might be relevant too.

—
Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.

Petr Menšík

unread,

Mar 11, 2026, 10:23:20 AMMar 11

to vim/vim, Subscribed

pemensik left a comment (vim/vim#19631)

Ah, played with it a bit. Reproduction with 9.2.112 needs scaling on one monitor be set different than the other. Tested it only with built-in monitor and the old full HD one. Used gvim -f --clean -geom 80x25 command. When built-in has scale set to 125%, but HD one has 100% scaling, pressing insert on one of those monitors was always without bottom status bar rendered. No other resizing was done. In my case, it was reliable. It worked on one of monitors, but not on the second. When I configured 125% scale on both, it worked on both. It worked on both also with 100% scaling.

—
Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.

Christian Brabandt

unread,

Mar 11, 2026, 10:30:03 AMMar 11

to vim/vim, Subscribed

chrisbra left a comment (vim/vim#19631)

That sounds like a X11 or graphics driver issue honestly. gvim doesn't care about what monitor it is being displayed.

—
Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.

Petr Menšík

unread,

Mar 11, 2026, 11:16:07 AMMar 11

to vim/vim, Subscribed

pemensik left a comment (vim/vim#19631)

When the window is maximized, it works reliably on all monitors. I am not so sure. But if you know how to debug or trace differences on various monitors, please share some steps. Whatever is the cause, it is quite annoying.

It seems not visible under ltrace, such as in command:
ltrace -l 'libwayland-client.so*' gvim -f --clean -geom 80x25.

—
Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.

Petr Menšík

unread,

Mar 11, 2026, 12:26:48 PMMar 11

to vim/vim, Subscribed

pemensik left a comment (vim/vim#19631)

Found wayland is reporting somehow weird sizes of displays. At least inxi tool displays something not real resolution of those devices.

$ inxi -G
Graphics:
  Device-1: Intel TigerLake-H GT1 [UHD Graphics] driver: i915 v: kernel
  Device-2: Luxvisions Innotech Integrated RGB Camera driver: uvcvideo
    type: USB
  Display: wayland server: X.Org v: 24.1.9 with: Xwayland v: 24.1.9
    compositor: gnome-shell v: 49.4 driver: X: loaded: modesetting
    unloaded: fbdev,vesa dri: iris gpu: i915 resolution: 1: 5120x2880~60Hz
    2: 3840x2160~60Hz 3: 4096x2560~60Hz
  API: OpenGL v: 4.6 vendor: intel mesa v: 25.3.6 renderer: Mesa Intel UHD
    Graphics (TGL GT1)
  API: Vulkan v: 1.4.341 drivers: intel,llvmpipe surfaces: N/A
  API: EGL Message: EGL data requires eglinfo. Check --recommends.
  Info: Tools: api: glxinfo,vulkaninfo x11: xdriinfo, xdpyinfo, xprop,
    xrandr

But in the end, the differences should not matter. Is there some way of debug logging or verbose mode?

—
Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.

twjobs2005

unread,

Mar 16, 2026, 5:32:51 PMMar 16

to vim/vim, Subscribed

twjobs2005 left a comment (vim/vim#19631)

interesting: my bug may be related? #19723

—
Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.

Petr Menšík

unread,

Mar 18, 2026, 7:17:41 AMMar 18

to vim/vim, Subscribed

pemensik left a comment (vim/vim#19631)

Oh, I can confirm it gets fixed with window resize or addition of new tab by --remote-tab. Testing related to #17982. Does not seem to matter in which way the resize is done.

—
Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.

Eric L.

unread,

4:26 AM (8 hours ago) 4:26 AM

to vim/vim, Subscribed

ericzolf left a comment (vim/vim#19631)

I'm the one who reported the issue under Fedora and IIRC the issue appeared when switching from Cinnamon/X11 to Gnome/Wayland. Two displays are enough for me to reproduce the issue 😏

image.png (view on web) image.png (view on web) I suspect Wayland and the different scaling between both screens.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!
You are receiving this because you are subscribed to this thread.

Eric L.

unread,

4:30 AM (8 hours ago) 4:30 AM

to vim/vim, Subscribed

ericzolf left a comment (vim/vim#19631)

It was actually easy to check: when setting both scales at 100% or even 125%, then the issue disappears. Back to the differing scaling, the issue appears again, but only when opening gvim on the internal monitor (the one at 125%).

—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!

You are receiving this because you are subscribed to this thread.

Reply all

Reply to author

Forward