Bug 454204 - Log-in error: [300] login not valid
Summary: Log-in error: [300] login not valid
Status: RESOLVED WORKSFORME
Alias: None
Product: drkonqi
Classification: Applications
Component: general (show other bugs)
Version: 5.24.5
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-05-22 11:32 UTC by Christopher Yeleighton
Modified: 2022-10-11 17:54 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Christopher Yeleighton 2022-05-22 11:32:18 UTC 
SUMMARY
I cannot log in to report a crash :-O

STEPS TO REPRODUCE
1. Wait for Kontact to crash.
2. Log in to report the crash.

OBSERVED RESULT
Log-in error: [300] login not valid

EXPECTED RESULT
Similar crashes

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: openSUSE Tumbleweed 20220520
(available in About System)
KDE Plasma Version: 5.24.5
KDE Frameworks Version: 5.94.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
Comment 1 Harald Sitter 2022-05-22 21:14:24 UTC 
Are you sure you your login data is correct? Any special characters in your password? Does it work when you change your password to something that only contains ascii letters?
Comment 2 Christopher Yeleighton 2022-05-26 16:40:11 UTC 
(In reply to Harald Sitter from comment #1)
> Are you sure you your login data is correct? Any special characters in your
> password? Does it work when you change your password to something that only
> contains ascii letters?

My password contains ASCII letters only.  I am able to log in in the browser.
Comment 3 Bug Janitor Service 2022-06-10 04:35:39 UTC 
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!
Comment 4 Harald Sitter 2022-06-10 09:18:21 UTC 
Not sure why this would be happening then to be honest. Maybe 5.25 will fix it, it's out next week.
Comment 5 Harald Sitter 2022-06-15 18:23:49 UTC 
Any improvement with 5.25?
Comment 6 Bug Janitor Service 2022-06-30 04:37:10 UTC 
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!
Comment 7 Bug Janitor Service 2022-07-15 04:37:06 UTC 
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!
Comment 8 Christopher Yeleighton 2022-10-11 17:48:00 UTC 
(In reply to Harald Sitter from comment #5)
> Any improvement with 5.25?

No improvement as of 5.25.5