Bug 404230 - Can not submit a bug report: Login button is disabled
Summary: Can not submit a bug report: Login button is disabled
Status: REOPENED
Alias: None
Product: frameworks-kcrash
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 5.55.0
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: David Faure
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-02-12 10:49 UTC by Tim Richardson
Modified: 2019-03-20 12:16 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
screenshot (110.47 KB, image/png)
2019-02-12 10:49 UTC, Tim Richardson 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Tim Richardson 2019-02-12 10:49:35 UTC 
Created attachment 117995 [details]
screenshot

SUMMARY
I can not submit a bug report: the login button is disabled. I enter my username as my email account (the same one I am using for the web submission of a bug report), password is correct too but I don't get a password validation failure. A screenshot is attached

STEPS TO REPRODUCE
1. Due to a crash in the KDE partition manager, the Crash Reporting Assistant starts. 
2. Can not proceed part the screen in the screenshot
3. 

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
MacOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Operating System: KDE neon 5.14
KDE Plasma Version: 5.15.0
KDE Frameworks Version: 5.55.0
Qt Version: 5.12.0
Kernel Version: 4.18.0-15-generic
OS Type: 64-bit
Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz
Memory: 31.2 GiB of RAM
Comment 1 Nate Graham 2019-02-12 18:27:20 UTC 
Well that's awkward. :(
Comment 2 Christoph Feck 2019-02-12 20:12:55 UTC 

*** This bug has been marked as a duplicate of bug 373099 ***
Comment 3 Tim Richardson 2019-02-12 23:06:26 UTC 
My bug has been marked as a duplicate of a bug which happened to a user who had no internet access. This is not the case with me: the bug report submitted via bugs.kde.org (in a browser requiring internet access) was done immediately after the problem, with no change in connectivity. 

I have reopened this because the 'duplicate' bug does not match the circumstances of this bug report (the reporter had no internet access, I did have internet access). At least, it is far from obvious to me.
Comment 4 Patrick Silva 2019-02-23 15:52:55 UTC 
I can't confirm such problem on my system.

Operating System: Arch Linux 
KDE Plasma Version: 5.15.1
KDE Frameworks Version: 5.55.0
Qt Version: 5.12.1
Comment 5 Tim Richardson 2019-02-23 22:52:02 UTC 
kdepart has not crashed again (I use it regularly, so that's good) so I can not reproduce it, sorry. It was an insanely frustrating problem though. Is there way of deliberate triggering bugs to test it? There are two clues: (a) kdepart runs as root (b) it thought there was no internet access

I would be happy to try to reproduce it if I can "trigger" a bug at will.
Comment 6 Aldoo 2019-03-20 12:16:25 UTC 
I just had this bug (for a crash in akonadiserver), so it's still there.
Sorry this does not help much since I do not know a reliable way to make it happen (although akonadiserver crashes every couple of minutes in my case... ).