Open kohms opened 1 year ago
Hm, I saw the same behavior inside a ubuntu:20.04 docker container, maybe openssl introduced changes?
root@7a4869a7a72f:/work# signal-backup-decode backups/signal-2023-07-27-19-10-12.backup -p xxx -o backups/signal-2023-07-27-19-10-12 -f
19:55:40 [INFO] Output path: backups/signal-2023-07-27-19-10-12
19:55:40 [INFO] Input file: backups/signal-2023-07-27-19-10-12.backup
thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: TryFromIntError(())', /root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/openssl-0.10.55/src/cipher_ctx.rs:565:50
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Read vs. written frames: [00:00:40] [--------------------------------------------------] 0/1
Hi, I used to run signal-backup-decode a while ago (I think it was on Ubuntu 20.04). It worked perfectly fine, thanks for the great and simple tooling. Unfortunately, I upgraded to a new install of Ubuntu 22.04 and tried to decrypt a backup from today to archive my messages and offload them from my Android Phone. The decryption freezes, because a thread panics, is there something I can do to make it work on Ubuntu 22.04 again?
Details:
OS:
Signal version: 6.26.4
Steps to reproduce:
The process seem not to progress afterwards any more, it does not terminate, but it only consumes 35,5 MB memory and 0 CPU.
Is maybe some shared OS lib to recent in Ubuntu 22.04 and broke compatibility with signal-backup-decode?
Thanks for any hints