Annoying GLib-GObject-WARNING messages when starting gvim

[John Little]

Since late last year, whenever I start gvim, I get these warnings on standard error:

(gvim:10602): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::sm-connect after class was initialised

(gvim:10602): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::show-crash-dialog after class was initialised

(gvim:10602): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::display after class was initialised

(gvim:10602): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::default-icon after class was initialised

This now on Kubuntu 14.04, built from source (I've put off addressing this until I got around to upgrading from 13.10).

My understanding is that they're caused by some now unmaintained gnome library when it calls something GTK, so it's not something we can fix in vim source.

Now, the gvim in the Ubuntu repositories does not give these warnings, so I conclude it is possible to build gvim without them. Does anyone here know how?

Regards, John Little

[Christian Brabandt]

I noticed those too. IIRC, those were warnings from a policy change in
the GObject class of glib 2.38¹, but I think, those warnings have been
reverted later² on.

The only workaround until this is fixed in your distribution is to
install vim-gtk instead of the vim-gnome one.

¹https://git.gnome.org/browse/glib/tree/NEWS?id=2.38.0
²https://bugzilla.gnome.org/show_bug.cgi?id=698614

Best,
Christian
--
Demokratie ist wenn zehn Füchse und ein Hase darüber abstimmen,
was es heute zum Abendessen gibt.
Freiheit ist, wenn der Hase mit einer Schrotflinte die Wahl
anfechten kann.
-- Vince Ebert

[John Little]

On Friday, August 8, 2014 4:05:22 AM UTC+12, Christian Brabandt wrote:

> ... I think, those warnings have been
> reverted later² on.

That's good news, I hadn't found bug 698614. I suspected a GTK 3 hidden agenda.

> The only workaround until this is fixed in your distribution is to
> install vim-gtk instead of the vim-gnome one.

That doesn't work for me, I build my own vim. I have vim-gtk installed, not vim-gnome anyway.

Regards, John Little

[John Little]

On Friday, August 8, 2014 10:46:13 AM UTC+12, John Little wrote:

> That doesn't work for me, I build my own vim. I have vim-gtk installed, not vim-gnome anyway.

Och, I was compiling with gnome support, using a script from Tony I'd got years ago that I've not looked at closely since then. Without all that gnomish bloat, compiling is twice as fast. I don't use the gnome session stuff anyway. Stupid warnings are gone, thank you Christian.

Regards, John Little

[pablo jacome]

Hi John,

I also ran into the same problem with the Warning messages being prompted. I read through this and I uninstalled Gnome (as other sites suggested) so that I could only use Gtk. I have Gtk 3.10.8 installed and I'm running on Ubuntu 14.04. I still get the same Warning messages when I open Gvim from the terminal, but I noticed that you said you are Now compiling with Gtk, I'm assuming that is my same problem.

Have you any thoughts or suggestions as to what it could be?

[Jacob Borer]

For the lazy:
sudo apt-get install vim-gtk
sudo update-alternatives --config gvim