Linux keyring issues

[DominiqueFrt]

With Kubuntu 20.04 - Vorta 0.7.2 - Borg 1.1.15
Problem since the update at the end of January
Identical problem on 2 machines with 3 accounts each
Complete reinstallation from PPA then Flatpack without success

2021-02-09 13:05:51,922 - vorta.i18n - DEBUG - Loading translation succeeded for ['fr', 'fr-FR', 'fr-Latn-FR']. 2021-02-09 13:05:51,948 - apscheduler.scheduler - INFO - Scheduler started 2021-02-09 13:05:52,195 - root - INFO - Using NetworkManagerMonitor NetworkStatusMonitor implementation. 2021-02-09 13:05:52,202 - vorta.network_status.network_manager - WARNING - Couldn't load settings for /org/freedesktop/NetworkManager/Settings/1 Traceback (most recent call last): File "/app/lib/python3.7/site-packages/vorta/network_status/network_manager.py", line 52, in get_known_wifis settings = self._nm.get_settings(connection_path) File "/app/lib/python3.7/site-packages/vorta/network_status/network_manager.py", line 139, in get_settings return get_result(settings.call('GetSettings')) File "/app/lib/python3.7/site-packages/vorta/network_status/network_manager.py", line 163, in get_result raise DBusException("DBus call failed: {}".format(msg.arguments())) vorta.network_status.network_manager.DBusException: DBus call failed: ['uid 1002 has no permission to perform this operation'] 2021-02-09 13:05:52,277 - vorta.borg.borg_thread - INFO - Running command /app/bin/borg --version 2021-02-09 13:06:08,442 - vorta.network_status.network_manager - WARNING - Couldn't load settings for /org/freedesktop/NetworkManager/Settings/1 Traceback (most recent call last): File "/app/lib/python3.7/site-packages/vorta/network_status/network_manager.py", line 52, in get_known_wifis settings = self._nm.get_settings(connection_path) File "/app/lib/python3.7/site-packages/vorta/network_status/network_manager.py", line 139, in get_settings return get_result(settings.call('GetSettings')) File "/app/lib/python3.7/site-packages/vorta/network_status/network_manager.py", line 163, in get_result raise DBusException("DBus call failed: {}".format(msg.arguments())) vorta.network_status.network_manager.DBusException: DBus call failed: ['uid 1002 has no permission to perform this operation'] 2021-02-09 13:06:12,092 - asyncio - DEBUG - Using selector: EpollSelector 2021-02-09 13:06:48,008 - vorta.borg.borg_thread - DEBUG - Using VortaSecretStorageKeyring keyring to store passwords. 2021-02-09 13:06:54,450 - vorta.network_status.network_manager - WARNING - Couldn't load settings for /org/freedesktop/NetworkManager/Settings/1 Traceback (most recent call last): File "/app/lib/python3.7/site-packages/vorta/network_status/network_manager.py", line 52, in get_known_wifis settings = self._nm.get_settings(connection_path) File "/app/lib/python3.7/site-packages/vorta/network_status/network_manager.py", line 139, in get_settings return get_result(settings.call('GetSettings')) File "/app/lib/python3.7/site-packages/vorta/network_status/network_manager.py", line 163, in get_result raise DBusException("DBus call failed: {}".format(msg.arguments())) vorta.network_status.network_manager.DBusException: DBus call failed: ['uid 1002 has no permission to perform this operation'] 2021-02-09 13:06:54,479 - vorta.network_status.network_manager - WARNING - Couldn't load settings for /org/freedesktop/NetworkManager/Settings/1 Traceback (most recent call last): File "/app/lib/python3.7/site-packages/vorta/network_status/network_manager.py", line 52, in get_known_wifis settings = self._nm.get_settings(connection_path) File "/app/lib/python3.7/site-packages/vorta/network_status/network_manager.py", line 139, in get_settings return get_result(settings.call('GetSettings')) File "/app/lib/python3.7/site-packages/vorta/network_status/network_manager.py", line 163, in get_result raise DBusException("DBus call failed: {}".format(msg.arguments())) vorta.network_status.network_manager.DBusException: DBus call failed: ['uid 1002 has no permission to perform this operation'] 2021-02-09 13:08:12,743 - vorta.network_status.network_manager - WARNING - Couldn't load settings for /org/freedesktop/NetworkManager/Settings/1 Traceback (most recent call last): File "/app/lib/python3.7/site-packages/vorta/network_status/network_manager.py", line 52, in get_known_wifis settings = self._nm.get_settings(connection_path) File "/app/lib/python3.7/site-packages/vorta/network_status/network_manager.py", line 139, in get_settings return get_result(settings.call('GetSettings')) File "/app/lib/python3.7/site-packages/vorta/network_status/network_manager.py", line 163, in get_result raise DBusException("DBus call failed: {}".format(msg.arguments())) vorta.network_status.network_manager.DBusException: DBus call failed: ['uid 1002 has no permission to perform this operation'] 2021-02-09 13:08:47,745 - vorta.borg.borg_thread - DEBUG - Using VortaSecretStorageKeyring keyring to store passwords. 2021-02-09 14:05:56,615 - vorta.borg.borg_thread - DEBUG - Using VortaSecretStorageKeyring keyring to store passwords.

cordially

[m3nu]

So what's the issue you are reporting and can you try to add your logs with line breaks preserved? Will make it easier to read. Thanks!

[DominiqueFrt]

vorta.log
Problem: Backup failure.Cannot access an existing repository or create a new repository.
Message: Please unlock your password manager
cordially

[m3nu]

Have you checked it your issue still happens on the current master branch? There is already a fix for a similar issue.

Else one of our Linux maintainers needs to have a look.

[jetlag666]

Hello, I also have this issue on Kubuntu 20.04 since 3 days ago.

[m3nu]

Please try the current master branch to verify if the fix (#779) applied there resolves your issue.

[peerwal]

Hi, i am running into the same issue using KDE Neon 5.20. Both the flatpak and the latest deb package install come up with the same message: Please unlock your password manager

[DominiqueFrt]

I purged Vorta and Borg
I deleted :
~ / .cache / borg /
~ / .cache / vorta /
~ / .config / borg /
~ / .config / vortac
~ / .local / share / vorta /
~ / .var / app / com.borgbase.Vorta /

Reinstallation from your site: https://vorta.borgbase.com
/ install / linux /

Creation of a new depot

Flatpack: Please unlock your password manager
PPA: Same message

Are there other folders to delete to reset everything

cordially

[m3nu]

Sorry, but I'm unable to reproduce this on Gnome (Fedora/SecretStorage keyring) or KDE (Kubuntu/KWallet keyring) using the latest master branch installed via pip.

I can't comment on individual distribution packages, since they are maintained by external packagers listed here: https://vorta.borgbase.com/install/linux/

[DominiqueFrt]

For information

Cordially

[DominiqueFrt]

After restarting PC:
Administrator account: OK
User account: Problem

Hope this can help

[m3nu]

The issue you are facing is (most likely) already fixed in Github's master branch. So either install that or wait for the next 0.7.3 release. Based on your screenshot, you installed version 0.7.2 from PyPi. If you are unsure on how to install the current master branch, please see our developer docs.

The logs in your screenshot are unrelated to the keyring.

[DominiqueFrt]

For information. Return Vorta 0.7.3

Vorta 0.7.3.pdf

[carobinario]

If you have troubles you should give KeepassXC a try: it's a password manager that supports FreeDesktop.org Secret Service standard, so it can store password from apps, like Vorta, that use that standard.

I had the same Please unlock your password manager issue in Fedora Kde spin. I removed gnome-keyring, disabled kdewallet and enabled Secret Service integration in KeepassXC. Here you can read a tutorial: https://c3pb.de/blog/keepassxc-secrets-service.html.

Tested with Vorta 0.7.2 installed via Flathub.

[m3nu]

Is your issue resolved with the latest release 0.7.3? (Since nobody is testing the Github version, we'll just do more frequent releases.)

[peerwal]

Yes, thanks for your support. It works fine now. Obviously it didn't work with Kwallet and as long as the gnome-keyring daemon was enabled (wondering, why it obviously is enabled by default even on systems using KDE Plasma).

I have been using KeepassXC as my default password manager for a long time just had to upgrade it to the latest version 2.6.4 and enable the Secret Servive option to make Vorta use KeepassXC without issueing that annaoying message

[DominiqueFrt]

Following the update to Vorta 0.7.3, I stay on Vorta 0.7.2.
Update from the software then with pip3 without success.
How to remove all traces of Vorta to redo a clean installation?


Vorta 2021-02-19.pdf

[M4g3dd0]

I have encountered the same issue. I installed Seahorse and unlocked the password manager. I am on Debian testing, Seahorse version 3.38.0.1. Vorta version 0.7.2 Cinnamon version 4.8.6

[m3nu]

Vorta version 0.7.2

You probably want to update Vorta first. Your issue may be adressed in the latest release.

We are also looking for Linux users to help test the current Github version before it's released. Else it's unavoidable that some bugs will be released on Linux.

[DominiqueFrt]

Installation Vorta 0.7.3 from GitHub source, if I have correctly interpreted the instructions
Vorta 0.7.3.pdf

[m3nu]

Nice graphic design work! 👌

To upgrade a package with Pip, try: $ pip install --upgrade vorta

Regarding your error, I don't think it's related to Vorta. Your DBus + Kwallet has some issue. Sadly I can't tell you more than that.

If you have time to debug it yourself, you can follow the code in vorta/keyring/kwallet.py. In try_unlock() it would usually give you a long number. In your case you get an error message. So KWallet is there in __init__(), but causes an error later. I can't reproduce this (Kubuntu 20.20), but if we get more such reports, we should probably unlock the repo in VortaKWallet5Keyring.__init__() and handle the error there.

[JanSchnacki]

I just updated vorta to 0.7.3 via the Ubuntu PPA package, and... YAY! I can backup again.

KWallet is detected successfully again.

[DominiqueFrt]

Vorta 0.7.3 is finally installed
I ended up with 2 different vorta versions on 2 accounts.
So I placed the command "pip3 uninstall vorta" from each account and reinstall vorta from the PPA
The situation is the same with Vorta 0.7.3, works with KeePassXC

I submitted a request to upgrade KeePassXC

I installed d-feet present in the Discover software library.
I don't have the skill to use this tool. Now I can make "gnome-keyring-daemon" and "kwalletd5" executable, restart Vorta without KeePassXC, and return the d-feet information to you if you guide me.

[neurer]

Please forgive if it's not the right place to ask, but my issue appears to be related. I'm on 0.7.3 via samuel-w1 PPA. Backups stopped working with the last update as it asks for KDE Wallet Service. I'm using Gnome keyring/Seahorse only.

[neurer]

@mauromol Yes, that's what it looks like to me too. Here's what removing libkwalletbackend5-5 would do:

sudo apt remove libkwalletbackend5-5
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages were automatically installed and are no longer required:
  kwayland-data kwayland-integration libdbusmenu-qt5-2 libfam0 libgpgmepp6 libkf5auth-data libkf5authcore5 libkf5codecs-data libkf5codecs5 libkf5config-bin libkf5config-data libkf5configcore5 libkf5configgui5 libkf5configwidgets-data libkf5configwidgets5 libkf5coreaddons-data
  libkf5coreaddons5 libkf5crash5 libkf5dbusaddons-bin libkf5dbusaddons-data libkf5dbusaddons5 libkf5guiaddons5 libkf5i18n-data libkf5i18n5 libkf5idletime5 libkf5notifications-data libkf5notifications5 libkf5service-bin libkf5service-data libkf5service5 libkf5wallet-data
  libkf5waylandclient5 libkf5widgetsaddons-data libkf5widgetsaddons5 libkf5windowsystem-data libkf5windowsystem5 libpolkit-qt5-1-1 libqt5texttospeech5
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED:
  libkf5wallet-bin libkf5wallet5 libkwalletbackend5-5

Not exactly sure, but these appear to be the remains of a Kdenlive install. I'll have another look in the next days.

Never the less, a different approach to selecting keyrings seems worth considering.

[m3nu]

Based on the feedback here, it seems that KWallet is also commonly installed. Same as Secret Storage.

So I'll do the same as python-keyring and use KWallet only if the desktop is KDE. This works as expected in the VMs I test (Kubuntu/KDE, Fedora/Gnome, Debian 11/KDE).

If you can, please help test the pull request here or view the new rules to select the correct keyring.

[neurer]

Went ahead and did some testing with 0.7.4:

• removed libkwalletbackend5-5 and its dependencies: Vorta uses Gnome keyring fine
• re-installed libkwalletbackend5-5 and its dependencies: Vorta uses Gnome keyring fine
• libkwalletbackend5-5 does not pull libkf5wallet-bin as a dependency. Went ahead and installed libkf5wallet-bin: Vorta tries using KWallet and fails

It seems as if having libkf5wallet-bin and it's dependencies installed will interfere with selecting the correct keyring. Please mind that this still doesn't mean KWallet is usable in a (non-KDE) desktop environment. So any app that requires libkf5wallet-bin to be present would lead to Vorta keyring selection issues.

Hope this helps with testing any proposed changes.

Last but not least. For now, with libkf5wallet-bin and dependencies gone, my backups are working again. Without config changes or re-linking.

[mauromol]

So, if I understand it right, if you don't have libkf5wallet-bin installed, backups are working fine. If it is, Vorta tries to use KWallet, it can't find the passwords there and backups fail.
If this is the case, this is another clue of the fact that the fallback mechanism is not working properly (in addition to the fact that the use of KWallet is unexpected in your case).

[m3nu]

The fallback is from the detected system keychain to Vorta’s DB. It’s not to another system keychain.

[DominiqueFrt]

Bonjour,

A ce jour Vorta 0.7.3 fonctionne :
Avec KeePassXC sur mon compte administrateur
Sans KeePassXC sur mes 2 comptes utilisateur

Je ne comprend pas ce qui fais la différence.
Cependant, le fait que Vorta fonctionne différemment sur 2 comptes peut permettre de comparer des fichiers.
Je peux poster les fichiers qui pourraient être utiles.

Sur ma seconde machine je n'ai pas eu de problème avec Vorta 0.7.3 sauf devoir reconfigurer les dépôts.

Cordialement

---

Hi,

To date Vorta 0.7.3 works:
With KeePassXC on my administrator account
Without KeePassXC on my 2 user accounts

I don't understand what makes the difference.
However, the fact that Vorta works differently on 2 accounts may allow you to compare files.

I can post any files that might be useful.

On my second machine I had no problem with Vorta 0.7.3 except having to reconfigure the repositories.

Cordially

⁄usr⁄lib⁄python3⁄dist-packages⁄vorta⁄keyring
.pdf
Compte administrateur | ~⁄.cache⁄log⁄vorta.pdf
Compte utilisateur | ~⁄.cache⁄log⁄vorta.pdf

[m3nu]

For your admin account, SecretStorage seems to work, but the password still comes from Vorta's DB. Maybe SS didn't work before?

For the user accounts, they don't seem to have access to a keyring and Vorta's DB is used.

In general, we first try to use a system keyring (KWallet or SS) and then fall back to keeping the password in the DB.

Also recommend to send logs as .log, as you find them instead PDF. A bit hard to read.

[samuel-w]

Looks like your dbus permissions are broken, judging by this error message for the NetworkManager DBus.
DBus call failed: ['uid 1000has no permission to perform this operation']

[m3nu]

Looks like your dbus permissions are broken, judging by this error message for the NetworkManager DBus.
DBus call failed: ['uid 1000has no permission to perform this operation']

Careful. This error could be from network_manager. It tries getting the current and past Wifis in a few different ways and prints the error if it fails.

For everyone else having this error: There is now a potential fix merged into the master branch. You can try it using

$ pip install --force-reinstall git+https://github.com/borgbase/vorta.git

[samuel-w]

I also patched it in to my PPA.

[m3nu]

If the master branch is working for all Linux users, we should do a small release soon.

Would appreciate feedback on this. Quick way to install from the current master branch:

$ pip install --force-reinstall git+https://github.com/borgbase/vorta.git

[m3nu]

Did a minor release to hopefully address all the issues reported here. Thanks to everyone for adding fixes so quickly.

If you want to make sure the next release works well on your platform and give early feedback, please consider joining the Pre-release testing thread.

[m3nu]

Maybe we should make the keyring integration optional. So Linux users can disable it, if they don't use the keyring that's installed.: #898

[samuel-w]

I don't see the case where I have a password manager installed and I don't want to use it in applications. I'd rather fix/remove the code causing the bugs.

[DominiqueFrt]

Hi,

Test today Vorta 0.7.4
Passwords with Kwallet or KeePassXC: OK
One minor note: The main window opens at startup.

[m3nu]

Minor release 0.7.5 is out that addresses the keyring issues reported here. Main changes:

• You can disable the system keychain and just keep the repo passphrase in Vorta's settings DB (slightly less secure)
• Keyring is now picked by assigning a score. So it will prioritized KWallet on KDE and Secret Storage on Gnome.

Maybe additional rules could be added here. If you do NOT use Gnome or KDE, but have both, KWallet and SecretStorage installed, it will use SecretStorage.

[alastairdb]

I'm running KDE on Ubuntu 20.04. I have two pip installed versions of vorta. Version 0.6.24 works fine. Version 0.7.5 gives me the following error message:

Your repo passphrase was stored in a password manager which is no longer available.
Try unlinking and re-adding your repo.

I get this message no matter what is set in "Store repository passwords in system keychain, if available."

I'm reluctant to unlink and relink in case I lose all the information in the "Archives" tab. I guess I'll keep using 0.6.24 until it breaks or I learn more about relinking

[m3nu]

Archive details will be fetched from the repo when re-linking. You will only loose the size of the added data.

I would still recommend to relink, since currently you don't know where your password is saved. Previous Vorta versions assumed only one password manager is installed at a time. This turned out to be too naive, since many system come with both, SecureStorage and KWallet. For your case, I guess the password is in SS, but now Vorta looks in KWallet only. Hence the message you get.

Alternatively you may be able to add some random repo and then edit the URL and password in KWallet to match your other repo. Then it will be found without relinking anything.

[carobinario]

Hi,
I'm using Vorta 0.8.3 (Borg 1.2.0) with Opensuse Tumbleweed (20220409), KDE Plasma Version: 5.24.4, KDE Frameworks Version: 5.92.0, Qt Version, 5.15.2. Also I'm using KeepassXC 2.7 as Secret service password manager.

I always back up without problem to an usb hard disk and to Borgbase (two different profiles).

Today I created a third profile to backup to the usb hard disk. Unfortunately Vorta hanged when I created the repo

2022-04-11 18:18:51,027 - vorta.borg.borg_job - WARNING -
IMPORTANT: you will need both KEY AND PASSPHRASE to access this repo!
If you used a repokey mode, the key is stored in the repo, but you should back it up separately.
Use "borg key export" to export the key, optionally in printable format.
Write down the passphrase. Store both at safe place(s).

After restarting Vorta I tried to backup but I had this error:

2022-04-11 18:29:15,829 - vorta.borg.borg_job - DEBUG - Password not found in primary keyring. Falling back to VortaDBKeyring.
2022-04-11 18:29:15,830 - vorta.notifications - DEBUG - notification not suppressed

What's wrong? Why can I backup to the other two repositories but not to the third one?

Here is the log: vorta.log

Thanks

[real-yfprojects]

Hi @carobinario,

I don't think your comment relates to the post you commented on. This discussion is already has a lot of post. I therefore ask you to open a new issue for your problem.

[carobinario]

Ok, thanks.