Closed volllly closed 10 months ago
As a temporary workaround the launcher configurationparameter useLegacyDataProtection
can be set to true
.
That might be caused by the serviceuser not being able to access the keyring.
useLegacyDataProtection
to true on linux per default for nowuseLegacyDataProtection
true and false when a proxy string is set.Check if user keyring needs time to become available. or if it is even available for services.
Describe the bug
When installing the launcher as a systemd service on linux the launcher will not start up because it can not access the keyring to write.
To Reproduce
Exceptions (if any)
Further technical details & context