pretty sure not kcachegrind because opening a diff with "kompare" by
double-click in Konqueror has the *identical* behavior talking nonsense
that "KDEinit could not open /usr/bin/kompare" *by close* it leading
here too in open it once again after clkick away that silly popupd
Am 13.10.2016 um 18:45 schrieb Rex Dieter:
Silly phone, make that dbus, not days
-------- Original message --------
From: Rex Dieter <rdieter@xxxxxxx>
Date: 10/13/16 11:43 AM (GMT-06:00)
To: KDE on Fedora discussion <kde@xxxxxxxxxxxxxxxxxxxxxxx>
Subject: RE: KDEInit buggy with kcachegrind
It's usually an application bug in how it interacts with kdeinit/days
(single vs multi instance detection)
-------- Original message --------
From: Reindl Harald <h.reindl@xxxxxxxxxxxxx>
Date: 10/13/16 11:39 AM (GMT-06:00)
To: kde@xxxxxxxxxxxxxxxxxxxxxxx
Subject: Re: KDEInit buggy with kcachegrind
Am 13.10.2016 um 13:57 schrieb Rex Dieter:
Reindl Harald wrote:
not sure how to trigger it with other applications
but when i click on a cachegrind.out file (xdebug analysis) it opens
"kcachegrind" first fine BUT after close it a message "KDEInit could not
start '/usr/bin/kcachegrind'" and when i close that error message it's
opened again
I'm guessing this is simply a kcachegrind error, file a bug?
how can this be a kcachegrind error?
kcachegrind is just fine
the opener (Konqueror) is locked because KDEInit waits for nobody knows
what and after you are done with kcachegrind and close it pretends it
could not be started and to make the fun perfect it starts it again
_______________________________________________
kde mailing list -- kde@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to kde-leave@xxxxxxxxxxxxxxxxxxxxxxx
