Bug 385089

Summary:	cant login in the bug tracking system through the Crash Reporting Assistant
Product:	[Applications] drkonqi	Reporter:	j22gim
Component:	general	Assignee:	Unassigned bugs <unassigned-bugs-null>
Status:	RESOLVED FIXED
Severity:	grave	CC:	bcooksley, BugZilla, sheedy, sitter
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Mint (Ubuntu based)
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	ScreenCapture017.png ScreenCapture018.png ScreenCapture019.png ScreenCapture020.png ScreenCapture021.png ScreenCapture022.png krunner-20171229-185829.kcrash.txt Screenshot of the error

Description j22gim 2017-09-26 14:26:26 UTC

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.

Comment 1 Ben Cooksley 2017-09-27 07:18:53 UTC

Can you please provide a screenshot of the error from the reporting assistant?

Comment 2 Christoph Feck 2017-10-10 22:56:05 UTC

If you can provide the information requested in comment #1, please add it.

Comment 3 Christoph Feck 2017-10-25 12:00:58 UTC

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.

Comment 4 j22gim 2017-12-10 21:47:03 UTC

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!

Comment 5 Ben Cooksley 2017-12-10 23:42:13 UTC

Thanks for the update.

We'll close this for now, if you encounter the issue again please capture a screenshot and reopen this bug!

Comment 6 j22gim 2017-12-29 22:22:39 UTC

Created attachment 109584 [details]
ScreenCapture017.png

Comment 7 j22gim 2017-12-29 22:23:32 UTC

Created attachment 109585 [details]
ScreenCapture018.png

Comment 8 j22gim 2017-12-29 22:24:07 UTC

Created attachment 109587 [details]
ScreenCapture019.png

Comment 9 j22gim 2017-12-29 22:24:33 UTC

Created attachment 109589 [details]
ScreenCapture020.png

Comment 10 j22gim 2017-12-29 22:24:55 UTC

Created attachment 109590 [details]
ScreenCapture021.png

Comment 11 j22gim 2017-12-29 22:25:26 UTC

Created attachment 109591 [details]
ScreenCapture022.png

Comment 12 j22gim 2017-12-29 22:25:49 UTC

Created attachment 109592 [details]
krunner-20171229-185829.kcrash.txt

Comment 13 j22gim 2017-12-29 22:30:13 UTC

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.

Comment 14 Ben Cooksley 2017-12-30 05:10:57 UTC

We'll probably need debug output from DrKonqi for this, reassigning to the DrKonqi developers so they can assist us here.

Comment 15 j22gim 2018-01-18 16:59:40 UTC

Hi, any news on this? Is there any other information I could help with?

Comment 16 Ben Cooksley 2018-01-28 09:33:03 UTC

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?

Comment 17 Simon Reed 2018-05-07 09:05:27 UTC

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.

Comment 18 Simon Reed 2018-05-07 09:06:18 UTC

Created attachment 112464 [details]
Screenshot of the error

Comment 19 Harald Sitter 2019-07-19 10:05:42 UTC

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