Loading ...
Sorry, an error occurred while loading the content.

Re: Gtk-warning with one of the recent patches.

Expand Messages
  • Charles Campbell
    ... When I play Mines, that occasionally produced Gtk-WARNING **: unable to find signal handler messages , but --sync does appear to have cleared them up (I
    Message 1 of 4 , Sep 27, 2011
    • 0 Attachment
      Tony Mechelynck wrote:
      > On 26/09/11 22:34, Charles Campbell wrote:
      >> Charles Campbell wrote:
      >>> Hello,
      >>>
      >>> I've been getting these messages in the shell after exiting vim:
      >>>
      >>> (gvim:16151): Gtk-WARNING **: unable to find signal handler for
      >>> object(GtkWindow:0xac9380) with func(0x5e4f1e) and data(0xafd030)
      >>>
      >>> and
      >>>
      >>> (gvim:16320): Gtk-WARNING **: unable to find signal handler for
      >>> object(GtkDrawingArea:0x1f44ec0) with func(0x5e4dca) and
      >>> data(0x2271800)
      >>>
      >>> (gvim:16320): Gtk-WARNING **: unable to find signal handler for
      >>> object(GtkWindow:0x1f1e380) with func(0x5e4f1e) and data(0x2271800)
      >>>
      >>> (gvim:16320): Gtk-WARNING **: unable to find signal handler for
      >>> object(GtkDrawingArea:0x1f44ec0) with func(0x5e4dca) and
      >>> data(0x2271800)
      >>>
      >>> (gvim:16320): Gtk-WARNING **: unable to find signal handler for
      >>> object(GtkWindow:0x1f1e380) with func(0x5e4f1e) and data(0x2271800)
      >>>
      >>> (gvim:16320): Gtk-WARNING **: unable to find signal handler for
      >>> object(GtkDrawingArea:0x1f44ec0) with func(0x5e4dca) and
      >>> data(0x2271800)
      >>>
      >>> (gvim:16320): Gtk-WARNING **: unable to find signal handler for
      >>> object(GtkWindow:0x1f1e380) with func(0x5e4f1e) and data(0x2271800)
      >>>
      >>> They don't seem to disturb vim's operation any, however.
      >>>
      >>> VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Sep 23 2011 14:57:52)
      >>> Included patches: 1-322
      >>> Compiled by cecampbe@...
      >>> Huge version with GTK2 GUI.
      >> Hello,
      >>
      >> More info on this: its not due to a recent vim patch; its appearing when
      >> I try using a vim 7.3 with no patches. I presume that gtk got updated on
      >> my system and has contributed these nice warnings.
      >>
      >> Regards,
      >> Chip Campbell
      >>
      >
      > Do you get them also when running gvim with the --sync command-line
      > switch? X11 commands are normally asynchronous, and fatal X errors
      > give (at least under GTK2) messages recommending to run the program
      > with --sync to make the error debuggable, but some of these errors
      > disappear when you do. I imagine that the warninigs you see might be
      > due to trying to display something in a window, or part of one, after
      > they have been destroyed... or something.
      >
      > See :help gui-gtk
      When I play Mines, that occasionally produced "Gtk-WARNING **: unable to
      find signal handler messages", but --sync does appear to have cleared
      them up (I played two games, just as a test, of course) (and oh, I won
      both of them!).

      However,
      gvim --sync . (which invokes netrw)
      :GVColors
      :q

      still results in 26 of them. (GVColors can be had from
      http://drchip.0sites.net/astronaut/vim/index.html#GVCOLORS )

      Thank you,
      Chip Campbell

      --
      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
    Your message has been successfully submitted and would be delivered to recipients shortly.