drkonqi and outdated software

[Justin Zobel]

On 19/11/25 19:09, Harald Sitter wrote:
> Hey!
>
> I currently have an MR open to disable crash reporting to KDE by
> default and would like your input on the matter.
>
> https://invent.kde.org/plasma/drkonqi/-/merge_requests/364
>
> Essentially we have a problem with users sitting on outdated software
> versions, reporting crashes, and then getting their crash closed
> because their version is no longer getting releases from us. So the
> idea is we have a simple knob to turn on/off reporting to KDE at
> compile time and leave it to distributions to toggle this as
> necessary.
>
> When this is disabled, instead of getting the regular drkonqi UX flow,
> the user will get a less integrated flow where they get a notification
> about the crash that takes them to coredump-gui and then from there
> they can click a button to go to the bug report url you have defined
> in os-release.
>
> How the knob is used is mostly up to you. You could have it enabled
> while you ship supported versions but disable it when their support
> ends. Or just leave it disabled and route all crash reporting through
> your bug tracker first, upstreaming as necessary.
>
> Obviously if you release supported versions regularly through rolling
> updates or backports you can always enable reporting to KDE.
>
> There is also the matter of default-off or on. Any preferences?
>
> HS

Does Sentry/DrKonqi not support sending and capturing the version of the 
software?

This would allow you to ignore versions that are unsupported and simply 
close those reports, or filter them out.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/distributions/attachments/20251119/c6252782/attachment.htm>