am getting a CRITICAL error using gvim and linux

[Charles E Campbell]

Here it is:

** (gvim:62530): CRITICAL **: murrine_style_draw_box: assertion
'width >= -1' failed

Suggestions appreciated.

Regards,
Chip Campbell

Info:

uname -a:
Linux djinni.campbellfamily.biz 3.10.0-327.el7.x86_64 #1 SMP Fri Nov 20
11:12:42 CST 2015 x86_64 x86_64 x86_64 GNU/Linux

cat /etc/system-release:
Scientific Linux release 7.3 (Nitrogen)

vim --version:
VIM - Vi IMproved 8.0 (2016 Sep 12, compiled May 17 2017 23:30:31)
Included patches: 1-599
Compiled by c...@djinni.campbellfamily.biz
Huge version with GTK2 GUI. Features included (+) or not (-):
+acl +file_in_path +mouse_sgr +tag_old_static
+arabic +find_in_path -mouse_sysmouse -tag_any_white
+autocmd +float +mouse_urxvt -tcl
+balloon_eval +folding +mouse_xterm +termguicolors
+browse -footer +multi_byte +terminfo
++builtin_terms +fork() +multi_lang +termresponse
+byte_offset +gettext -mzscheme +textobjects
+channel -hangul_input +netbeans_intg +timers
+cindent +iconv +num64 +title
+clientserver +insert_expand +packages +toolbar
+clipboard +job +path_extra +user_commands
+cmdline_compl +jumplist -perl +vertsplit
+cmdline_hist +keymap +persistent_undo +virtualedit
+cmdline_info +lambda +postscript +visual
+comments +langmap +printer +visualextra
+conceal +libcall +profile +viminfo
+cryptv +linebreak -python +vreplace
+cscope +lispindent -python3 +wildignore
+cursorbind +listcmds +quickfix +wildmenu
+cursorshape +localmap +reltime +windows
+dialog_con_gui -lua +rightleft +writebackup
+diff +menu -ruby +X11
+digraphs +mksession +scrollbind -xfontset
+dnd +modify_fname +signs +xim
-ebcdic +mouse +smartindent +xpm
+emacs_tags +mouseshape +startuptime +xsmp_interact
+eval +mouse_dec +statusline +xterm_clipboard
+ex_extra -mouse_gpm -sun_workshop -xterm_save
+extra_search -mouse_jsbterm +syntax
+farsi +mouse_netterm +tag_binary
system vimrc file: "$VIM/vimrc"
user vimrc file: "$HOME/.vimrc"
2nd user vimrc file: "~/.vim/vimrc"
user exrc file: "$HOME/.exrc"
system gvimrc file: "$VIM/gvimrc"
user gvimrc file: "$HOME/.gvimrc"
2nd user gvimrc file: "~/.vim/gvimrc"
defaults file: "$VIMRUNTIME/defaults.vim"
system menu file: "$VIMRUNTIME/menu.vim"
fall-back for $VIM: "/usr/local/share/vim"
Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK -pthread
-I/usr/include/gtk-2.0 -I/usr/lib64/gtk-2.0/include
-I/usr/include/atk-1.0 -I/usr/include/cairo
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0
-I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include
-I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng15
-I/usr/include/libdrm -I/usr/include/harfbuzz -O2
-fno-strength-reduce -Wall -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1
Linking: gcc -L/usr/local/lib -Wl,--as-needed -o vim -lgtk-x11-2.0
-lgdk-x11-2.0 -latk-1.0 -lgio-2.0 -lpangoft2-1.0 -lpangocairo-1.0
-lgdk_pixbuf-2.0 -lcairo -lpango-1.0 -lfontconfig -lgobject-2.0
-lglib-2.0 -lfreetype -lSM -lICE -lXpm -lXt -lX11 -lSM -lICE -lm
-ltinfo -lelf -lnsl -lselinux -lacl -lattr -ldl

[Tony Mechelynck]

On Thu, May 18, 2017 at 5:35 AM, Charles E Campbell
<drc...@campbellfamily.biz> wrote:
>
> Here it is:
>
> ** (gvim:62530): CRITICAL **: murrine_style_draw_box: assertion 'width >=
> -1' failed
>
> Suggestions appreciated.
>
> Regards,
> Chip Campbell

[...]

Is that at every startup (even with -u
/usr/local/share/vim/vim80/defaults.vim) or do you know of any
circumstances making the problem happen or nor happen?

Or is that a link-time error (at which version and patchlevel)?

Best regards,
Tony.

[Nikolay Aleksandrovich Pavlov]

? AFAIK linker is not a thing which may trigger assertion error. Also
OP has `vim --version` output which he could not if it was a link time
problem.

>
> Best regards,
> Tony.
>
> --
> --
> You received this message from the "vim_use" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups "vim_use" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+u...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[Charles E Campbell]

Hello:

gvim/vim compiled and linked ok; when I started it up that CRITICAL
message resulted (I'd just wiped out my vim directory+contents, gotten
the code via git, re-compiled, and was doing a test-run to insure that
it actually did compile&link correctly with gvim enabled). I haven't
been getting it lately, though, and a search of vim's code doesn't show
any "murrine" strings in it, so I don't know where that message came from.

Regards,
Chip Campbell

[Tim Chase]

On 2017-05-18 11:04, Charles E Campbell wrote:
> gvim/vim compiled and linked ok; when I started it up that CRITICAL
> message resulted (I'd just wiped out my vim directory+contents,
> gotten the code via git, re-compiled, and was doing a test-run to
> insure that it actually did compile&link correctly with gvim
> enabled). I haven't been getting it lately, though, and a search
> of vim's code doesn't show any "murrine" strings in it, so I don't
> know where that message came from.

I suspect that it's a GTK-theme error/warning. Now whether it's a
false alarm on the theme's part, or gvim sending out-of-bounds
parameters, it might take a bit more debugging.

-tim

[stosss]

After an update I started getting some GTK-theme message when starting "gvim -p *.php *.txt" in a terminal window in my file manager. After another update it went away.