It’s the same app.
2 Likes
@ngraham, does it merely provide analytics, like ABRT Analytics - Problem #670019 - tracker-miners in readdir64? If not, what’s it for? (I should probably have just asked that first.)
It provides automatic crash reporting (if you opt in) to our Sentry instance, which tracks automatically-reported crashes.
1 Like
Thank you, @ngraham.
1 Like
I’ve noticed, as 437675 – Crash after selecting effect in Kamoso. demonstrates
I was able to reproduce [the crash] a moment ago, and submitted it via Is the Crash Handler separate to DrKonqi? - #4 by ngraham, but I don’t have access to Sign In | Sentry, so I can’t correlate them here.
that crashes which it’s invoked for don’t appear to be recorded by DrKonqi like most other crashes:
Is this deliberate? If so, might I know the rationale?
For the obvious reason: because it would be redundant to track the same crash in two places, in two systems.
1 Like
@ngraham, indeed.
Like I’ve touched on in Is the Crash Handler separate to DrKonqi? - #3 by rokejulianlockhart, and as I expect you’re aware, when reporting a bug on Fedora 40 (via the included-by-default GNOME ABRT client) to RedHat’s Bugzilla instance, like 2273737 – [abrt] plasma-systemmonitor: QHashPrivate::iterator<QHashPrivate::Node<QModelIndex, QSortFilterProxyModelPrivate::Mapping*> >::node(): plasma-systemmonitor killed by SIGSEGV, it includes a URI to the corresponding analytics contribution. In the case of the referenced bug, that would be https://retrace.fedoraproject.org/faf/reports/bthash/e99887b973d6527529f5b898bbff2e7d2096e0c.
DrKonqi doesn’t do this - when a report is submitted via the window we’re discussing, the report isn’t visible to the user anymore. In the case that I’ve mentioned earlier about my very old bug report for Kamoso, that’s somewhat problematic, because I can’t access that backtrace anymore (your Sentry instance is private).
Am I going about this incorrectly?
Yes, the sentry instance is private.
Yeah. So are the traces retained locally? That’s the crux of the problem. If they’re not, it’s difficult to provide useful info when filing a bug.
I don’t seem to ever see DrKonqi anymore; just:
I’ve written this Ask Ubuntu answer responding to a question about DrKonqi, and have needed to state:
As Is the Crash Handler separate to DrKonqi? - #10 by rokejulianlockhart explains, it appears to me that DrKonqi has largely been replaced by the opaque Crash Handler, so this [Crashed Processes Viewer] may be the new official KDE way to acquire stack traces.
Consequently, I would like confirmation that Konqi is gone if it is, so that I don’t accidentally put it in recommendations if it’s been deprecated.