GNOME Bugzilla – Bug 622823
crash in Deskbar: Trying global menu
Last modified: 2010-06-27 05:59:36 UTC
What were you doing when the application crashed? Trying global menu Distribution: Debian squeeze/sid Gnome Release: 2.30.0 2010-04-26 (Debian) BugBuddy Version: 2.30.0 System: Linux 2.6.32-5-686 #1 SMP Tue Jun 1 04:59:47 UTC 2010 i686 X Vendor: The X.Org Foundation X Vendor Release: 10707000 Selinux: No Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: gnome GTK+ Modules: globalmenu-gnome, gnomebreakpad, canberra-gtk-module Memory status: size: 179752960 vsize: 179752960 resident: 43311104 share: 18276352 rss: 43311104 rss_rlim: 18446744073709551615 CPU usage: start_time: 1277562680 rtime: 327 utime: 274 stime: 53 cutime:9 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/python2.5' [Thread debugging using libthread_db enabled] 0xb775d424 in __kernel_vsyscall ()
+ Trace 222593
Thread 1 (Thread 0xb75b08d0 (LWP 4573))
A debugging session is active. Inferior 1 [process 4573] will be detached. Quit anyway? (y or n) [answered Y; input not from terminal] ---- Critical and fatal warnings logged during execution ---- ** GLib-GObject **: Attempt to add property GtkMenuBar::local to class after it was derived ----------- .xsession-errors (7 sec old) --------------------- Using Mod4, ignoring Mod1. GLib-GObject-ERROR **: Attempt to add property GtkMenuBar::local to class after it was derived aborting... GLib-GObject-ERROR **: Attempt to add property GtkMenuBar::local to class after it was derived aborting... warning: .dynamic section for "/usr/lib/libpango-1.0.so.0" is not at the expected address (wrong library or version mismatch?) warning: .dynamic section for "/usr/lib/libpangoft2-1.0.so.0" is not at the expected address (wrong library or version mismatch?) warning: .dynamic section for "/usr/lib/libpangocairo-1.0.so.0" is not at the expected address (wrong library or version mismatch?) warning: .dynamic section for "/usr/lib/pango/1.6.0/modules/pango-basic-fc.so" is not at the expected address (wrong library or version mismatch?) --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of bug 598209 ***