Source: backintime Version: 1.5.4-1 Severity: important Hello,
upstream maintainer here. A user found a bug that IMHO should be fixed before the upcoming 13/Trixie release. It affects all users creating a new backup profile using SSH with a passphrase on their key-pair. After clicking on OK in the "Manage profiles" dialog an error message is shown: "Could not unlock ssh private key. Wrong password or password not available for cron.". And on a terminal the message is "ERROR: Failed to unlock SSH private key <key-file-path>". The reporting user provided a solution. After investigating the issue and the solution, I'll report back. Regards, Christian Buhtz -- System Information: Debian Release: 12.11 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-37-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
