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 607221 - Widget names not set when using GtkBuilder
Widget names not set when using GtkBuilder
Status: RESOLVED DUPLICATE of bug 591085
Product: gtk+
Classification: Platform
Component: Class: GtkBuilder
2.19.x
Other Linux
: Normal normal
: ---
Assigned To: GtkBuilder maintainers
GtkBuilder maintainers
Depends on:
Blocks:
 
 
Reported: 2010-01-17 14:37 UTC by Severin Heiniger
Modified: 2010-01-17 19:07 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
C testcase. Compile using gcc testcase.c -Wall -o testcase `pkg-config --cflags --libs gtk+-2.0` (639 bytes, text/x-csrc)
2010-01-17 14:37 UTC, Severin Heiniger 		Details
UI file (788 bytes, application/x-designer)
2010-01-17 14:38 UTC, Severin Heiniger 		Details
Python version of the testcase (245 bytes, text/x-python)
2010-01-17 14:40 UTC, Severin Heiniger 		Details

Description Severin Heiniger 2010-01-17 14:37:54 UTC 
Created attachment 151594 [details]
C testcase. Compile using gcc testcase.c -Wall -o testcase `pkg-config --cflags --libs gtk+-2.0`

When loading a XML UI file using GtkBuilder, the 'name' property of widgets isn't set. On the other hand, the 'name' property of 'GtkAction' objects is properly set.

A test case written in both Python and C is attached. The problem can only be encountered on an up-to-date Ubuntu Lucid machine (libgtk2.0-0 version 2.19.3-1). Everything works fine using Ubuntu Karmic.

This bug has been reported in Launchpad.net.
Comment 1 Severin Heiniger 2010-01-17 14:38:51 UTC 
Created attachment 151595 [details]
UI file
Comment 2 Severin Heiniger 2010-01-17 14:40:20 UTC 
Created attachment 151596 [details]
Python version of the testcase
Comment 3 Javier Jardón (IRC: jjardon) 2010-01-17 19:07:19 UTC 
Seems to be a duplicate of bug #591085

*** This bug has been marked as a duplicate of bug 591085 ***