Source: dino-im Severity: normal Dear Maintainer,
whenever I try to send OMEMO messages from Dino to a contact using the Conversations client, they can not decrypt the message. Other clients might have the same problem, but I didn't test it yet. The proper OMEMO key shows up under the contact settings in Dino. Verifying the key doesn't help. I haven't found any way to successfully send a decryptable OMEMO message. I actually think that this bug is of 'important' severity, because I consider OMEMO to be a major selling point of Dino. But since it's still usable without OMEMO encryption, I left it at 'normal' to be sure. Sincerely Keno Goertz *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: 10.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-11-amd64 (SMP w/12 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled