Search Criteria
Package Details: tutanota-desktop 220.240411.0-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/tutanota-desktop.git (read-only, click to copy) |
---|---|
Package Base: | tutanota-desktop |
Description: | Official Tutanota email client |
Upstream URL: | https://tuta.com |
Licenses: | GPL-3.0-or-later |
Submitter: | yochananmarqos |
Maintainer: | yochananmarqos (ajgraves) |
Last Packager: | yochananmarqos |
Votes: | 27 |
Popularity: | 0.091967 |
First Submitted: | 2020-03-03 17:27 (UTC) |
Last Updated: | 2024-04-12 14:34 (UTC) |
Dependencies (7)
- alsa-lib
- gtk3 (gtk3-ubuntuAUR, gtk3-no_deadkeys_underlineAUR, gtk3-patched-filechooser-icon-viewAUR, gtk3-classic-xfceAUR, gtk3-classicAUR)
- libsecret
- nss (nss-hgAUR)
- git (git-gitAUR) (make)
- nvmAUR (nvm-gitAUR) (make)
- python (python32AUR, python37AUR, python310AUR) (make)
Latest Comments
1 2 3 4 5 6 7 Next › Last »
Achilleus commented on 2023-12-21 16:20 (UTC) (edited on 2023-12-21 16:20 (UTC) by Achilleus)
Drack commented on 2023-12-20 10:32 (UTC) (edited on 2023-12-20 10:33 (UTC) by Drack)
@tyler19820201 I had the same problem. On my side, the problem was that I didn't setup any wallet or keyring on my system that Tutanota support. I run KDE's Plasma, so I installed KDE Wallet, created a wallet using the default name. From there, Tutanota was able to access the wallet and store my email credentials. I think that Tutanota use libsecret as a backend, that access KDE Wallet through the Secret Service API using D-Bus. That fixed the issue on my system.
P.S.: To use KDE Wallet, you may read https://wiki.archlinux.org/title/KDE_Wallet
tyler19820201 commented on 2023-12-14 08:59 (UTC)
After update i am having Could not access secret storage error. Any workaround for this to fix??
Achilleus commented on 2023-12-05 21:13 (UTC)
@yochananmarqos
Sorry for that - I've corrected my comment.
I'm always building packages with yay, and if this fails, then using the standard way with makepkg. Both ways failed this time.
yochananmarqos commented on 2023-12-05 20:47 (UTC) (edited on 2023-12-05 20:47 (UTC) by yochananmarqos)
@Achilleus: I build in a clean chroot every time I update. It built just fine earlier.
Either way, I can't read that, please use proper formatting:
```
type or paste code here
```
Achilleus commented on 2023-12-05 20:45 (UTC) (edited on 2023-12-05 20:59 (UTC) by Achilleus)
yochananmarqos commented on 2023-12-01 17:14 (UTC)
@painfularch: If it were possible, I would have already done it.
painfularch commented on 2023-12-01 10:59 (UTC)
@yochananmarqos could you update the PKGBUILD to use system electron? See https://wiki.archlinux.org/title/Electron_package_guidelines for reference.
andrito commented on 2023-07-26 19:14 (UTC)
npm ERR! gyp ERR! node -v v16.16.0 npm ERR! gyp ERR! node-gyp -v v9.0.0 npm ERR! gyp ERR! not ok
1 2 3 4 5 6 7 Next › Last »