# Duplicati 2.3.0.1-1 fails to access key ring and crashes **URL:** \ **Category:** Support\ **Created:** [May 29, 2026, 7:36pm UTC](https://forum.duplicati.com/t/duplicati-2-3-0-1-1-fails-to-access-key-ring-and-crashes/22436 "2026-05-29T19:36:51Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Gotit](https://forum.duplicati.com/letter_avatar_proxy/v4/letter/g/ecae2f/32.png) [@Gotit](https://forum.duplicati.com/u/Gotit)\ **Post date:** [May 29, 2026, 7:36pm UTC](https://forum.duplicati.com/t/duplicati-2-3-0-1-1-fails-to-access-key-ring-and-crashes/22436/1 "2026-05-29T19:36:51Z")
Hi - I upgraded working Duplicati to v2.3.0.1-1, on EndeavourOS, and now on launch it tries to access gnome key ring, but doesn’t have the password. I get a screen prompt to enter the password (which I don’t have), click cancel and Duplicati crashes. I think this is similar to the issue in [https://forum.duplicati.com/t/crash-2-3-0-1-on-start-kubuntu-26-04/22361](https://forum.duplicati.com/t/crash-2-3-0-1-on-start-kubuntu-26-04/22361). Libsecrets is already on my system. I installed Seahorse and Duplicati worked once, but now crashes again. Here’s the report: > $ ./duplicati > Crash! > Duplicati.Library.Interface.UserInformationException: Server crashed on startup > - → Duplicati.Library.Interface.UserInformationException: Dimissed collection unlock prompt > at Duplicati.Library.SecretProvider.LibSecret.SecretCollection.UnlockAsync() > at Duplicati.Library.SecretProvider.LibSecretLinuxProvider.InitializeAsync(Uri config, CancellationToken cancellationToken)at Duplicati.Library.DynamicLoader.SecretProviderLoader.GetDefaultSecretProviderForOperatingSystem(CancellationToken cancellationToken) > at Duplicati.Library.Main.SecretProviderHelper.GetDefaultSecretProvider(Dictionary`2 options, CancellationToken cancellationToken) > at Duplicati.Server.Program.Main(IApplicationSettings applicationSettings, String[] \_args) > at Duplicati.GUI.TrayIcon.HostedInstanceKeeper.\<\>c\_\_DisplayClass5\_0.\<.ctor\>b\_\_0(Object \_) > -– End of inner exception stack trace — > at Duplicati.GUI.TrayIcon.HostedInstanceKeeper..ctor(IApplicationSettings applicationSettings, String[] args) > at Duplicati.GUI.TrayIcon.Program.Main(String[] \_args) > at Duplicati.GUI.TrayIcon.Net10.Program.\<\>c\_\_DisplayClass0\_0.b\_\_0() > at Duplicati.Library.Crashlog.CrashlogHelper.WrapWithCrashLog[T](Func`1 method) > Unhandled exception. Duplicati.Library.Interface.UserInformationException: Server crashed on startup > - → Duplicati.Library.Interface.UserInformationException: Dimissed collection unlock prompt > at Duplicati.Library.SecretProvider.LibSecret.SecretCollection.UnlockAsync() > at Duplicati.Library.SecretProvider.LibSecretLinuxProvider.InitializeAsync(Uri config, CancellationToken cancellationToken)at Duplicati.Library.DynamicLoader.SecretProviderLoader.GetDefaultSecretProviderForOperatingSystem(CancellationToken cancellationToken) > at Duplicati.Library.Main.SecretProviderHelper.GetDefaultSecretProvider(Dictionary`2 options, CancellationToken cancellationToken) > at Duplicati.Server.Program.Main(IApplicationSettings applicationSettings, String[] \_args) > at Duplicati.GUI.TrayIcon.HostedInstanceKeeper.\<\>c\_\_DisplayClass5\_0.\<.ctor\>b\_\_0(Object \_) > -– End of inner exception stack trace — > Aborted (core dumped) ./duplicati I also checked: > $ busctl --user list | grep secrets > org.freedesktop.secrets 1273 gnome-keyring-d gotit :1.0 user@1000.service - - Any thoughts on what I can try next ---
**Author:** ![Gotit](https://forum.duplicati.com/letter_avatar_proxy/v4/letter/g/ecae2f/32.png) [@Gotit](https://forum.duplicati.com/u/Gotit)\ **Post date:** [June 7, 2026, 8:42pm UTC](https://forum.duplicati.com/t/duplicati-2-3-0-1-1-fails-to-access-key-ring-and-crashes/22436/2 "2026-06-07T20:42:56Z")
So, I tried to downgrade Duplicati to the previous version, but that started to become a rabbit hole as v2.3.0.1-1 uses a newer DB version. I forced a reinstall of the current version, but still no joy. Any thoughts on next steps would be appreciated. Thanks. ---
**Author:** ![ts678](https://forum.duplicati.com/letter_avatar_proxy/v4/letter/t/8491ac/32.png) [@ts678](https://forum.duplicati.com/u/ts678)\ **Post date:** [June 7, 2026, 9:45pm UTC](https://forum.duplicati.com/t/duplicati-2-3-0-1-1-fails-to-access-key-ring-and-crashes/22436/3 "2026-06-07T21:45:13Z")
[DatabaseTool](https://docs.duplicati.com/duplicati-programs/command-line-interface-cli-1/databasetool) can [Downgrade](https://docs.duplicati.com/duplicati-programs/command-line-interface-cli-1/databasetool#downgrade) if you like, or post you cited had this, which seems like it should avoid the crash that you’re experiencing: > [@Crash 2.3.0.1 on Start (Kubuntu 26.04)](https://forum.duplicati.com/t/crash-2-3-0-1-on-start-kubuntu-26-04/22361/3): > > Set the `--disable-db-encryption=true` commandline option (or `DUPLICATI__DISABLE_DB_ENCRYPTION=true` environment variable). ---
**Author:** ![kenkendk](https://forum.duplicati.com/user_avatar/forum.duplicati.com/kenkendk/32/5305_2.png) [@kenkendk](https://forum.duplicati.com/u/kenkendk)\ **Post date:** [June 8, 2026, 3:34pm UTC](https://forum.duplicati.com/t/duplicati-2-3-0-1-1-fails-to-access-key-ring-and-crashes/22436/4 "2026-06-08T15:34:46Z")
> [@Gotit](#): > > Any thoughts on next steps would be appreciated. Thanks. This will be fixed with the next stable patch release, but for now you need to set a different secret provider, to avoid loading `libsecret`. You can start Duplicati like this: ```plaintext duplicati --secret-provider=file:///home//.config/.duplicati-keys.json?passphrase= --disable-db-encryption=true ``` This will tell Duplicati to use a file to read/write secrets, and at the same time avoid writing secrets to encrypt the database. You can skip the `--disable-db-encryption` if you like and then the database will be encrypted, and encryption key will be in the file. ---
**Author:** ![Gotit](https://forum.duplicati.com/letter_avatar_proxy/v4/letter/g/ecae2f/32.png) [@Gotit](https://forum.duplicati.com/u/Gotit)\ **Post date:** [June 8, 2026, 10:09pm UTC](https://forum.duplicati.com/t/duplicati-2-3-0-1-1-fails-to-access-key-ring-and-crashes/22436/5 "2026-06-08T22:09:44Z")
Thanks for the responses. I had another app complain about my login keyring. So, started snooping and found my key ring was corrupt. I deleted it and setup a new one. Duplicati starts fine now. Thanks again.