[Pkg-xmpp-devel] Bug#1024899: profanity: some Profanity → Beagle OMEMO msgs give “This message cannot be decrypted for any recipient.”

[debbug.profanity at sideload.33mail.com]

Package: profanity
Version: 0.13.1-1~bpo11+1
Severity: important
X-Debbugs-Cc: debbug.profanity at sideload.33mail.com

Configuration:

  Bob has 2 clients   → linux:Profanity & Android:Snikket
  Alice has 2 clients → macos:Beagle & iOS:Snikket
  server              → snikket.org

Bob’s Profanity and Snikket installations both trust both of Alice’s
fingerprints.

Alice           → Bob works
Bob (Snikket)   → Alice works
Bob (Profanity) → Alice broken

When Bob executes:

  /msg alice at foo.snikket.org Some text here.

Profanity gives:

===8<------------------------------
  01:23:45 ! This message cannot be decrypted for any recipient.                                                                              
             You should trust your recipients' device fingerprint(s) using "/omemo trust FINGERPRINT".                                        
             It could also be that the key bundle of the recipient(s) have not been received. In this case, you could try "omemo end", "omemo 
             start", and send the message again.                                                                                              
===8<------------------------------

The error msg suggestion to do “omemo end…start” worked, but it should
not have been necessary because the chat session was working
previously. That is, Bob successfully sent msgs already, then this
error came out of the blue.  A snip of the OMEMO session went like
this:

===8<------------------------------
  Alice (text) → Bob [success]
  Bob (text from Profanity) → Alice [success]
  Alice (images) → Bob [success]
  Bob (text from Profanity) → Alice [success]
  Bob (text from Profanity) → Alice [success]
  Alice (text) → Bob [success]
  Bob (text from Profanity) → Alice [failure!]
  Bob (text from Snikket) → Alice [success]
  (Bob) /omemo end
  (Bob) /omemo start
  Bob (text from Profanity) → Alice [apparent success from sending side but not yet confirmed by Alice]
===8<------------------------------

Bob must have had Alice’s keys all along since the past msgs were sent
without issue. It looks as if Profanity lost Alice’s keys
spontaneously. Bob should not have been interrupted with the missing
keys error which then forced Bob to stop & start OMEMO all of the
sudden.

-- System Information:
Debian Release: 11.5
  APT prefers stable-updates
  APT policy: (990, 'stable-updates'), (990, 'stable-security'), (990, 'testing'), (990, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-19-amd64 (SMP w/2 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages profanity depends on:
ii  libc6                      2.31-13+deb11u5
ii  libcurl3-gnutls            7.74.0-1.3+deb11u3
ii  libgcrypt20                1.8.7-6
ii  libgdk-pixbuf-2.0-0        2.42.2+dfsg-1+deb11u1
ii  libglib2.0-0               2.66.8-1
ii  libgpgme11                 1.14.0-1+b2
ii  libgtk-3-0                 3.24.24-4+deb11u2
ii  libncursesw6               6.2+20201114-2
ii  libnotify4                 0.7.9-3
ii  libotr5                    4.1.1-4
ii  libpython3.9               3.9.2-1
ii  libreadline8               8.1-1
ii  libsignal-protocol-c2.3.2  2.3.3-1
ii  libsqlite3-0               3.34.1-3
ii  libstrophe0                0.12.2-1~bpo11+1
ii  libtinfo6                  6.2+20201114-2

profanity recommends no packages.

profanity suggests no packages.

-- no debconf information