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 638369 - Silent (random?) parsing error
Silent (random?) parsing error
Status: RESOLVED OBSOLETE
Product: glade
Classification: Applications
Component: general
3.6.x
Other Linux
: Normal normal
: ---
Assigned To: Glade 3 Maintainers
Glade 3 Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-12-30 19:52 UTC by Lars Kruse
Modified: 2018-03-26 15:16 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
open this file via "glade broken.xml" and check the (erroneously empty) "OpenGLSettingsFrame" (474.40 KB, text/xml)
2010-12-30 19:52 UTC, Lars Kruse
Details
properly working glade data file (474.49 KB, application/xml)
2010-12-30 19:53 UTC, Lars Kruse
Details

Description Lars Kruse 2010-12-30 19:52:42 UTC
Created attachment 177277 [details]
open this file via "glade broken.xml" and check the (erroneously empty) "OpenGLSettingsFrame"

Hi,

I am creating a PyGTK application GUI with glade.
It worked very well until I recently added a GtkFileChooserButton. This caused - on subsequent file loading via glade - the silent removal of a VBox from a different part of the GUI.

I am using glade 3.6.7-1+b1 (debian package for i386).

How to reproduce:
1) run "glade broken.xml"
2) check the GtkFrame "OpenGLSettingsFrame" - it is empty (but it is supposed to contain a VBox with some checkboxes)
3) close glade and run "glade working.xml" - the frame mentioned above contains the expected checkboxes

the only difference between working.xml and broken.xml is the type of a single object: GtkFileChooserButton (broken) and GtkToolButton (working).

Sadly I failed to find a smaller xml file exposing this behaviour.

Additionally I noticed, that his problem is _not_ exposed, if start glade without any arguments and load "broken.xml" via the Open File menu item. Thus this feels like there is some kind of missing memory inisitalization. Or what do you think?

Hopefully you will be able to track down this bug. Thanks for your time!

cheers,
Lars
Comment 1 Lars Kruse 2010-12-30 19:53:37 UTC
Created attachment 177278 [details]
properly working glade data file
Comment 2 GNOME Infrastructure Team 2018-03-26 15:16:42 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/glade/issues/74.