https://bugs.kde.org/show_bug.cgi?id=433972
Harald Sitter <sit...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REPORTED |NEEDSINFO
Resolution|--- |WAITINGFORINFO
--- Comment #3 from Harald Sitter <sit...@kde.org> ---
I've had a look at this and have to say that if the token is IP address bound I
doubt there is anything we can do about the exit node changing in between two
requests. I mean, token business is entirely within bugzilla itself, there is
nothing we can do to influence server-side policies there. drkonqi actually
forces a token refresh just before submitting the report, it's done so since
5.17
https://invent.kde.org/plasma/drkonqi/-/commit/824efbe6aa174a5a4426c93b514c5b8c1e0669ef
For all intents and purposes there'll only be milliseconds between the (2nd)
login and the submission if the IP address was what caused the woes then that
was very unfortunate timing and makes very little sense because hitting retry
does the *exactly* same dance again. i.e. if you retry the token again gets
refreshed.
So, I'm rather suspecting something else was to blame, but I also have no idea
what could have caused it. So, I need the same data as in the other bug:
Please add the following to your /etc/environment
QT_LOGGING_RULES="org.kde.drkonqi.*=true;kf.kio.kio_http=true"
KDE_FORK_SLAVES=1
and then logout and in again, try to reproduce the bug. Immediately after the
error copy your ~/.local/share/sddm/wayland-session.log (I think that's the
path anyway). It probably contains your password, so you want to strip that and
then either attach it here or send it to me directly by mail if you want to be
extra careful not to leak sensitive data that may be in the log.
The log should contain the actual network transfer with bugzilla and give an
idea why exactly things are going wrong.
--
You are receiving this mail because:
You are watching all bug changes.
