State of server-side retrace of KDE crashes?

[Nate Graham]

For what it's worth, I don't think server-wise retracing is solely a 
workaround for distro-specific issues. Even for distros that ship debug 
symbols, I often find in my bug triaging that it can be a challenge to 
get users to actually use them.

The DrKonqi auto-symbol-downloader sometimes doesn't work (a bug that 
should be fixed, of course), and also when people file a crash reports 
manually and remember to submit a backtrace, they need to install the 
debug packages manually too, which they often forget or don't know how 
to do. As a result, I still have to ask for them to try again after 
reinstalling debug packages manually a lot.

Nate



On 12/19/21 11:47, Ahmad Samir wrote:
> On 19/12/21 20:26, Antonio Rojas wrote:
>> El domingo, 19 de diciembre de 2021 17:27:52 (CET), Kevin Kofler 
>> escribió:
>>
>>> PS: Those major distributions have had this sorted out for a couple 
>>> years
>>> already. I really do not understand why it is such a problem
>>> for Arch to get
>>> this working. The current situation is a pain for everyone. I cannot
>>> reasonably do any debugging on my PinePhone running Manjaro ARM. Even 
>>> the
>>> limited debugging support in the form of prebuilt rebuilds of GTK and Qt
>>> with debugging information is available only for x86_64.
>>
>> Because, unlike those other "major distributions", Arch infrastructure 
>> and
>> packaging work relies entirely on volunteers in their free time. And the
>> commercially-oriented derivatives that take advantage of this work 
>> (such as
>> the one you mention) do not ever contribute back.
>>
> 
> As usual, "open-source, if you want something done, do it yourself, or 
> send patches."
> 
> Regards,
> Ahmad Samir