Bug 358453 - org.kde.kfind is found although it is not installed
Summary: org.kde.kfind is found although it is not installed
Status: RESOLVED WORKSFORME
Alias: None
Product: frameworks-kservice
Classification: Frameworks and Libraries
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Other Linux
: NOR minor
Target Milestone: ---
Assignee: David Faure
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-01-23 20:49 UTC by Gregor Mi
Modified: 2021-09-24 04:35 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gregor Mi 2016-01-23 20:49:08 UTC
In kservicefactory.cpp there is the method KService::Ptr KServiceFactory::findServiceByDesktopName(const QString &_name) that I added with some debug code:

KService::Ptr KServiceFactory::findServiceByDesktopName(const QString &_name)
{
    qDebug() << "### KServiceFactory::findServiceByDesktopName:  " << _name;

    if (!m_nameDict) {
        qDebug() << "#### error";
        return KService::Ptr();    // Error!
    }

    // Warning : this assumes we're NOT building a database
    // KBuildServiceFactory reimplements it for the case where we are building one

    int offset = m_nameDict->find_string(_name);
    if (!offset) {
        return KService::Ptr();    // Not found
    }

    qDebug() << "#### createEntry";
    KService::Ptr newService(createEntry(offset));

    // Check whether the dictionary was right.
    if (newService && (newService->desktopEntryName() != _name)) {
        // No it wasn't...
        return KService::Ptr();
    }

    qDebug() << "#### newService";
    return newService;
}

If _name is "org.kde.kfind" then "#### newService" is reached but kfind is not installed. What can be done?
Comment 1 Gregor Mi 2016-01-23 20:54:10 UTC
When I try to launch this service, this is the error message:

KDEInit could not launch 'kfind':
Could not open library '/usr/lib64/libkdeinit5_kfind'.
Cannot load library /usr/lib64/libkdeinit5_kfind: (/usr/lib64/libkdeinit5_kfind.so: Kann die Shared-Object-Datei nicht öffnen: Datei oder Verzeichnis nicht gefunden)

I already did a kbuildsycoca5.
Comment 2 Gregor Mi 2016-01-23 21:05:02 UTC
I found out the following:

1) KService picks up the the kfind desktop file that was installed in my KF5 dev env: dolphin(21680)/default KMoreTools::registerServiceByDesktopEntryName: installedService->entryPath() "/z_root_space/gregor/kde-usr/share/applications/org.kde.kfind.desktop"

which I think is fine because I start the program (in this case dolphin) in the KF5 dev env.

2) With `dev-kf5-run kfind` kfind runs fine (where dev-kf5-run is the script that sets up the dev env variable)

So, I wonder what is the problem with KDEInit?
Comment 3 Gregor Mi 2016-09-06 12:44:39 UTC
I still wonder why KDEInit does not find the master version of KFind which is installed in the KDE development /usr directory. Maybe close this issue because a normal user would not be affected?
Comment 4 Ahmad Samir 2021-08-25 21:55:23 UTC
Is this still an issue?
Comment 5 Bug Janitor Service 2021-09-09 04:36:05 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Bug Janitor Service 2021-09-24 04:35:40 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!