lottanzb team mailing list archive
-
lottanzb team
-
Mailing list archive
-
Message #00171
[Bug 507739] Re: Widget names not set when using gtk.Builder
C test-case. Compile it using
gcc testcase.c -Wall -o testcase `pkg-config --cflags --libs gtk+-2.0`
and make sure that 'testcase.ui' is in the same directory as 'testcase'
when executing it.
** Attachment added: "testcase.c"
http://launchpadlibrarian.net/38001124/testcase.c
** Also affects: gtk+2.0 (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
LottaNZB cannot be launched on an up-to-date Lucid machine because of a
- bug in PyGTK (or something more low-level). I tracked down the problem:
+ bug in GtkBuilder. I tracked down the problem:
- When loading a XML UI file using gtk.Builder, the 'name' property of
- widgets isn't set. Because of this, get_name() just returns a string
- containing the widget type (like GtkWindow). On the other hand, the
- 'name' property of 'gtk.Action' objects is properly set.
+ When loading a XML UI file using GtkBuilder, the 'name' property of
+ widgets isn't set. On the other hand, the 'name' property of
+ 'gtk.Action' objects is properly set.
- A test case is attached. Compare the output on a Karmic and a Lucid
- machine.
+ A test case written in both Python and C is attached. Compare the output
+ on a Karmic and a Lucid machine.
I'm pretty sure that LottaNZB worked about a week ago, when I initially
installed Lucid. This means that the bug could have been introduced in a
- recent update of the pygtk package.
+ recent update.
** Summary changed:
- Widget names not set when using gtk.Builder
+ Widget names not set when using GtkBuilder
** Description changed:
LottaNZB cannot be launched on an up-to-date Lucid machine because of a
bug in GtkBuilder. I tracked down the problem:
When loading a XML UI file using GtkBuilder, the 'name' property of
- widgets isn't set. On the other hand, the 'name' property of
- 'gtk.Action' objects is properly set.
+ 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. Compare the output
on a Karmic and a Lucid machine.
I'm pretty sure that LottaNZB worked about a week ago, when I initially
installed Lucid. This means that the bug could have been introduced in a
recent update.
** Changed in: lottanzb
Status: New => Invalid
** Changed in: lottanzb (Ubuntu)
Status: New => Invalid
--
Widget names not set when using GtkBuilder
https://bugs.launchpad.net/bugs/507739
You received this bug notification because you are a member of LottaNZB
Development Team, which is subscribed to LottaNZB.
Status in LottaNZB • Automated Usenet Client: Invalid
Status in “gtk+2.0” package in Ubuntu: New
Status in “lottanzb” package in Ubuntu: Invalid
Status in “pygtk” package in Ubuntu: New
Bug description:
LottaNZB cannot be launched on an up-to-date Lucid machine because of a bug in GtkBuilder. I tracked down the problem:
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. Compare the output on a Karmic and a Lucid machine.
I'm pretty sure that LottaNZB worked about a week ago, when I initially installed Lucid. This means that the bug could have been introduced in a recent update.