SUMMARY When trying to submit a bug report via drkonqi, it complained about token errors, exactly as in the screenshots given in #411983. Hitting the Retry button just kept cycling between two error messages similar to those in the aforementioned bug. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.21.2 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Happened right after #433971 when trying to report #433970. Is the token bound to an IP address? I was using Tor as the system proxy, so my outbound IP address via Tor might have changed between "logging in" and submitting the bug report. When it failed I would have liked to try to login again, but there was no way to do that, because the UI provided no login interfaces, and the "back" button was disabled. I don't know for sure, but since all of this happened during the crash of an essential KDE component (plasmashell) during login, I think I might have been fortunate to be able to access other programs via krunner (including my browser to report this), instead of my login session terminating or ending up with no running programs besides the non-functioning drkonqi. I also saw no button in drkonqi to try to restart the crashing program, just one to end the wizard. I found this to be a bit scary.
Which distro are you on?
Gentoo.
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.
(In reply to Harald Sitter from comment #3) > Please add the following to your /etc/environment > > QT_LOGGING_RULES="org.kde.drkonqi.*=true;kf.kio.kio_http=true" > KDE_FORK_SLAVES=1 I added this to /etc/environment, started a new session, modified the kcalc sources to get a crashing kcalc binary to invoke drkonqi, tried to file a bogus bug report and succeeded in filing bug #434155 (i.e. the original issue did not reproduce). While I could probably "try more" to reproduce the bug in more similar conditions that were present while this issue occurred, I don't think spamming bugs.kde.org with more bogus reports would be tolerated.
You can add DRKONQI_KDE_BUGZILLA_URL="https://bugstest.kde.org/" to the environment as well to route bug reports go to a test instance of bugzilla. Otherwise just keep it set up the way it is until you hit the bug again. Considering that it isn't very reproducible I rather do suspect something funny was going on with tor exit nodes that we'll not be able to do much about. As mentioned, there's seconds, at most, between the token refresh and the submission.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!