GNOME Bugzilla – Bug 118705
libbonoboui-2.2.3 breaks Evolution-1.4.3 preferences dialog (and more?)
Last modified: 2004-12-22 21:47:04 UTC
After installing libbonoboui-2.2.3 from source Evolution crashes when trying to access it's preferences through Tools->Settings. In console evolution gives the following error when trying to access the preferences: ---------------------------------------------------------- [preacher@corinthian ~]$ evolution Bonobo-ERROR **: file bonobo-socket.c: line 227 (bonobo_socket_hierarchy_changed): assertion failed: (priv->toplevel == previous_toplevel) aborting... (gnome_segv:28763): Gtk-WARNING **: gtkmessagedialog.c:270: invalid property id 1 for "message-type" of type `GParamEnum' in `GtkMessageDialog' ---------------------------------------------------------- After downgrading back to libbonoboui-2.2.2 it works again. My version of libbonobo is 2.2.3. (Sorry for bad formatting from my side or/and lack of information, this is my first bug report, ever.)
Dudie - this is rather serious looking ...
Let me take a look; I'm fetching an 1.4.3 package right now. It works fine for me with HEAD, which shouldn't be that different from 1.4.3, anyways...
Just a follow-up. I just built Evo 1.4.4 with all the new subcomponents (gtkhtml, gal, etc.) and the crash is still there: Bonobo-ERROR **: file bonobo-socket.c: line 227 (bonobo_socket_hierarchy_changed): assertion failed: (priv->toplevel == previous_toplevel) aborting... Interesting to note that this new libbonoboui feature made it into a stable release before it made it into a 2.3.x release....
Got same crash (abort trap) in Gnumeric-1.1.19 after clicking on the toolbar's rightarrow ( see http://raven.oook.cz/gnumeric.png ). Message is same: Bonobo-ERROR **: file bonobo-socket.c: line 227 (bonobo_socket_hierarchy_changed): assertion failed: (priv->toplevel == previous_toplevel) aborting... libbonobo version is 2.2.3
OK, I can reproduce this. Working on it.
Fixed in both HEAD and the gnome-2-2 branches. I'll put out a 2.2.4 release ASAP.
*** Bug 118564 has been marked as a duplicate of this bug. ***