gtk warnings after netrw.vim update in vim 7.3.347
Ivan Krasilnikov
After updating to vim 7.3.347+ I started to get "Gtk-WARNING **:
unable to find signal handler for object ..." warnings in console
while using gvim.
I build vim with flags --with-features=huge --enable-gui=gnome2.
Here is how I can reliable reproduce the problem on my system (a
customized Ubuntu 10.04):
$ cd ~
$ echo 'syntax on' >.vimrc
$ gvim -c ':tabe .' -c ':q' -c ':tabe .' -c ':qa!' .vimrc
(gvim:11287): Gtk-WARNING **: unable to find signal handler for
object(GtkDrawingArea:0x1de2e30) with func(0x5a41f0) and
data(0x1ccf950)
(gvim:11287): Gtk-WARNING **: unable to find signal handler for
object(GnomeApp:0x1dce000) with func(0x5a40d0) and data(0x1ccf950)
gvim --sync flag suggested on vim_dev a while ago doesn't help.
The problem seems to have been triggered by the latest update of netrw.vim:
http://code.google.com/p/vim/source/diff?spec=svn37ecb8ff4560&r=37ecb8ff4560&format=side&path=/runtime/autoload/netrw.vim
tyru
https://gist.github.com/1393489
My memory is not clear but maybe the warnings occurred when jumping across windows.
but I don't use netrw.vim. (I use vimfiler.vim instead)
My environment is Linux Mint 11.
My :version is:
VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Nov 1 2011 22:12:46)
Included patches: 1-353
Huge version with GTK2 GUI. Features included (+) or not (-):
+arabic +autocmd +balloon_eval +browse ++builtin_terms +byte_offset +cindent +clientserver +clipboard +cmdline_compl +cmdline_hist
+cmdline_info +comments +conceal +cryptv +cscope +cursorbind +cursorshape +dialog_con_gui +diff +digraphs +dnd -ebcdic +emacs_tags
+eval +ex_extra +extra_search +farsi +file_in_path +find_in_path +float +folding -footer +fork() +gettext -hangul_input +iconv
+insert_expand +jumplist +keymap +langmap +libcall +linebreak +lispindent +listcmds +localmap -lua +menu +mksession +modify_fname
+mouse +mouseshape +mouse_dec -mouse_gpm -mouse_jsbterm +mouse_netterm -mouse_sysmouse +mouse_xterm +mouse_urxvt +multi_byte
+multi_lang -mzscheme +netbeans_intg +path_extra -perl +persistent_undo +postscript +printer +profile +python -python3 +quickfix
+reltime +rightleft -ruby +scrollbind +signs +smartindent -sniff +startuptime +statusline -sun_workshop +syntax +tag_binary
+tag_old_static -tag_any_white -tcl +terminfo +termresponse +textobjects +title +toolbar +user_commands +vertsplit +virtualedit
+visual +visualextra +viminfo +vreplace +wildignore +wildmenu +windows +writebackup +X11 -xfontset +xim +xsmp_interact
+xterm_clipboard -xterm_save
system vimrc file: "$VIM/vimrc"
user vimrc file: "$HOME/.vimrc"
user exrc file: "$HOME/.exrc"
system gvimrc file: "$VIM/gvimrc"
user gvimrc file: "$HOME/.gvimrc"
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/atk-1.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pixman-1 -g -O2 -D_FORTIFY_SOURCE=1
Linking: gcc -L/usr/lib/i386-linux-gnu -L/usr/local/lib -Wl,--as-needed -o vim -pthread -L/usr/lib/i386-linux-gnu -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgio-2.0 -lpangoft2-1.0 -lpangocairo-1.0 -lgdk_pixbuf-2.0 -lm -lcairo -lpango-1.0 -lfreetype -lfontconfig -lgobject-2.0 -lgmodule-2.0 -lgthread-2.0 -lrt -lglib-2.0 -lSM -lICE -lXpm -lXt -lX11 -lXdmcp -lSM -lICE -lm -lncurses -lnsl -L/usr/lib/python2.7/config -lpython2.7 -lpthread -ldl -lutil -lm -Xlinker -export-dynamic -Wl,-O1 -Wl,-Bsymbolic-functions
(sorry for lots of missing information though...)
--
You received this message from the "vim_dev" 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
Ivan Krasilnikov
inside removeEventHandler() at gui_beval.c:479..487 as a result of
some "let &beval = ..." statement.
Apparently, removeEventHandler() is called twice somewhere.
Bram Moolenaar
Ivan Krasilnikov wrote:
Just guessing, does this patch solve the problem:
*** ../vim-7.3.353/src/option.c 2011-10-12 16:57:07.000000000 +0200
--- src/option.c 2011-11-29 22:42:04.000000000 +0100
***************
*** 7771,7779 ****
#ifdef FEAT_BEVAL
else if ((int *)varp == &p_beval)
{
! if (p_beval == TRUE)
gui_mch_enable_beval_area(balloonEval);
! else
gui_mch_disable_beval_area(balloonEval);
}
#endif
--- 7771,7779 ----
#ifdef FEAT_BEVAL
else if ((int *)varp == &p_beval)
{
! if (p_beval && !old_value)
gui_mch_enable_beval_area(balloonEval);
! else if (!p_beval && old_value)
gui_mch_disable_beval_area(balloonEval);
}
#endif
--
panic("Foooooooood fight!");
-- In the kernel source aha1542.c, after detecting a bad segment list
/// Bram Moolenaar -- Br...@Moolenaar.net -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
Charles Campbell
> Ivan Krasilnikov wrote:
>
>
>> Attached are stack traces of these warnings. Warnings are printed
>> inside removeEventHandler() at gui_beval.c:479..487 as a result of
>>
>> Apparently, removeEventHandler() is called twice somewhere.
>>
> Just guessing, does this patch solve the problem:
>
>
> *** ../vim-7.3.353/src/option.c 2011-10-12 16:57:07.000000000 +0200
> --- src/option.c 2011-11-29 22:42:04.000000000 +0100
> ***************
> *** 7771,7779 ****
> #ifdef FEAT_BEVAL
> else if ((int *)varp ==&p_beval)
> {
> ! if (p_beval == TRUE)
> gui_mch_enable_beval_area(balloonEval);
> ! else
> gui_mch_disable_beval_area(balloonEval);
> }
> #endif
> --- 7771,7779 ----
> #ifdef FEAT_BEVAL
> else if ((int *)varp ==&p_beval)
> {
> gui_mch_enable_beval_area(balloonEval);
> ! else if (!p_beval&& old_value)
> gui_mch_disable_beval_area(balloonEval);
> }
> #endif
>
>
Thank you,
Chip Campbell
tyru
Ivan Krasilnikov
> Just guessing, does this patch solve the problem:
Yes. It fixed the warnings for me. Thank you.