[vim/vim] GVim crashes with "Error flushing display: Resource temporarily unavailable" when deleting many lines with `:g` with `clipboard=unnamedplus` (Issue #19203)

5 views
Skip to first unread message

Xidorn Quan

unread,
Jan 17, 2026, 6:38:51 PMJan 17
to vim/vim, Subscribed
upsuper created an issue (vim/vim#19203)

Steps to reproduce

  1. Use GVim to open a large file, for example https://github.com/SoftManiaTech/sample_log_files/blob/master/Linux/Linux_2k.log
  2. set clipboard=unnamedplus
  3. :g!/su/d

Expected behaviour

GVim is still alive with lines lacking su be removed, but it crashes.

Version of Vim

9.1.2090 (latest master)

Environment

Operating System: Ubuntu 25.10
Desktop Environment: GNOME 49 (Wayland)

Logs and stack traces

Gdk-Message: 10:34:33.454: Error flushing display: Resource temporarily unavailable


Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/19203@github.com>

Xidorn Quan

unread,
Jan 18, 2026, 12:45:03 AMJan 18
to vim/vim, Subscribed
upsuper left a comment (vim/vim#19203)

I did (ask LLM to) do some investigation, which suggested me to attach WAYLAND_DEBUG=1 to see some diagnose information, but weirdly when I add that env var, GVim stops crashing on the STR. It feels like some timing / race condition.


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/19203/3764943667@github.com>

Christian Brabandt

unread,
Jan 18, 2026, 3:23:23 AMJan 18
to vim/vim, Subscribed
chrisbra left a comment (vim/vim#19203)

It crashes or does not crash?


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/19203/3765049218@github.com>

Xidorn Quan

unread,
Jan 18, 2026, 3:24:55 AMJan 18
to vim/vim, Subscribed
upsuper left a comment (vim/vim#19203)

It crashes with the original STR, but if GVim runs with WAYLAND_DEBUG=1 then it doesn't crash.


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/19203/3765050292@github.com>

Christian Brabandt

unread,
Jan 18, 2026, 3:31:58 PMJan 18
to vim/vim, Subscribed
chrisbra left a comment (vim/vim#19203)

and with crash you mean the process has been exited? Or is vim still running?


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/19203/3765714704@github.com>

Xidorn Quan

unread,
Jan 18, 2026, 3:46:46 PMJan 18
to vim/vim, Subscribed
upsuper left a comment (vim/vim#19203)

By crash I mean vim quits abruptly. The window gets closed and the process is exited.


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/19203/3765727822@github.com>

Benjamin Cohen

unread,
Jan 26, 2026, 12:53:30 PMJan 26
to vim/vim, Subscribed
ben-cohen-xs left a comment (vim/vim#19203)

This happens to me as well, with set clipboard=unnamed. I am running Fedora 43 with GNOME 49.3.


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/19203/3800881247@github.com>

Reply all
Reply to author
Forward
0 new messages