Bug 456770 - Submission of report fails because too much text is included, but this is not explained by drkonqi to the user.
Summary: Submission of report fails because too much text is included, but this is not...
Status: RESOLVED INTENTIONAL
Alias: None
Product: drkonqi
Classification: Applications
Component: general (show other bugs)
Version: 5.25.3
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-07-15 17:49 UTC by Roke Julian Lockhart Beedell
Modified: 2022-07-18 17:29 UTC (History)
2 users (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 Roke Julian Lockhart Beedell 2022-07-15 17:49:33 UTC 
SUMMARY
Submission of report fails because too much text is included, but this is not explained by drkonqi to the user.

STEPS TO REPRODUCE
1. Include more than 65535 characters of text within report.
2. Attempt to submit report via drkonqi.

OBSERVED RESULT
“Comments cannot be longer than 65535 characters.” appears and the report that has been submitted is rejected.

EXPECTED RESULT
The report should be accepted, or 

SOFTWARE/OS VERSIONS
Windows: Not affected.
macOS: Not affected.
Linux/KDE Plasma: Affected.
KDE Plasma Version: All are affected, but mine is “5.25.3”.
KDE Frameworks Version: Irrelevant, but mine is “5.96.0”.
Qt Version: Irrelevant, but mine is “5.13.3”.

ADDITIONAL INFORMATION
The reporter is unable to remediate their mistake because drkonqi does not allow the user to return to the previous page. 

This problem may be caused by how if I attempt to submit the amount of characters that I included within drkonqi's report via "http://bugs.kde.org", solely “Comments cannot be longer than 65535 characters.” appears and consequently my submission is rejected. If submitted via "http://bugs.kde.org", "Please press Back and try again." appears.
Comment 1 Roke Julian Lockhart Beedell 2022-07-15 19:37:06 UTC 
(In reply to BEEDELL ROKE JULIAN LOCKHART from comment #0)
> The report should be accepted, or
...[or] what "http://bugs.kde.org/show_bug.cgi?id=456768" describes should be provided.
Comment 2 Harald Sitter 2022-07-18 11:38:21 UTC 
Did you actually write a 65k character report though?
Comment 3 Harald Sitter 2022-07-18 11:38:33 UTC 
.
Comment 4 Roke Julian Lockhart Beedell 2022-07-18 14:14:05 UTC 
(In reply to Harald Sitter from comment #2)
> Did you actually write a 65k character report though?

Yes.
Comment 5 Nate Graham 2022-07-18 15:02:51 UTC 
That is too much information; nobody will read a wall of text. Please condense it into something readable. Thanks!
Comment 6 Roke Julian Lockhart Beedell 2022-07-18 17:29:47 UTC 
(In reply to Nate Graham from comment #5)
> That is too much information; nobody will read a wall of text. Please
> condense it into something readable. Thanks!

Yeah, don't worry about that: I foolishly attempted to copy a log into drkonqi rather than attach it to the finished bug-report as a file.

However, a user that has not ever finished the process of bug-reporting would probably not think that to be strange because they might well have not used Bugzilla or GitHub/GitLab previously. Consequently, I believe that explanation of why the report failed is important to ensure that they do not not report any bugs again. I know people lazy enough to not bother again after such a thing.