On Tue, 25 Oct 2016 at 14:20:27 -0300, Ben Armstrong wrote:
> I upgraded from libgtk-3-0 3.22.1-1 to 3.22.2-1.
...
> I attempted to open gvim (vim.gtk3 -g), with or without a filename as
> parameter.
...
> (gvim:1904): Gtk-CRITICAL **: gtk_widget_set_size_request: assertion 'width
> >= -1' failed
> *** BUG ***
> In pixman_region32_init_rect: Invalid rectangle passed
> Set a breakpoint on '_pixman_log_error' to debug
What 'guiopts' do you use in gvim? (type ":set guiopts?" into gvim)
Which Gtk theme are you using? I ask because I use vim.gtk3 myself, and
I can't reproduce this with the default Adwaita theme.
It would probably be useful if you can get a backtrace from the crash,
the invalid pixman_region32_init_rect call, and/or the invalid
size request.
The size request is probably the most useful:
$ sudo apt install gdb
$ G_DEBUG=fatal_criticals gdb /usr/bin/vim.gtk3
(gdb) run
... when it crashes with the critical warning you quoted ...
(gdb) thread apply all bt
To make the backtrace useful, you will probably need the libgtk-3-0-dbgsym
and vim-gtk3-dbgsym packages from the debug symbols archive. Please see
<https://wiki.debian.org/HowToGetABacktrace> for more information about
backtraces and debug symbols.
Thanks,
S
