"You cannot report this error, because krunner does not provide a bug reporting address." It does under the Plasma umbrella however. Reproducible: Always Steps to Reproduce: 1. krunner crashes 2. Unable to submit bug report to Plasma developers 3. Actual Results: Unable to submit bug report to Plasma developers Expected Results: Able to submit bug to Plasma developers
Also a problem with Plasma 5.3.2 on OpenSUSE Tumbleweed
I'm guessing that this is the same bug. Was performing a large update (mostly KDE frameworks/ plasma stuff) in Fedora 22 and drkonqi pops up with the following:- "We are sorry, kded5 (deleted) closed unexpectedly You cannot report this error, because kded5 (deleted) does not provide a bug reporting address Details: Executable: kded5 (deleted) PID: 2016 Signal: Aborted (6) Time: 24/10/2015 20:34:56" Developer info: "Application: kded5 (deleted) (kded5 (deleted)), signal: Aborted [Current thread is 1 (LWP 2016)] Thread 1 (LWP 2016): #0 0x8f2c8a5d in ?? () Backtrace stopped: Cannot access memory at address 0xab83c10"
Just had this again. This time trying to search for an app in the kmenu. Application: plasmashell (deleted) (5.4.1) Qt Version: 5.5.0 Operating System: Linux 4.2.3-200.fc22.x86_64 x86_64 Distribution: "Fedora release 22 (Twenty Two)" -- Information about the crash: I was searching for an app using the kemenu -- Backtrace: A useful backtrace could not be generated Report to https://bugs.kde.org/
Yeah, what happens is that there are crashes after an update and then drkonqi fails to trace the crash because the binary that crashed has since been deleted (i.e. replaced by the update). This probably needs catching somewhere. Although I am not quite sure where.
Drkonqi will fairly reliably detect applied updates and refuse to report bug reports against software started prior to the update. Starting with Plasma 5.18.