I've managed to fix an issue with OTR that occurs after a system - that
has Jitsi running - restores from standby/suspend.
You may still get a second OTR session after restoring from stand-by.
This is due to a new OTR session being initiated.
For devs and interested, some details:
ContactResource did not have equality defined. After re-establishing the
network connection (or at least, I am assuming this is the root reason)
new instances for ContactResource are used. Since ContactResource had
equality defined by instance address only, Some Jitsi GUI operations
broke down. Specifically, OTR's session switcher menu did not correctly
switch sessions as it never found the active contact (resource).
I have now defined equality based on resourceName.