TypeError exception when picty starts

[bbinet]

bruno@neo: ~/dev/3rd/picty (master) $ ./bin/picty
running picty with module path /home/bruno/dev/3rd/picty/modules
Traceback (most recent call last):
  File "./bin/picty", line 67, in <module>
    sett.set_property("gtk-button-images",True)
TypeError: object of type `GtkSettings' does not have property `gtk-button-images'

I'm running debian wheezy. I've tried both to install from debian .deb package, and from source, but I get the same error anyway. Maybe some unsupported versions of dependencies? Here are the installed versions of the dependencies:

for i in python python-gtk2 python-gnome2 python-pyexiv2 python-pyinotify; do dpkg-query --show $i;done
python  2.7.3-4+deb7u1
python-gtk2 2.24.0-3+b1
python-gnome2   2.28.1+dfsg-1
python-pyexiv2  0.3.2-5
python-pyinotify    0.9.3-1.1

[spillz]

Thanks for reporting. I will fix it later today. Just an issue with newer Gtk versions.

If you are eager to test, just comment the offending line out -- line 67 of bin/picty. (You may need to comment another line or two, but I don't think so.) On Feb 18, 2014 4:32 PM, "Bruno Binet" notifications@github.com wrote:

bruno@neo: ~/dev/3rd/picty (master) $ ./bin/picty running picty with module path /home/bruno/dev/3rd/picty/modules Traceback (most recent call last): File "./bin/picty", line 67, in sett.set_property("gtk-button-images",True) TypeError: object of type GtkSettings' does not have propertygtk-button-images'

I'm running debian wheezy. I've tried both to install from debian .deb package, and from source, but I get the same error anyway. Maybe some unsupported versions of dependencies? Here are the installed versions of the dependencies:

for i in python python-gtk2 python-gnome2 python-pyexiv2 python-pyinotify; do dpkg-query --show $i;done python 2.7.3-4+deb7u1 python-gtk2 2.24.0-3+b1 python-gnome2 2.28.1+dfsg-1 python-pyexiv2 0.3.2-5 python-pyinotify 0.9.3-1.1

Reply to this email directly or view it on GitHubhttps://github.com/spillz/picty/issues/3 .

[bbinet]

Commenting the offending line out actually fix this issue, thanks @spillz.

[spillz]

Fixed.