After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 598209 - ** GLib-GObject **: Attempt to add property GtkMenuBar::local to class after it was derived
** GLib-GObject **: Attempt to add property GtkMenuBar::local to class after ...
Status: RESOLVED NOTGNOME
Product: glib
Classification: Platform
Component: general
2.22.x
Other Linux
: Normal critical
: ---
Assigned To: gtkdev
gtkdev
: 599550 601855 622823 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2009-10-12 21:13 UTC by Gilles Dartiguelongue
Modified: 2010-06-27 05:59 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Gilles Dartiguelongue 2009-10-12 21:13:47 UTC
Since I updated to glib-2.22, all gtkmm based apps started crashing in the same weird way. Here is a gnote crash, but it is also 100% reproducible with gparted or gnome-system-monitor. I also found the following references via google which sound quite similar:
 * "python-wnck: Abort on "Attempt to add property GtkMenuBar::local" http://bugs.debian.org/550502
 * "[Bug 448375] [NEW] me-tv crashes on launch" http://www.mail-archive.com/ubuntu-bugs@lists.ubuntu.com/msg1755291.html

I've updated to gtk+-2.18 and all 2.18 mm-bindings after seeing this problem but to no avail.


Distribution: Gentoo Base System release 2.0.1
Gnome Release: 2.26.3 2009-09-18 (Gentoo)
BugBuddy Version: 2.28.0

System: Linux 2.6.30-gentoo-r6 #1 SMP Sun Sep 6 13:03:09 CEST 2009 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10603901
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome
GTK+ Modules: canberra-gtk-module, globalmenu-gnome, gnomebreakpad

Memory status: size: 316874752 vsize: 316874752 resident: 21622784 share: 16613376 rss: 21622784 rss_rlim: 18446744073709551615
CPU usage: start_time: 1255388652 rtime: 16 utime: 13 stime: 3 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/gnote'

[?1034h[Thread debugging using libthread_db enabled]
[New Thread 0x7f524abd7770 (LWP 27916)]
0x00007f524747aa15 in __libc_waitpid (pid=27919, stat_loc=0x7ffffcd89560, options=0)
    at ../sysdeps/unix/sysv/linux/waitpid.c:32
	in ../sysdeps/unix/sysv/linux/waitpid.c
Current language:  auto; currently c

Thread 1 (Thread 0x7f524abd7770 (LWP 27916))

  • #0 __libc_waitpid
    at ../sysdeps/unix/sysv/linux/waitpid.c line 32
  • #1 IA__g_spawn_sync
    at gspawn.c line 386
  • #2 IA__g_spawn_command_line_sync
    at gspawn.c line 700
  • #3 bugbuddy_segv_handle
    at gnome-breakpad.cc line 369
  • #4 <signal handler called>
  • #5 raise
    at ../nptl/sysdeps/unix/sysv/linux/raise.c line 64
  • #6 abort
    at abort.c line 88
  • #7 IA__g_logv
    at gmessages.c line 549
  • #8 IA__g_log
    at gmessages.c line 569
  • #9 IA__g_object_class_install_property
    at gobject.c line 428
  • #10 dyn_patch_menu_bar_patcher
    at dyn-patch-menubar.c line 130
  • #11 dyn_patch_type_r
    at dyn-patch-vfunc.c line 34
  • #12 dyn_patch_init
    at dyn-patch-main.c line 44
  • #13 _global_menu_module_deferred_init_gsource_func
    at module-main.c line 120
  • #14 IA__g_main_context_dispatch
    at gmain.c line 1960
  • #15 g_main_context_iterate
    at gmain.c line 2591
  • #16 IA__g_main_loop_run
    at gmain.c line 2799
  • #17 IA__gtk_main
    at gtkmain.c line 1216
  • #18 gnote::Gnote::start_tray_icon
    at gnote.cpp line 202
  • #19 gnote::Gnote::main
    at gnote.cpp line 147
  • #20 main
    at main.cpp line 39

Comment 1 Alexander Larsson 2009-10-13 18:10:34 UTC
Looks like the global menu gtk+ module is doing some weird hack.
Comment 2 Gilles Dartiguelongue 2009-10-13 21:56:04 UTC
I'd like to believe so but it also crashes when I remove the applet from the panels. Unless there's some magic way it survives in the running session (I didn't re-login).
Comment 3 Colin Walters 2009-10-13 21:58:56 UTC
(In reply to comment #2)
> I'd like to believe so but it also crashes when I remove the applet from the
> panels. Unless there's some magic way it survives in the running session (I
> didn't re-login).

I believe it sets up a GTK_MODULES environment variable, so yes, it could continue to affect applications until you log out and log back in.
Comment 4 Gilles Dartiguelongue 2009-10-17 16:16:22 UTC
So the module indeed is still loaded after removing the applet because the gnome-settings-daemon for gtk modules autoloading isn't changed. Changing this setting made the problem go away as well as updating to a svn build of globalmenu applet after reading upstream issue [1]. Sorry for wasting your time.

[1] http://code.google.com/p/gnome2-globalmenu/issues/detail?id=507
Comment 5 Christian Persch 2009-10-25 17:38:31 UTC
*** Bug 599550 has been marked as a duplicate of this bug. ***
Comment 6 Fabio Durán Verdugo 2009-11-14 01:23:25 UTC
*** Bug 601855 has been marked as a duplicate of this bug. ***
Comment 7 Akhil Laddha 2010-06-27 05:59:36 UTC
*** Bug 622823 has been marked as a duplicate of this bug. ***