Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Could not access secret storage #7247

Open
2 tasks done
Shshark opened this issue Jul 19, 2024 · 20 comments
Open
2 tasks done

Could not access secret storage #7247

Shshark opened this issue Jul 19, 2024 · 20 comments
Labels
bug broken functionality, usability problems, unexpected errors desktop Desktop client related issues

Comments

@Shshark
Copy link

Shshark commented Jul 19, 2024 •
edited
Loading

  • This is not a feature request (existing functionality does not work, not missing functionality).
    I will request features on forum or via support.
  • I've searched and did not find a similar issue.

Describe the bug
I am running Windows 10 after last update 235.240718 (as I recall)I keep getting "Could not Access Secret Storage" . I have uninstalled and deleted everything I can find related to Tuta, ended task, restarted several times after uninstalls and reinstallation three times. Nothing works I keep getting the same error window. This problem does not seem to plague my android version on the phone.
To Reproduce
Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

  • OS: [e.g. iOS]
  • Desktop Environment, if applicable (on Linux)
  • Version [e.g. 22]

Additional context
Add any other context about the problem here.
@Shshark Shshark added bug broken functionality, usability problems, unexpected errors desktop Desktop client related issues labels Jul 19, 2024
@charlag
Copy link
Contributor

charlag commented Jul 22, 2024

hi, thank you for the report!
Could you please try to get logs (you can click on the version number on the login screen, you can go to settings->about->send logs or you can start from command line) and see if there's any specific error that you see?

@charlag charlag mentioned this issue Jul 25, 2024
Closed
@Shshark
Copy link
Author

Shshark commented Jul 25, 2024 via email

@njmulsqb
Copy link

Facing same issue
image

@sang-shelton
Copy link

The app was running fine until a couple of days and i started seeing this issue as well

Screenshot_20240825_154906

System info 

Operating System: Manjaro Linux 
KDE Plasma Version: 6.0.5
KDE Frameworks Version: 6.5.0
Qt Version: 6.7.2
Kernel Version: 6.9.12-3-MANJARO (64-bit)
Graphics Platform: X11
Processors: 32 × AMD Ryzen 9 5950X 16-Core Processor
Memory: 31.3 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 3060/PCIe/SSE2
Manufacturer: Micro-Star International Co., Ltd.
Product Name: MS-7C91
System Version: 1.0

@astrodv
Copy link

astrodv commented Sep 10, 2024 •
edited
Loading

Try to delete your tuta config folder (don't know which one is on windows, on linux it is ./config/tutanota ) and restart the app.

@sang-shelton
Copy link

Try to delete your tuta config folder (don't know which one is on windows, on linux it is ./config/tutanota ) and restart the app.

Thanks much, that worked.
My config file is in /home/user/.config/tutanota-desktop

@Shshark
Copy link
Author

Shshark commented Sep 15, 2024 via email

@nitschis
Copy link

Hey, would you know it, everything is broken again.

Only deleting the config worked, nice, now I have to rebuild my search index again, for literally 16 hours.. This is getting unbearable.

@astrodv
Copy link

astrodv commented Sep 18, 2024

I wonder if we can just delete a specific subfolder/file inside the ./config folder then..

@nitschis
Copy link

now I have to rebuild my search index again

2 Hours later, on a Gigabit line and high-end PC. Such a great user experience.

Screenshot_20240918_171309

@wantija
Copy link

wantija commented Jan 21, 2025

Had this happen to me, on Linux using KeepassXC for my secret service. For me I just had to delete (or backup then delete just in case) the files in ~/.config/tutanota-desktop/safe_storage/.

@ThracianKnight1907
Copy link

I have the same issue on Fedora KDE 41 and tutanota flatpak v 261250116.0

@wantija
Copy link

wantija commented Jan 22, 2025

Actually, looks like v261.250116.0 isn't using my secret storage? I have KeepassXC closed and I am able to open up the desktop program. I've also deleted ~/.config/tutanota_desktop and ~/.config/tuta_integration.

@nitschis
Copy link

Had this happen to me, on Linux using KeepassXC for my secret service. For me I just had to delete (or backup then delete just in case) the files in ~/.config/tutanota-desktop/safe_storage/.

Thank you, this worked for me. I had to re-login, but at least my search index did not get deleted. I stopped updating the app because of the hassle, it decided to still update without me pressing the popup, that's why I just had this issue again.

@charlag charlag marked this as a duplicate of #8345 Jan 23, 2025
@charlag charlag mentioned this issue Jan 23, 2025
Closed
2 tasks
@stemy2
Copy link

stemy2 commented Jan 23, 2025

Actually, looks like v261.250116.0 isn't using my secret storage? I have KeepassXC closed and I am able to open up the desktop program. I've also deleted ~/.config/tutanota_desktop and ~/.config/tuta_integration.

At my side, the folder is empty. And when i delete the folder and relaunch the app, it recreates it and shows the error message again.

@charlag
Copy link
Contributor

charlag commented Jan 23, 2025

@stemy2 for you the error is not the the data is out of sync with keychain but that keychain implementation was not found at all. You need either an app that provides secret storage D-Bus implementation or override it with --password-store= argument

@stemy2
Copy link

stemy2 commented Jan 23, 2025

@stemy2 for you the error is not the the data is out of sync with keychain but that keychain implementation was not found at all. You need either an app that provides secret storage D-Bus implementation or override it with --password-store= argument

I actually have an app for this purpose named kWallet, why is the app unable to detect it? And i don't get where i'm supposed to put the argument '--password-store='.

@charlag
Copy link
Contributor

charlag commented Jan 23, 2025

@stemy2 it depends on your set up a bit.

Arch Wiki says:

Note: Since KDE Frameworks 5.97.0 KDE Wallet supports org.freedesktop.secrets DBus API and can now be used by libsecret for storing and retrieving passwords and other secrets using the Secret Service API.

If that is the case you shouldn't need to do anything. We select gnome-libsecret backend automatically.

If you are on an older version you might want to tell the app to use KWallet backend directly. See https://chromium.googlesource.com/chromium/src/+/master/docs/linux/password_storage.md

@stemy2
Copy link

stemy2 commented Jan 25, 2025 •
edited
Loading

@stemy2 for you the error is not the the data is out of sync with keychain but that keychain implementation was not found at all. You need either an app that provides secret storage D-Bus implementation or override it with --password-store= argument

I tried all the possible option with ad-hoc keyring managers, nothing works.

And i have to say this: the global UX with the desktop app is quite painful. Since the first time i tried to make it work, it worked like a charm only for a very short time.

@wrdhub wrdhub mentioned this issue Jan 27, 2025
Open
@charlag
Copy link
Contributor

charlag commented Jan 27, 2025

@stemy2 you might need to delete local data before trying out other keychains because if you just swap out the keychain the local data won't be decryptable anymore. We would have to see the error you are getting to know more.

We are working on adding more graceful handling for this error:
#8380

but we can't prevent the issues with the keychain itself

@charlag charlag mentioned this issue Jan 27, 2025
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug broken functionality, usability problems, unexpected errors desktop Desktop client related issues
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
9 participants
@charlag @wantija @stemy2 @njmulsqb @nitschis @ThracianKnight1907 @astrodv @sang-shelton @Shshark