Unless restarting Gajim OMEMO does not work at all on a newly added account while working on the other
Versions
-
OS: Windows 7
-
GTK+ Version: 3.24.1
-
PyGObject Version: 3.30.4
-
GLib Version : 2.58.3
-
python-nbxmpp Version: 0.9.91
-
Gajim Version: 1.1.92
-
OMEMO plugin: 2.6.50
Steps to reproduce the problem
- have a proven Gajim installation with an account where OMEMO works (although not perfectly ;-) )
- add an additional accout
- try to do anything in regards to OMEMO on that newly created account
Actual behavior
- nothing happening when clicking on the shield button to show fingerprints
- nothing happening when trying to send an OMEMO message: absolutely nothing happens on sending apart from the entered text disappearing
- in the OMEMO plugin configuration there is no fingerprint for shown for that account
- in the OMEMO plugin using the pulldown list to switch to the other account and then switching back to the newly added account first results in this error...
Traceback
Traceback (most recent call last):
File "C:\Programme (standalone)\Gajim\UserData\Plugins\omemo\gtk\config.py", line 86, in account_combobox_changed_cb
self.update_context_list()
File "C:\Programme (standalone)\Gajim\UserData\Plugins\omemo\gtk\config.py", line 154, in update_context_list
fpr = get_fingerprint(identity_key, formatted=True)
File "C:\Programme (standalone)\Gajim\UserData\Plugins\omemo\backend\util.py", line 38, in get_fingerprint
fingerprint = binascii.hexlify(public_key).decode()[2:]
TypeError: a bytes-like object is required, not 'MagicMock'
--------------------------------------------------------------
...and then displays the wrong combination of account and fingerprint (shows fingerprint of old account while new account is shown in account pulldown menu!
Workaround: close and restart Gajim. OMEMO will then work work.