lottanzb team mailing list archive

Thread
Date

[Bug 507739] Re: Widget names not set when using gtk.Builder

To: lottanzb@xxxxxxxxxxxxxxxxxxx
From: Severin Heiniger <severinheiniger@xxxxxxxxx>
Date: Fri, 15 Jan 2010 20:11:41 -0000
Reply-to: Bug 507739 <507739@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

** Summary changed:

- lottanzb crashed with AttributeError in _autoconnect_by_method_name()
+ Widget names not set when using gtk.Builder

-- 
Widget names not set when using gtk.Builder
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: New
Status in “lottanzb” package in Ubuntu: New

Bug description:
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:

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.

A test case 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.