Bug 415062 - Fails to submit crash report when backtrace is too big
Summary: Fails to submit crash report when backtrace is too big
Status: RESOLVED WORKSFORME
Alias: None
Product: drkonqi
Classification: Applications
Component: general (show other bugs)
Version: 5.14.5
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-12-11 17:23 UTC by Ralf Jung
Modified: 2020-01-12 04:33 UTC (History)
1 user (show)

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


Attachments
the message DrKonqi failed to submit (66.00 KB, text/plain)
2019-12-11 17:23 UTC, Ralf Jung
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ralf Jung 2019-12-11 17:23:38 UTC
Created attachment 124436 [details]
the message DrKonqi failed to submit

SUMMARY
DrKonqi fails to submit a bug report when the backtrace is too long.


STEPS TO REPRODUCE
1. Make a KDE application crash with a big backtrace (and lots of threads)
2. Try to submit the crash report through DrKonqi

OBSERVED RESULT

It says "Error sending crash report", "Error message was: Comments cannot be bigger than 65535 characters".


EXPECTED RESULT

DrKonqi shouldn't fail to submit a bugreport. Maybe make the backtrace an attachment instead?


SOFTWARE/OS VERSIONS

Operating System: Debian GNU/Linux 
KDE Plasma Version: 5.14.5
Qt Version: 5.12.5
KDE Frameworks Version: 5.62.0
Kernel Version: 5.3.0-2-amd64
OS Type: 64-bit
Processors: 8 × Intel® Xeon® CPU E3-1505M v5 @ 2.80GHz
Memory: 15,6 GiB of RAM

ADDITIONAL INFORMATION

I attached the message DrKonqi tried to submit.
Comment 1 Nate Graham 2019-12-13 12:53:05 UTC
You're using Plasma 5.14.5, which is no longer maintained upstream. Can you check with Plasma 5.17?
Comment 2 Ralf Jung 2019-12-13 13:01:42 UTC
I can, once it lands in my distro...
Though also I wouldn't know how to trigger this error on purpose.
Comment 3 Bug Janitor Service 2019-12-28 04:33:07 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 Bug Janitor Service 2020-01-12 04:33:11 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!