Proton Authenticator App "Secure Key Issues"

User Support General
1

I am running the lastest version of QubesOS 4.3 as of posting this and I am running the lastest version of Fedora 43 and all packages.

Some background info if you need more please ask:

  • I installed Proton Authenticator ( PA ) by going to Proton’s website and downloading the .RPM file and to install it I just when to the folder it was in and ran “sudo dnf install <name_of_package>”
  • The version of PA I am running is the lastest as of writting this: 1.1.4

My Issue:
Before today PA was working with no issues. Now when I go to the terminal and run “proton-authenticator” the app opens like normal and asks me for a password like always, but when I type in the password (regardless of if it is the right or wrong password) I get a gray screen and it says gray for ever. No matter how long I wait. The app never crashes, no more logs are added, the window can be resized and moved around. The only error that does occur in the terminal is: Can’t find a11y bus: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ExecFailed: Failed to execute program org.a11y.Bus: Permission denied. It is the first thing that shows up in the terminal and the only error. Also when I run the same command, but with sudo in front I get a pop up inside of the app that says, “Secure Key Issues” that says PA cannot create a secure key. I need help to fix this so I can use my 2FA app of choice.

2

Even if you use seahorse, is it still unable to unlock your keyring?
I’m not sure if the issue involves the app or a qube, but when I tested it myself, I noticed some strange behavior related to the app’s keyring functionality.

3

I do not use seahorse.

4

Try
NO_AT_BRIDGE=1 proton-authenticator

Ensure that at-spi is installed
sudo dnf install at-spi2-core

You can check if the bus is running properly:
systemctl --user status dbus