We get this with some versions of PyGTK/Python (seen on SLES12): /usr/lib64/python2.7/site-packages/gobject/__init__.py:115: Warning: Attempt to add property thinlinc+tlgtk+wizard+WizardPage::page-forwardable after class was initialised type_register(cls, namespace.get('__gtype_name__')) /usr/lib64/python2.7/site-packages/gobject/__init__.py:115: Warning: Attempt to add property thinlinc+tlgtk+wizard+WizardPage::page-busy after class was initialised type_register(cls, namespace.get('__gtype_name__')) /usr/lib64/python2.7/site-packages/gobject/__init__.py:115: Warning: Attempt to add property thinlinc+tlgtk+wizard+WizardPage::page-backable after class was initialised type_register(cls, namespace.get('__gtype_name__')) Should probably have a look at it.
Happens with both tl-setup and tl-run-rdesktop on SLES12. https://bugzilla.gnome.org/show_bug.cgi?id=698614 is interesting. Apparently, the patch which causes the warning has been reverted, even though this usage is still not recommended. Don't understand how to fix though.
Created attachment 659 [details] Warnings in sudo error dialog on CentOS7 These error messages also appear on CentOS 7, where they can leak into the sudo error dialog.
I was unable to reproduce this on a fresh install of SLES12 SP5 (neither `tlinstaller` nor `tl-setup` produces such warnings). I attempted to reproduce it using both 4.12.1 and Jenkins server-bundle #2063 (that uses PyGObject/GTK+ 3.20.10 instead of PyGTK/GTK+ 2.28.6). From what I can tell we do not install any properties before init as described in GNOME bug #698614 mentioned in comment 1. On top of this everything seem to work as intended. Marking as CLOSED/WORKSFORME.