It's because of changes in gnupg-2.1. It is already fixed upstream. Please backport the fix. Reproducible: Always
Full traceback: Exception in thread Thread-622: Traceback (most recent call last): File "/usr/lib64/python2.7/threading.py", line 810, in __bootstrap_inner self.run() File "/usr/lib64/python2.7/threading.py", line 763, in run self.__target(*self.__args, **self.__kwargs) File "/usr/lib64/python2.7/site-packages/gajim/common/gnupg.py", line 768, in _read_response result.handle_status(keyword, value) File "/usr/lib64/python2.7/site-packages/gajim/common/gnupg.py", line 292, in handle_status raise ValueError("Unknown status message: %r" % key) ValueError: Unknown status message: u'NEWSIG' See URL for ticket submitted upstream.
+*gajim-0.16.1-r1 (18 May 2015) + + 18 May 2015; Justin Lecher <jlec@gentoo.org> + +files/gajim-0.16.1-gnupg-2.1-backport.patch, +gajim-0.16.1-r1.ebuild, + -gajim-0.15.4.ebuild: + Backport fix for gnupg 2.1, bug #549742; Drop old +
The patch is empty :) https://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/net-im/gajim/files/gajim-0.16.1-gnupg-2.1-backport.patch?view=markup
+*gajim-0.16.1-r2 (20 May 2015) + + 20 May 2015; Justin Lecher <jlec@gentoo.org> +gajim-0.16.1-r2.ebuild, + -gajim-0.16.1-r1.ebuild, files/gajim-0.16.1-gnupg-2.1-backport.patch: + Fix patch, bug #549742 +