On my experimental system (not used for productive use) I recently switched to KF5/Plasma/KDE5 from the KDE overlay and tried to upgrade as much KDE applications as possible. I also upgrade from KDE PIM 4 to KDE PIM 5 (contact, kmail, kaddressbook, etc.). Unfortunately, drkonqi still depends on kdepimlibs:4 even in version 15.08.2. Hence, drkonqi cannot be co-installed with the KDE PIM suite 5. Occasionally, I experience a crash of the new KDE applications and I would really like to use my experimental system to report those crashes, but I cannot without drkonqi. Right now, the applications crash silently. Previously, I had KDE PIM 4 but kept the rest on Plasma/KDE 5. But this way, I obviously cannot try out KDE PIM 5. To make a long story short: There is a chicken-egg-problem here. I would kindly recommend to migrate drkonqi as soon as possible (at least if already done by upstream), because otherwise it is really difficult to make bug reports for the new system. Reproducible: Always
This is a situation caused by upstream. In fact, you don't need kde-apps/drkonqi:4 at all, just switch off USE=crash-reporter in kde-apps/kdebase-runtime-meta and you're set. For plasma-5, make sure kde-plasma/plasma-workspace-5.4.2 has USE=drkonqi set.
Previously, I had the following setting: kde-plasma/plasma-workspace-5.4.2 +drkonqi kde-apps/kdebase-runtime-meta-15.08.2 +minimal -crash-reporter Previously means before I tried to upgrade to KDE PIM 5. With these settings drkonqi was not triggered when a KDE application crashed. So I (wrongly) assumed that I additionally had to install drkonqi. With drkonqi being installed separately it appeared on screen in case of a crash. Now, I know from comment #1 that this should not be necessary. After I upgraded to KDE PIM 5 I had to unmerge drkonqi, so I am actually back to the same settings as above. If I understand correctly, a crash should trigger drkonqi, because it is implicitly bundled within kde-plasma/plasma-workspace-5.4.2 and enabled by USE flag. But there is no crash handler. My applications crash silently.
It turns out that many applications simply are lacking the ties with kcrash at this point so that they would trigger drkonqi in case of a crash. This is going to improve with 15.12.
As Andreas said, drkonqi not being triggered in KF5-based applications is an upstream issue that at this stage needs to be addressed in each individual application. We can look at moving 15.12 to the main tree soon (which includes some fixed packages).
I upgraded to 15.12. some days ago and DrKonqi still does not show up after a crash. Does the issue still remains unfixed upstream and do I have to wait for a future version or do I miss something?
Depends, each application needs to initialise KCrash independently, and some of these patches have even been backported to 15.12 in Gentoo. So, what crashed and didn't trigger drkonqi?
In my case Kate (kde-apps/kate-15.12.0) and Kontact with KMail plugin being open (kde-apps/kdepim-15.12.0). In case it helps: I have KDE Plasma 5.5, KDE frameworks 5.17 and KDE apps 5.12.
