On 08.09.24 3:25 PM, Nicolas Fella via Development wrote:
Hi,

at Akademy I had a chat with Volker Hilsheimer and now want to open this
to a wider audience.

In KDE we have an automatic crash reporting system based on Sentry.
Naturally some amount of the crash reports point to the problem being in
Qt instead of in KDE code. In those cases we of course want to create
useful Qt bugreports for you. Unfortunately it is not always easy for us
to narrow down or reproduce the problem so a lot of issues are never
reported to you, even if they could be potentially interesting to you.

Now I am wondering how we can improve the communication pipeline in that
regard and make sure you Qt people are aware of the reports we get and
can give your input on it. I see a few possible ways to go about this,
which aren't necessarily mutually exclusive:

- We report every Qt-related-looking crash we get as a QTBUG, even if we
don't have a reproducer or much information on what's going on

- Someone from KDE writes a weekly(?)/monthly(?) summary email with
relevant looking reports that we would like someone from Qt to look at

- We give some Qt people access to our crash reporting system directly

Let me know what you think about this

Hi,

we now have the infrastructure in place to give Qt developers direct
access to our sentry. Tor Arne already has access and we can extend it
to more people.

To get access you need a KDE account (https://identity.kde.org/). Then
either drop me or our sysadmins (sysad...@kde.org) an email saying you
are a Qt developer and would like access and give your KDE account
username. Once you are in Sentry you'll want to join the "KDE" organization.

Something worth mentioning: We only started using Sentry in Qt 6/Plasma
6 times and only added the Qt version to the crash metadata somewhat
recently. Therefore it's unlikely to see Qt versions before 6.7.2 in the
crash reports, but that doesn't mean there are no crashes.

Cheers

Nico

--
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Reply via email to