Indeed gbirthday is unmaintained (and is Python2/PyGTK).
When porting it to Qt I renamed it as qbirthday so that anyone willing a GTK version can pick gbirthday where we left it. I doubt anyone will, so switching to qbirthday sounds more reasonable on the long run. Besides, it should be easier to package. It has a setup.py and all. I contacted gbirthday's Debian packager but got no answer. Anyone willing to give it a go, please do so.
I have no idea what triggers this glib.GError and frankly, I won't take the time to investigate. Of course, if a patch is proposed, I can release a new version with the fix.
Meanwhile, @tellapu, you could try qbirthday (you're not the same person as Filbuntu, are you?) and see if you have that same display issue.
qbirthday maintainer here.
Indeed gbirthday is unmaintained (and is Python2/PyGTK).
When porting it to Qt I renamed it as qbirthday so that anyone willing a GTK version can pick gbirthday where we left it. I doubt anyone will, so switching to qbirthday sounds more reasonable on the long run. Besides, it should be easier to package. It has a setup.py and all. I contacted gbirthday's Debian packager but got no answer. Anyone willing to give it a go, please do so.
I have no idea what triggers this glib.GError and frankly, I won't take the time to investigate. Of course, if a patch is proposed, I can release a new version with the fix.
Meanwhile, @tellapu, you could try qbirthday (you're not the same person as Filbuntu, are you?) and see if you have that same display issue.