Package: backintime-qt
Version: 1.2.1-3
Severity: normal
Dear Maintainer,
In ssh mode backintime fails to read previously stored credentials since
python3-keyring 23.2.0-1 has been rolled out. Instead it always calls
backintime-askpass to query the password from the GUI.
Logs say it cannot work with the back end python3-keyring uses:
keyring.backends.chainer
$ backintime-qt --debug
DEBUG: [common/backintime.py:583 argParse] Arguments: {'debug': True} |
unknownArgs: []
Back In Time
Version: 1.2.1
Back In Time comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it
under certain conditions; type `backintime --license' for details.
DEBUG: [common/backintime.py:670 getConfig] config file:
/home/sg/.config/backintime/config
DEBUG: [common/backintime.py:671 getConfig] share path:
/home/sg/.local/share/backintime
DEBUG: [common/backintime.py:672 getConfig] profiles: 1=Hauptprofil
DEBUG: [common/pluginmanager.py:90 PluginManager.load] Register plugin path
/usr/share/backintime/plugins
DEBUG: [common/pluginmanager.py:106 PluginManager.load] Add plugin
qt4plugin.py
DEBUG: [common/pluginmanager.py:106 PluginManager.load] Add plugin
notifyplugin.py
Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use
QT_QPA_PLATFORM=wayland to run on Wayland anyway.
DEBUG: [common/tools.py:823 keyringSupported] No appropriate keyring found.
'keyring.backends.chainer' can't be used with BackInTime
[...]
With python3-keyring 22.0.1-1 backintime succeeds to read the ssh password from
the keyring (no password dialog pops up).
However logs now say
[...]
DEBUG: [common/tools.py:823 keyringSupported] No appropriate keyring found.
'keyring.backends.SecretService' can't be used with BackInTime
[...]
Further investigations showed that one can force python3-keyring 23.2.0-1 to
use keyring.backends.SecretService instead of keyring.backends.chainer.
~/.config/python_keyring/keyringrc.cfg:
[backend]
default-keyring=keyring.backends.SecretService.Keyring
Doing so apparently allows backintime to read from the keyring (no password
dialog pops up), but still the logs show
[...]
DEBUG: [common/tools.py:823 keyringSupported] No appropriate keyring found.
'keyring.backends.SecretService' can't be used with BackInTime
[...]
Two Conclusion:
1) Backintime fails to access the keyring when keyring.backends.chainer is in
use.
2) Backintime's test for keyring back ends does not work properly. It does not
recognize a back end as functional it does work with later on.
-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 5.14.0-2-amd64 (SMP w/8 CPU threads)
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
Versions of packages backintime-qt depends on:
ii backintime-common 1.2.1-3
ii libnotify-bin 0.7.9-3
ii policykit-1 0.105-31
ii python3 3.9.2-3
ii python3-dbus.mainloop.pyqt5 5.15.4+dfsg-4
ii python3-pyqt5 5.15.4+dfsg-4
ii x11-utils 7.7+5
Versions of packages backintime-qt recommends:
ii python3-secretstorage 3.3.1-1
Versions of packages backintime-qt suggests:
pn meld | kompare <none>
-- no debconf information
