GNOME Bugzilla – Bug 773012
[gnome-terminal][wayland] resizing window too large leads to crash
Last modified: 2021-07-05 13:49:22 UTC
Created attachment 337776 [details] journaclctl output containing core backtrace and some log context Hi, I am running Arch Linux with wayland and after the update to 3.22 gnome-terminal would core dump on startup. The profile I was using had a terminal size of 511x511. The core dump goes away if I reduce the terminal size to 80x24. I attached the log output from journalctl, but I tried to cut it down to the lines that seemed important. So there might be stuff missing. Let me know if you need more information. Cheers, Robert
Oct 15 15:26:02 org.gnome.Shell.desktop[4139]: Window manager warning: Could not import pending buffer, ignoring commit: Failed to create texture 2d due to size/format constraints Oct 15 15:26:02 gnome-terminal-[4270]: Error flushing display: Broken pipe So this was g-t trying to resize the window to a size that's too large for the windowing system. IMHO this a bug in gdk/gtk; it shouldn't be processing a resize that will be too large. -> gtk:wayland
Unfortunately the actual size limit is the texture size which varies between hardware.
If anything, this is mutter who eventually raises the protocol error. See bug 770387.
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org which have not seen updates for a longer time (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version, then please follow https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines and create a new ticket at https://gitlab.gnome.org/GNOME/mutter/-/issues/ Thank you for your understanding and your help.