Something crashed (I think Double Commander) and I want to share the information to help solving it. Thus I accepted to create a report using the Crash Reporting Assistant. But when the report is done, I am asked to login to the KDE bug tracking system using a username and a password. I have a username (email) and password which I tested several times are correct (ie I can login without problems in the website bugs.kde.org). But the Crash Reporting Assistant dialog says "Error: Invalid username or password". I think this is very discouraging to people who wants to help. It is much more convenient to file a bug this way than to do it manually in the site. Thanks for all your efforts and this great open software.
Can you please provide a screenshot of the error from the reporting assistant?
If you can provide the information requested in comment #1, please add it.
To further investigate this issue, KDE developers need the information requested in comment #1. If you can provide it, or need help with finding that information, please add a comment.
I'm sorry guys, I didn't capture the screen when it happened, assuming that it was going to happen again at some point. But it's been a while now without installing or changing anything so it didn't happen again. If it happens again I will take the screen capture and show you. But I don't see what else you would get from the screen capture: it was the regular login dialog and then the error message I already mentioned. I'm afraid you'll be dissapointed when I show you the screen capture because there will be little further information... but anyway, I will take the screen capture when (if) it happens again. Thanks again and sorry for the delay!
Thanks for the update. We'll close this for now, if you encounter the issue again please capture a screenshot and reopen this bug!
Created attachment 109584 [details] ScreenCapture017.png
Created attachment 109585 [details] ScreenCapture018.png
Created attachment 109587 [details] ScreenCapture019.png
Created attachment 109589 [details] ScreenCapture020.png
Created attachment 109590 [details] ScreenCapture021.png
Created attachment 109591 [details] ScreenCapture022.png
Created attachment 109592 [details] krunner-20171229-185829.kcrash.txt
Hi, it just happened again (when starting krunner). I noticed that before the starting of the KDE Crash handler, there was a message (in the notification area, so I didn't take a screen capture) saying something like "no proxy was detected" or something like this. I screen-captured the rest of the process. You can see the dialog saying the error message I reported in my original posting: "Error: Invalid username or password" In the following screen capture you can see that I logged into the website (obviously using the same login data) with no problems. I hope this helps.
We'll probably need debug output from DrKonqi for this, reassigning to the DrKonqi developers so they can assist us here.
Hi, any news on this? Is there any other information I could help with?
Looks like the Dr Konqi developers haven't seen this unfortunately. Could you please use 'kdebugdialog' to enable all areas, then when you next encounter this, grab the contents of your session log (where this is stored differs depending on the distribution unfortunately - it could be using journald, or storing it as a hidden file in ~/) Once you've got the session log, could you take a look through some of the last lines in it to see what Dr Konqi is trying to do which isn't working?
I am getting this too. Akregator keeps crashing on me but I cannot send the bug report. I get:"Error sending the crash report: /Received unexpected error code 32,000 from bugzilla. Error message was: The cookies or token provide were not valid or have expired. You may login again to get new cookies or a new token../" Selecting Retry gives the same message.I am sure I have seen this before in the past, but can;t find it on Google.
Created attachment 112464 [details] Screenshot of the error
Login has been completely reworked for 5.17 and should be working much more reliably now. Also. The last comment is entirely unrelated to this bug but rather bug #383530