Bug 243001

Summary:	Integration with upstream bug trackers (Qt bugs, etc)
Product:	[Websites] bugs.kde.org	Reporter:	David <davidsboogs>
Component:	general	Assignee:	Matt Rogers <mattr>
Status:	RESOLVED INTENTIONAL
Severity:	wishlist	CC:	nate
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Unlisted Binaries
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description David 2010-06-28 09:09:51 UTC

Version:           unspecified
OS:                Linux

Pretty much every crash I experience and attempt to report using the automated reporting tool already exists and is 'a bug in an external application or library' (Resolved External) - which effectively means it is a Qt problem and as such it's basically "wontfix".
In my opinion this is a bad state of affairs - These bugs need to be fixed for KDE to work.  And we basically can't report the 'I'm seeing this' reports that might get them priority. (using drkonqi anyway - and that's most users' limit.) or even see if there is any status or progress.

I propose some integration between the KDE and Qt bug databases: It should be possible to resolve a KDE bug as a dupe of a Qt bug, Perhaps drkonqi should be able to file Qt bugs if the backtrace shows that that's where the failure happened.  I think Qt bugs should be able to be marked as ship blockers.  
At bare minimum it should autolink mentions of Qt bugs in comments or descriptions.
Of course the scope is entirely up for debate - but I do think that this is something which could help the project, at least making crashes less frustrating.


Reproducible: Sometimes

Comment 1 Christoph Feck 2010-06-28 09:55:17 UTC

We have a kdelibs/qt component that you can (re)assign a bug to. Unfortunately, Qt developers clearly stated that they will not look there at all.

Comment 2 Christoph Feck 2010-07-02 16:33:17 UTC

As far as I understand it, Launchpad has it.

It should be possible to move simply move bugs to upstream bugtrackers, at least for freedesktop.org and nokia.com.

Reworded the request accordingly.

Comment 3 Justin Zobel 2021-03-09 05:49:52 UTC

Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.

Comment 4 Nate Graham 2022-09-02 17:14:15 UTC

> which effectively means it is a Qt problem and as such it's basically "wontfix".

That's not an accurate assessment. In my experience the Qt folks fix lots of bugs. I understand that it's frustrating when a Qt bug goes dormant, but no amount of integration between bug trackers is going to change that; it's a developer resourcing issue.

Our upstreams use diverse bug trackers and unfortunately is isn't possible to simply move a bug from one system to another; you have to actually file a new one.