| Summary: | net-im/gajim-0.16.5-r1 with app-crypt/gnupg-2.1.15 - runtime error: gpg: Unknown status message: u'KEY_CONSIDERED' | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Vladimir <v_2e> |
| Component: | Current packages | Assignee: | Amadeusz Żołnowski (RETIRED) <aidecoe> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | https://trac.gajim.org/ticket/8355 | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | gajim-0.16.6.ebuild | ||
Created attachment 449174 [details]
gajim-0.16.6.ebuild
Looks like this bug is fixed in the new version 0.16.6. I attach the ebuild I used for installing (simply renamed the old ebuild and commented out all the patches; I am not sure if it is correct though).
Thanks, Vladimir! I have bump to 0.16.6. Could you confirm it resolves the issue, please? I have just emerged gajim-0.16.6 from the Portage tree, and everything works well so far (including the PGP-encrypted messages). Thanks! Thanks for testing! 0.16.6 solved the problem for me too. Probably <gajim-0.16.6 should declare <gnupg-2.1.13 dependency, see https://lists.gnupg.org/pipermail/gnupg-announce/2016q2/000390.html Note, 0.16.6 is still ~x86, so users loose their messages after update & login. |
After a recent upgrade from gnupg-2.1.11-r1 to gnupg-2.1.15 Gajim gives this error message after start: Exception in thread Thread-12: Traceback (most recent call last): File "/usr/lib64/python2.7/threading.py", line 801, in __bootstrap_inner self.run() File "/usr/lib64/python2.7/threading.py", line 754, in run self.__target(*self.__args, **self.__kwargs) File "/usr/lib64/python2.7/site-packages/gajim/common/gnupg.py", line 772, in _read_response result.handle_status(keyword, value) File "/usr/lib64/python2.7/site-packages/gajim/common/gnupg.py", line 628, in handle_status raise ValueError("Unknown status message: %r" % key) ValueError: Unknown status message: u'KEY_CONSIDERED' --------------------- This bug has already been reported to upstream and has a status "FIXED" there. However, in Gentoo it still does not work.