Re: KDEInit buggy with kcachegrind

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



For kcachegrind, try changing

/usr/share/appilcations/kde4/kcachegrind.desktop

X-DBUS-ServiceName=...
to
X-DBUS-ServiceName=org.kde.kcachegrind

and restart your session (or at least re-run kbuildsycoca5/kbuildsycoca), and see if that helps.  If so, confirms my suspicions

-- Rex
________________________________________
From: Reindl Harald <h.reindl@xxxxxxxxxxxxx>
Sent: Thursday, October 20, 2016 6:01:59 PM
To: kde@xxxxxxxxxxxxxxxxxxxxxxx
Subject: Re: KDEInit buggy with kcachegrind

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
_______________________________________________
kde mailing list -- kde@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to kde-leave@xxxxxxxxxxxxxxxxxxxxxxx




[Index of Archives]     [KDE Users]     [Fedora General Discussion]     [Older Fedora Users Mail]     [Fedora Advisory Board]     [Fedora Security]     [Fedora Maintainers]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Mentors]     [Fedora Package Announce]     [Fedora Package Review]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Triage]     [Coolkey]     [Yum Users]     [Yosemite Forum]     [Fedora Art]     [Fedora Docs]     [Asterisk PBX]

  Powered by Linux