… do not forget to properly setup KAboutData !

DrKonqi, the KDE crash handler dialog and report assistant, is prepared to send crash reports to our bugtracker at bugs.kde.org.

However, there are KDE based applications that are not developed by the official KDE team or that use their own bugtracker. In those cases, you need to tell DrKonqi about this custom reporting address (which could be a site or a contact email). If you don’t do so, that kind of reports are going to end up being sent to bugs.kde.org and closed as DOWNSTREAM, usually causing more trouble for the reporting user (and increasing the work of the KDE bug triagers)

There are two ways to tell KAboutData (and therefore DrKonqi) about your custom tracker:

On the KAboutData constructor:

The 10th argument of the KAboutData constructor allows the developer to set a custom bug reporting address entry (URL or email), in QByteArray format

The 10th argument of the KAboutData constructor allows the developer to set a custom bug reporting address entry (URL or email), in QByteArray format Using the setBugAddress function:

Once the KAboutData object is created, and before calling KCmdLineArgs::init() (and/or before creating the KApplication object), you can call aboutData.setBugAddress("URL");

You can always check the KAboutData API

Thanks!