On Thu, Apr 7, 2022 at 3:44 PM Christopher <ctubbsii(a)fedoraproject.org> wrote:
On Thu, Apr 7, 2022 at 2:21 PM Michael Catanzaro <mcatanzaro(a)gnome.org> wrote:
>
> On Thu, Apr 7 2022 at 02:10:06 PM -0400, Christopher
> <ctubbsii(a)fedoraproject.org> wrote:
> > At the very least, it could give a more useful error message. One of
> > my questions in the original post was whether this is even related to
> > OTP or not... it's not obvious that it is related at all. So far,
> > there's discussion in response regarding OTP... I have no reason to
> > believe that's even the problem yet. It would help if somebody could
> > confirm that OTP is the cause of this error, and that it still works
> > otherwise.
>
> Have you reported a bug (upstream, not downstream)? A bug report would
> be the place to start.
No. I don't know who upstream is for this. As far as I can tell, this
is a login service specifically for Fedora developers in GOA. I don't
even know if this is a message coming remotely, from Fedora's KDC,
something specific to my FAS account, from a Kerberos library, from
GOA, or the specific extension or whatever that adds the Fedora
account as an option to GOA. I usually try to do information gathering
before filing bugs. Maybe it's a known issue? Maybe it's
Fedora-specific? Right now, though, I'm just hoping to understand if
it's just me, or if others, with or without OTP, have also seen it, so
I know where to look next. If I were to file a bug right now, it would
almost certainly be against the wrong component, and merely say "saw
error message X", because I have no information yet.
The original message didn't come to fedora-devel. Could you restate
what the original issue was so we can take a look?