GNOME Bugzilla – Bug 535001
Anjuta stales at opening a project with a glade file
Last modified: 2009-06-30 14:47:43 UTC
Please describe the problem: Anjuta tries to open an previous session with an open glade file it stales at opening with the following output in console: http://paste.debian.net/4315/ Steps to reproduce: 1. crete a project with a glade file 2. do something with the glade file 3. save the project and use the save session option in preferences 4. exit anjuta 5. restart anjuta Actual results: anjuta stales loading the project Expected results: anjuta loading the project ... Does this happen every time? yes Other information:
This bug is fixed in bug 531585. Also bug 510024 is fixed in bug 532625.
*** Bug 547653 has been marked as a duplicate of this bug. ***
i gave anjuta v2.4.2 a try and built it, but this bug still remains the same. My env is opensuse 11.0, gnome 2.22.1, kde41.
(In reply to comment #3) > i gave anjuta v2.4.2 a try and built it, but this bug still remains the same. > My env is opensuse 11.0, gnome 2.22.1, kde41. Try upgrading to a newer version of glade-3 (or at least gladeui library).
seems i was to keen. After making svn glade3 and anjuta (make uninstall, make, make install) my situation is bader now :-(, because the bug is not gone, but new effects arise: only the glade pane "widgets" is still dockable, all the others like "project" appear as standalone windows now, that's not usable. Got another idea for me or should i reverse to actual glade 3.4.3-24.1 and wait?
(In reply to comment #5) > After making svn glade3 and anjuta (make uninstall, make, make install) my > situation is bader now :-(, because the bug is not gone, but new effects arise: > > only the glade pane "widgets" is still dockable, all the others like "project" > appear as standalone windows now, that's not usable. > > Got another idea for me or should i reverse to actual glade 3.4.3-24.1 and > wait? Perhaps you should reverse to an older anjuta version, but keep the new version of glade. I tried last versions of glade3 and anjuta from svn and they seem to work almost well. What's you CPU load while anjuta stales? Is there a record about bug 531585 in ChangeLog of your glade3 sources? Do those standalone windows have a special dockable header?
Another day, another luck ;-). Starting anjuta today still shows the glade bug, but the panes are ok again. Can't explain it, maybe my make of the actual gimp yesterday (after glade3, anjuta) did something good, because i had to install a few things like the gnome-utils. But back to your questions: - if no other processes order bigger CPU time, then anjuta takes it until 90%. - bug 531585 is part of the changelog in glade3 - though no more of importance: the standalone windows had the button to embed in the most left vertical pane and also did so, but activating them in this pane does not embed them in the normal left pane, but as single windows instead I started anjuta from console in order to catch some messages. Here the result for you, Pavel: ** Message: Spawning script GladeUI-Message: 1 missing displayable value for GnomeDateEdit::dateedit-flags (libgnomedb-glade3:27271): GladeUI-WARNING **: No icon named 'widget-gnomedb-gnome-db-basic-form' was found for object class 'GnomeDbBasicForm'. (libgnomedb-glade3:27271): GladeUI-WARNING **: No icon named 'widget-gnomedb-gnome-db-canvas-db-relations' was found for object class 'GnomeDbCanvasDbRelations'. (libgnomedb-glade3:27271): GladeUI-WARNING **: No icon named 'widget-gnomedb-gnome-db-combo' was found for object class 'GnomeDbCombo'. (libgnomedb-glade3:27271): GladeUI-WARNING **: No icon named 'widget-gnomedb-gnome-db-connection-properties' was found for object class 'GnomeDbConnectionProperties'. (libgnomedb-glade3:27271): GladeUI-WARNING **: No icon named 'widget-gnomedb-gnome-db-data-import' was found for object class 'GnomeDbDataImport'. (libgnomedb-glade3:27271): GladeUI-WARNING **: No icon named 'widget-gnomedb-gnome-db-data-source-selector' was found for object class 'GnomeDbDataSourceSelector'. (libgnomedb-glade3:27271): GladeUI-WARNING **: No icon named 'widget-gnomedb-gnome-db-dbms-update-viewer' was found for object class 'GnomeDbDbmsUpdateViewer'. (libgnomedb-glade3:27271): GladeUI-WARNING **: No icon named 'widget-gnomedb-gnome-db-dsn-assistant' was found for object class 'GnomeDbDsnAssistant'. (libgnomedb-glade3:27271): GladeUI-WARNING **: No icon named 'widget-gnomedb-gnome-db-dsn-editor' was found for object class 'GnomeDbDsnEditor'. (libgnomedb-glade3:27271): GladeUI-WARNING **: No icon named 'widget-gnomedb-gnome-db-dsn-spec' was found for object class 'GnomeDbDsnSpec'. (libgnomedb-glade3:27271): GladeUI-WARNING **: No icon named 'widget-gnomedb-gnome-db-editor' was found for object class 'GnomeDbEditor'. (libgnomedb-glade3:27271): GladeUI-WARNING **: No icon named 'widget-gnomedb-gnome-db-error-dialog' was found for object class 'GnomeDbErrorDialog'. (libgnomedb-glade3:27271): GladeUI-WARNING **: No icon named 'widget-gnomedb-gnome-db-error' was found for object class 'GnomeDbError'. (libgnomedb-glade3:27271): GladeUI-WARNING **: No icon named 'widget-gnomedb-gnome-db-find-dialog' was found for object class 'GnomeDbFindDialog'. (libgnomedb-glade3:27271): GladeUI-WARNING **: No icon named 'widget-gnomedb-gnome-db-form' was found for object class 'GnomeDbForm'. (libgnomedb-glade3:27271): GladeUI-WARNING **: No icon named 'widget-gnomedb-gnome-db-entry-string' was found for object class 'GnomeDbEntryString'. (libgnomedb-glade3:27271): GladeUI-WARNING **: No icon named 'widget-gnomedb-gnome-db-entry-boolean' was found for object class 'GnomeDbEntryBoolean'. (libgnomedb-glade3:27271): GladeUI-WARNING **: No icon named 'widget-gnomedb-gnome-db-entry-combo' was found for object class 'GnomeDbEntryCombo'. (libgnomedb-glade3:27271): GladeUI-WARNING **: No icon named 'widget-gnomedb-gnome-db-entry-time' was found for object class 'GnomeDbEntryTime'. (libgnomedb-glade3:27271): GladeUI-WARNING **: No icon named 'widget-gnomedb-gnome-db-entry-timestamp' was found for object class 'GnomeDbEntryTimestamp'. (libgnomedb-glade3:27271): GladeUI-WARNING **: No icon named 'widget-gnomedb-gnome-db-entry-date' was found for object class 'GnomeDbEntryDate'. (libgnomedb-glade3:27271): GladeUI-WARNING **: No icon named 'widget-gnomedb-gnome-db-entry-filesel' was found for object class 'GnomeDbEntryFilesel'. (libgnomedb-glade3:27271): GladeUI-WARNING **: No icon named 'widget-gnomedb-gnome-db-entry-text' was found for object class 'GnomeDbEntryText'. (libgnomedb-glade3:27271): GladeUI-WARNING **: No icon named 'widget-gnomedb-gnome-db-entry-password' was found for object class 'GnomeDbEntryPassword'. (libgnomedb-glade3:27271): GladeUI-WARNING **: No icon named 'widget-gnomedb-gnome-db-grid' was found for object class 'GnomeDbGrid'. (libgnomedb-glade3:27271): GladeUI-WARNING **: No icon named 'widget-gnomedb-gnome-db-login-dialog' was found for object class 'GnomeDbLoginDialog'. (libgnomedb-glade3:27271): GladeUI-WARNING **: No icon named 'widget-gnomedb-gnome-db-login' was found for object class 'GnomeDbLogin'. (libgnomedb-glade3:27271): GladeUI-WARNING **: No icon named 'widget-gnomedb-gnome-db-provider-selector' was found for object class 'GnomeDbProviderSelector'. (libgnomedb-glade3:27271): GladeUI-WARNING **: No icon named 'widget-gnomedb-gnome-db-raw-form' was found for object class 'GnomeDbRawForm'. (libgnomedb-glade3:27271): GladeUI-WARNING **: No icon named 'widget-gnomedb-gnome-db-raw-grid' was found for object class 'GnomeDbRawGrid'. (libgnomedb-glade3:27271): GladeUI-WARNING **: No icon named 'widget-gnomedb-gnome-db-report-editor' was found for object class 'GnomeDbReportEditor'. (libgnomedb-glade3:27271): GladeUI-WARNING **: No icon named 'widget-gnomedb-gnome-db-selector' was found for object class 'GnomeDbSelector'. GladeUI-Message: No displayable values for property GnomeDbSelector::mode GladeUI-Message: No displayable values for property GnomeDbSelector::columns (libgnomedb-glade3:27271): GladeUI-WARNING **: No icon named 'widget-gnomedb-gnome-db-sql-console' was found for object class 'GnomeDbSqlConsole'. (libgnomedb-glade3:27271): GLib-GObject-WARNING **: gsignal.c:1669: signal `resource-updated' is invalid for instance `0x80bfa28'
one extra note: rpm tells me, that i still have glade v3.4.3-24.1. Is there anything else to do but ./autogen.sh, make, sudo make install in order to replace the version of glade? Since anjuta was built again after this, there should everything be fine, or not?
Remeber to pass --prefix=/usr to configure/autogen.sh in order to replace your old glade version. Though rpm will never notice that and will still show you the old version.
I have exactly the same problem running on Debian Lenny. Anjuta 2.4.2 Glade 3.4.5 Both applications recently installed via the Debian package process.
Can someone confirm if the patch in bug 558706 fixes this?
Seems like maintainers built the package without a corresponding patch. At least my glade-3 3.4.5-3ubuntu1 has this problem... again. But it was fixed in glade3 svn trunk and gnome-2-22 branch long ago.
*** Bug 562635 has been marked as a duplicate of this bug. ***
*** Bug 562679 has been marked as a duplicate of this bug. ***
This is a problem in Glade3 and was fixed in bug 531585 but somehow the patch is missing from the Glade3 tarball. We will carry the patch in Fedora until it (re-?)appears in the tarball. You may want to follow https://bugzilla.redhat.com/478698 to know when the packages are available.
I assume this issue is OBSOLETE by now. Feel free to revert if this is not the case :)