When I try to run brss-engine, I get the following error, after it outputs "Getting all categories":
Traceback (most recent call last):
File "/usr/bin/brss-engine", line 3, in <module>
main()
File "/usr/lib/python2.7/site-packages/brss/engine.py", line 1210, in main
engine = Engine()
File "/usr/lib/python2.7/site-packages/brss/engine.py", line 574, in __init__
self.__set_polling(self.settings)
File "/usr/lib/python2.7/site-packages/brss/engine.py", line 597, in __set_polling
None)
TypeError: second argument not callable
In the code, this is
self.timeout_id = GLib.timeout_add_seconds(
0,
interval*60,
self.__timed_update,
None)
I removed the first argument and the engine starts fine.
I'm running 0.18.5 on a fully up-to-date Arch Linux system.
(I'm the reporter...sorry, I forgot to log in before posting the report)
Hi and thanks for the report.
Unfortunately, I wasn't able to reproduce this error.
Could you please provide me with the versions of glib, python2-gobject that you have installed?
I'm suspecting python-gobject's GLib syntax (I'm noting that the dependencies listed in my README have been renamed, so something may have changed)
Hi, here are the versions I have installed:
python2-gobject2: 2.28.6-4
pygobject2-devel 2.28.6-4
python2-gobject: 3.0.1-1
pygobject-devel 3.0.1-1
glib2: 2.30.0-1
glibc: 2.14-6
I'm wondering if it's using the wrong python-gobject version (2 vs 3). Looking at the PKGBUILD and the code, I can't see why it would be, but it's a thought.
I'm running with
gobject-introspection 0.10.8-1
python2-gobject2 2.28.6-1
glib2 2.28.8-1
The trace indicates that python2.7 is the one being run.
I don't use python3 (ln -s /usr/bin/python2.7 /usr/bin/python), because few of the apps I use have been ported.
I'm not aware of any API change between gobject 2.28.6-1 and 2.28.6-4.
Since GI's documentation in mostly available for C and Vala, sometimes, guessing the syntax pygi wanted was a bit dicey.
I'll look into updating at least to the versions of python-gobject and glib you have to see if I can reproduce the issue.
Just updated.
confirmed
Fixed in 0.8.16
Works for me, thanks! (both bugs that I filed)
Looks great, I can't wait to use it!