Picture download failes with "A resource failed to call close."

[eku]

When downloading any attached file from the conversation thread it starts downloading, shows download percentage and finally fails.

Device: Android 9 (Lineage 16.0-20200325-NIGHTLY-bardockpro) Conversation: 2.10.5

logcat:

05-26 17:23:33.374  6051  6051 D conversations: using 16-byte IV for file transmission
05-26 17:23:33.375  6051  6051 D conversations: create temporary OMEMO encrypted file:
+/data/user/0/eu.siacs.conversations/cache/68a07985-9ed2-40b0-b398-6ea9840ef52a(image/jpeg)
05-26 17:23:34.550  6051  6059 W System  : A resource failed to call close.
05-26 17:23:34.867  2875  4224 E AppOps  : Operation not started: uid=10088
+pkg=eu.siacs.conversations op=WAKE_LOCK
05-26 17:23:36.890  2875  4224 W NotificationService: Toast already killed.
+pkg=eu.siacs.conversations callback=android.app.ITransientNotification$Stub$Proxy@b9b6914

If you need any more information or want me to try anything, feel free.

[licaon-kter]

Same for 2.10.6? Any other upload server too?

[eku]

2.10.6 is still no available on F-Droid. As for the server, I can say that it works in the other direction. On the other site runs Conversation Legacy.

[licaon-kter]

Oh wait, the old Conversations is from 2018, things have changed in the mean time, encryption wise.

2.10.6 is still no available on F-Droid.

Not an issue then.

Any reason to stick with the old version? It's obsolete, misses some security fixes let alone Audio/Video calls.

[eku]

Oh wait, the old Conversations is from 2018, things have changed in the mean time, encryption wise.

I use this combination since years and I know it worked very well.

Remember that the download of the file starts and progress is shown. How could that be an encryption problem?

Any reason to stick with the old version?

#2908 My home automation supports only OTR and not OMEMO.

[licaon-kter]

I use this combination since years and I know it worked very well.

Ok, decryption wise stuff has moved along...

Remember that the download of the file starts and progress is shown. How could that be an encryption problem?

This happens for unencrypted files too you mean?

My home automation supports only OTR and not OMEMO.

Some thoughts:

• If you are offline you'll miss the messages, right?
• Why not self host then? No need for encryption.
• The tooling of FHEM can't use a different program to send the message? You'd use a CLI one that has OMEMO then