https://bugs.kde.org/show_bug.cgi?id=372144

--- Comment #1 from David Oldford <david_oldf...@hotmail.com> ---
I can't believe it took me this long and this many combinations and
permutations to figure this out... I looked in my github settings and found the
personal access tokens. There was one for kdevelop. I deleted it and then was
able to authorize successfully on my main machine and not in my vm... It would
appear that kdevelop always tries to use the same name for an access token and
github doesn't like regenerating the same thing over and over again. I would be
a corner case user who uses (or wants to use at this point :) ) kdevelop on
multiple machines. It should be pretty easy to fix by adding the hostname and a
nonce to the end of the token name when it is generated with github (I
assume...).

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to