maces
maces
Shouldn't LXQt use kwallet5 instead of kwallet4 (also see: https://github.com/frankosterfeld/qtkeychain/pull/63)
Decision by user would be best option for me, too.
+1 for the environment variable QTKEYCHAIN_BACKEND, would be sufficient for my needs (currently compiled a custom version)
My thought was: When Distributions renew their version of qtkeychain, they probably also update KDE and KWallet with it. On Arch KDE4 is already deprecated. A configurable option or detection...
In https://sqlalche.me/e/20/xd2s the following is also mentioned: > When using the ORM this is nearly always due to the use of [lazy loading](https://docs.sqlalchemy.org/en/20/glossary.html#term-lazy-loading), which is not directly supported under asyncio...
Docker deployment works with version 1.0.17 but not with 1.0.18 as suggested. (The latest and 1.0.18 tag have the same digest currently)