GitHub Desktop "The name is not activatable" on Arch Linux

[ghost]

The problem

GitHub Desktop is completely unusable on Arch Linux.

Everytime after authorizing the app with my GitHub account the error "The name is not activatable" appears and GitHub Desktop fails to connect to my GitHub account and I cannot access my repositories.

Since there is no error code or anything else that could hint to the cause, the only things I can provide is a screenshot and the production.log inside ~/.config/GitHub Desktop/logs/

Release version

Version 3.3.8-linux2 (x64)

Operating system

OS: Arch Linux x86_64 | Kernel: 6.7.8-arch1-1 | DE: KDE Plasma 6.0.1 on Wayland

Steps to reproduce the behavior

1. Install GitHub Desktop from the AUR: https://aur.archlinux.org/packages/github-desktop
2. Open GitHub Desktop on Arch Linux.
3. Sign in with your GitHub account.
4. Authorize GitHub Desktop in your webbrowser.
5. Let the GitHub website redirect back to the GitHub Desktop application.
6. The error "The name is not activatable" will appear with no further information.

Log files

2024-03-08.desktop.production.log

Screenshots

Additional context

No response

[Zoddhand]

same issue here.

[olegovechko]

I have the same problem.

[shiftkey]

This is a generic DBUS message from the backing store we need to persist credentials, and it's really all the context we see from the application side. I'd suggest checking the gnome-keyring keychain is setup.

[ShoreNinth]

This is a generic DBUS message from the backing store we need to persist credentials, and it's really all the context we see from the application side. I'd suggest checking the gnome-keyring keychain is setup.

Thanks, sir. It's solved after I have gnome-keyring installed and set up.

[ghost]

This is a generic DBUS message from the backing store we need to persist credentials, and it's really all the context we see from the application side. I'd suggest checking the gnome-keyring keychain is setup.

Thanks, sir. It's solved after I have gnome-keyring installed and set up.

Yup, can confirm that installing gnome-keyring solves the issue.

I guess this issue only applies to users who don't have GNOME as their desktop environment? I'm not sure since I never used GNOME. Have been a loyal KDE user since day 1.

Would be nice if at least gnome-keyring would be added into the PKGBUILD of the github-desktop AUR package as a dependency so it gets installed along with github-desktop.

[Richardk2n]

The PKGBUILD has org.freedesktop.secrets as a dependency. Which is provided by gnome-keyring but also by kwallet which works fine for me. At least for continued use. This might be related to initial setup.

[ghost]

The PKGBUILD has org.freedesktop.secrets as a dependency. Which is provided by gnome-keyring but also by kwallet which works fine for me. At least for continued use. This might be related to initial setup.

Nope, I just set up GitHub Desktop on Arch with gnome-keyring installed. Worked flawlessly.

But as soon as I uninstalled gnome-keyring GitHub Desktop immediately stops working, even if you already have set up your account and repositories.

Funnily enough, if I reinstall gnome-keyring again, GitHub Desktop immediately works again.

[Richardk2n]

Works for me on both my machines (running Manjaro). Assure, that you have kwallet running and unlocked (If you set a separate password, it is locked by default; Maybe needs to be added to PAM manually on Arch). Other than that I am not sure, what I might have installed/configured different from you, but I can assure you gnome-keyring is not required and thus should not be made a requirement.

[ghost]

Works for me on both my machines (running Manjaro). Assure, that you have kwallet running and unlocked (If you set a separate password, it is locked by default; Maybe needs to be added to PAM manually on Arch). Other than that I am not sure, what I might have installed/configured different from you, but I can assure you gnome-keyring is not required and thus should not be made a requirement.

Okay, after further digging I noticed that I had installed kwallet but actually forgot to install kwallet-pam which is important for auto-unlocking of kwallet.

Now it works for me too without gnome-keyring.

[crazymonkyyy]

This is a generic DBUS message from the backing store we need to persist credentials, and it's really all the context we see from the application side. I'd suggest checking the gnome-keyring keychain is setup.

I have no interest in keyrings and other nonsense; I got this message after disabling kde's on a fresh install

I tried deleting .config/"github desktop", but it still didnt work after trying to log in

[axzxc1236]

In my case I have full disk encryption setup and use KDE, I configured SDDM to auto-login (because I already have password required to decrypt boot disk).

Github desktop won't prompt for wallet unlock, but chromium does.

So my work around is to open chromium first, unlock kwallet, then open Github desktop

[RomanShumikhin]

Same issue. I use auto-login feature in SDDM, so kwallet is not unlocked automatically until I start a browser or another app that that requires it and enter my password, after that GitHub Desktop starts working again.