desktop: Can't log into github desktop
Describe the bug
When logging into GitHub desktop the application hangs
Version & OS
2.9.9-linux2 (github-desktop-bin on the aur) Arch Linux (fresh install)
What I’ve tried
2 browsers (firefox and brave) Reinstalling the program adding:
source /etc/X11/xinit/xinitrc.d/50-systemd-user.sh &
eval $(/usr/bin/gnome-keyring-daemon --start) &
export SSH_AUTH_SOCK &
assuming it was a keyring issue (which it wasnt)
Images of what happened
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 8
- Comments: 33 (5 by maintainers)
Note: These reports are mostly about Arch Linux. This is probably just because 2.9.9 is in the AUR but is not yet in the deb/rpm repos.
Update: Yes. Definitely not an Arch-specific issue.
For Flatpak users, you can downgrade to 2.9.6 on this commit:
(Mind that the commit used by the flatpak is different from the repository, see instructions on downgrading).
Once I finished the authentication and updated to 2.9.9, it still works.
I just downgraded to v2.9.6 for now.
I had the same problem and the solution was to have version 2.6.6 installed and from that I was able to log in, then just go to the synapics package manager and run update, then go to 2.9.6 already logged in.
I’m going thru the same issue too. The application gets stuck, always waiting for the login, just after the authorization and redirection by the browser. It’s possible to cancel, but the process of syncing never ends. Here are my pieces of information so far:
Os System and versions: Github Desktop 2.9.9-linux2 Ubuntu 20.04.4 LTS
What I’ve tried so far: Installation by line code (2.9.6) Download and install Deb packages (.deb) direct from Github Shiftkey profile (I’ve tried several versions from 2.9.6 until 2.9.9 yet, and counting.)(uninstall and reinstall) Changing default browsers (I’ve tried Chrome, Firefox, and Chromium)
Images:
After the attempts described before, I only typed some commands such as auto-remove, update, and upgrade before turning the system off, and when I turned it on again, the application was working perfectly. I did not realize what exactly happened but now, the application is working smoothly. The last installation was made by the command line.
I hope this can help somehow. Thanks!
Given the fact that this issue has been around for almost two weeks now and other issues about this are popping up, should someone downgrade this to 2.9.6 on each package manager (or at least add a disclaimer in the readme or release notes)?
Yeah true ^^ didn’t checked the version difference.
@VanderlyBelo delete 2.9.9 install 2.9.6 and it’s work! very thanks you thank you for your help
Apologies for the delay in digging into this - I’ve had many other things distracting me. I recommend downgrading in the meantime to an earlier version, as those should be unaffected.
I’ve dusted off my test machine and walked through the steps here and I see this
--enable-breakpadmessage when I do the sign-in flow, so clearly something’s broken here with how the app is being re-launched with the2.9.9update.Great! This is the same as downgrading because the apt repo is still on 2.9.6.
Have this error noticed this in the logs:
2022-03-08T17:54:01.677Z - warn: [ui] Unknown URL action: unknown - payload: {"name":"unknown","url":"--enable-crashpad"}The full logs: