This bug seems to be somewhat related to bug #549742 The upstream reports to have fixed the bug in 0.16.2, however, as far as I understand, the bugfix was released after Gajim 0.16.2 release, so it needs to be patched additionally. It would be very good to import that fix into net-im/gajim-0.16.2-r1 Thank you!
What about gajim-0.16.3?
(In reply to Justin Lecher from comment #1) > What about gajim-0.16.3? Gajim-0.16.3 seems to work correctly. Thank you!
+ 06 Aug 2015; Justin Lecher <jlec@gentoo.org> -files/0.14-python-version.patch, + -files/0.14.1-testing.patch, -files/0.14.4-unicode.patch, + -files/gajim-0.14.4-debian_patches_unicode.patch, + -files/gajim-0.15-SA48695-2.patch, -files/gajim-0.15-SA48695.patch, + -files/gajim-0.15-plugin.patch, -files/gajim-0.15.2-CVE-2012-5524.patch, + -files/gajim-0.15.3-roster.patch, -files/gajim-0.15.3-starttls.patch, + -files/gajim-0.16.1-gnupg-2.1-backport.patch, + -files/gajim-0.16_beta2-pyopenssl-backport-1.patch, + -files/gajim-0.16_beta2-pyopenssl-backport-2.patch, -gajim-0.16.1-r2.ebuild, + -gajim-0.16.1.ebuild, -gajim-0.16.2.ebuild: + Clean old; obsoletes bug #556596 +