GNU bug report logs - #10230
24.0.92; Warnings on emacs startup

Previous Next

Package: emacs;

Reported by: thierry <thierry.volpiatto <at> gmail.com>

Date: Tue, 6 Dec 2011 09:29:02 UTC

Severity: normal

Found in version 24.0.92

Done: Jan Djärv <jan.h.d <at> swipnet.se>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: "Jan D." <jan.h.d <at> swipnet.se>
To: thierry <thierry.volpiatto <at> gmail.com>
Cc: 10230 <at> debbugs.gnu.org
Subject: bug#10230: 24.0.92; Warnings on emacs startup
Date: Tue, 06 Dec 2011 12:26:25 +0100
thierry skrev 2011-12-06 10:28:
> Hi all,
> I have tried building emacs like this:
>
> "./configure --with-x-toolkit=lucid --without-rsvg --without-gconf --with-wide-int"
>
> Emacs works fine except I have these warning messages on startup when
> starting from command line:
>
> --8<---------------cut here---------------start------------->8---
> (process:22974): GLib-GObject-CRITICAL **: /build/buildd/glib2.0-2.30.0/./gobject/gtype.c:2708: You forgot to call g_type_init()
>
> (process:22974): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
>
> (process:22974): GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed
> --8<---------------cut here---------------end--------------->8---
>

What libraries are linked to your Emacs?  Can you send the output of ldd?
Also if you can start the debugger and put breakpoints for g_log and 
g_logv and then post the backtrace when the breakpoint is hit, that 
would  be nice.  We can then see exactly what library is causing these 
messages.  Previously Emacs tried to call g_type_init as needed but as 
new libraryes that use glib was added (like dbus for example), this 
wasn't kept up to date.

	Jan D.






This bug report was last modified 13 years and 167 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.