Unknown or unsupported transport "disabled" for address "disabled:"

[tellts]

Can't authenticate to GitHub
Unknown or unsupported transport "disabled" for address "disabled:"

This occurs when I click on a menu item:
Clone a repository from the internet ...
After that, I click on the text "Github.com" and then enter the login or email (I tried two options) and the password. Then I clicked on the "Sign in" button.

Version GitHubDesktop-linux-2.3.1-linux1.deb

Open 'About GitHub Desktop' menu to see the Desktop version.
###In the menu about the program version is not written.
Also include what operating system you are using.
###AntiX.
I found a description of the solution to the problem "sudo apt install gnome-keyring" (desktop#5678). It didn’t help me.
Writes:
The gnome-keyring package of the newest version (3.28.2-5) is already installed.

[tellts]

I also tried clicking on the "Sign in using your browser" item. It opens a blank page on which there is no content and this does not help at all.

[shiftkey]

Unknown or unsupported transport "disabled" for address "disabled:"

This seems to be related to how the app tries to store and retrieve credentials. There's an upstream issue atom/node-keytar#132 which explores getting error, and there were a couple of things in there to try.

It's not clear to me which distro you have setup, but maybe the daemon for gnome-keyring isn't running (which would explain the message being raised by dbus). Someone on that thread was able to get this working as part of a TravisCI build by running these two commands:

$ /usr/bin/gnome-keyring-daemon --login
$ /usr/bin/gnome-keyring-daemon --components=secrets --start

[shiftkey]

I also tried clicking on the "Sign in using your browser" item. It opens a blank page on which there is no content and this does not help at all.

Which browser is this launching?

[tellts]

Hello. I am using the operating system antiX-19.1_x64-full.

I was advised to apply these commands, but it did not help.

export NO_AT_BRIDGE=1
eval $(dbus-launch --sh-syntax)
export DBUS_SESSION_BUS_PID
export DBUS_SESSION_BUS_WINDOWID
eval $(echo -n "" | /usr/bin/gnome-keyring-daemon --login)
eval $(/usr/bin/gnome-keyring-daemon --components=secrets --start)

These lines, if I understood correctly, are copied from the page
[(https://github.com/neo4j-devtools/neo4j-desktop/issues/23)]

Which browser is this launching?
Firefox.
It has already been launched. I don’t remember whether a new tab opens or if I opened it in advance and the request was substituted into the address bar.

[shiftkey]

@tellts only other thing I can suggest at this stage is running dbus-monitor in the background to see if a helpful error appears that might explain why it's not working. This guide has some rules to help filter out the noise: https://wiki.ubuntu.com/DebuggingDBus

[jfgordon2]

Might this be related to the dependency added in PR 186? It seems unnecessary to explicitly call gnome-keyring if we already have libsecret unless the linux build is calling gnome-keyring and not just using it as a key store? - @tellts is there any chance you can test building locally?

[tellts]

Hello. I don’t know yet.

[jfgordon2]

@tellts some help getting this set up to build locally is available here if you’re feeling adventurous.

[shiftkey]

@jfgordon2 the app doesn't call gnome-keyring directly, but it requires some sort of backend to handle it's requests to the Secret Service API (what libsecret represents).

We added gnome-keyring in that PR because it's convenient for GNOME users, and should run the necessary daemon that listens for these requests

[shiftkey]

Closing this one out because I don't have any more information to understand this problem.

@tellts if you do have time to reproduce this again the output from dbus-monitor from my earlier comment could help us understand what's happening on your machine #225 (comment)