Bug 489105

Summary: Need new category for Plasma 6 KRunner plugins, so they aren't mixed with the Plasma 5 ones.
Product: [Plasma] krunner Reporter: player one <nigvul>
Component: generalAssignee: Plasma Bugs List <plasma-bugs-null>
Status: CONFIRMED ---    
Severity: normal CC: alexander.lohnau, justin, natalie_clarius, nate, notmart
Priority: NOR    
Version First Reported In: 6.1.0   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description player one 2024-06-24 13:32:22 UTC 
SUMMARY
No one third-party plugin for krunner does not work. I assume this is due to the transition to plasma 6. I tried to install all third-party plugins, but not one, except for the built-in ones, did not work or did not install.

STEPS TO REPRODUCE
1. Open krunner
2. Open krunner settings
3. Download new plugins
4. Try install any plugins or try use any plugins

OBSERVED RESULT
No one third-party plugin for krunner does not work. Error during installation, error during plugin launch

EXPECTED RESULT
1. Documentation on creating plugins for plasma 6.x
2. Remove broken plugins on plasma 6.x
3. Please, fix the mechanism for creating plugins and how they work.

How I see the work of third-party plugins. 

Press create plugin
Enter action keywords: ob
Enter Custom command: python get_notes.py

Mechanism of operation: 
1. User input action keyword: obs
2. Krunner starts custom command 
3. The script performs the action and returns a list, separated by \n 
4. We see the list in Krunner 
5. We select one line 
6. The result is returned in the custom script 
7. Processing the selected

A simpler mechanism:
when calling "krunner --options "1. Option \n 2. Option\n 3. Option" 
fills the krunner with options for subsequent selection and returns the value when an option is selected. Thus, the mechanism of operation can be implemented in any language, as long as it is done unnoticeably to the user. The user enters action keyword, which runs a script and krunner displays all the results and returns them to the script. (like rofi, but better)

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora Linux 40 (KDE Spins)
KDE Plasma Version: 6.1.0
KDE Frameworks Version: 6.3.- 
Qt Version: 6.7.1
Comment 1 Marco Martin 2024-06-25 11:40:11 UTC 
hm, it looks like this one a swell needs a separed store category
Comment 2 player one 2024-06-25 12:47:23 UTC 
(In reply to Marco Martin from comment #1)
> hm, it looks like this one a swell needs a separed store category

There is already a separate one for widgets, why not do it for krunner. We see a widget suitable for plasma 6. I suggest that it has already been implemented.
Comment 3 player one 2024-06-25 12:49:41 UTC 
(In reply to Marco Martin from comment #1)
> hm, it looks like this one a swell needs a separed store category

A separate store is not the main thing. The main thing is the working mechanism of plugins.
Comment 4 Nate Graham 2024-06-25 14:07:08 UTC 
Marco is saying we need a separate category for "Plasma 6 KRunner plugins" so you aren't shown plugins for Plasma 5 that will not work.

Justin, can you create the category on the server so we can do the necessary work in the client?
Comment 5 Alexander Lohnau 2024-06-26 21:25:04 UTC 
Hmm, thought DBus runners should be compatible. Unless the maintainers ignored deprecation warnings for 3 years.
Comment 6 Alexander Lohnau 2024-06-26 21:25:59 UTC 
Maybe one should not enforce a category, but specific tags. Like plasma5 and plasma6. In case of runners that I have on the store, most are compatible with both major versions.
Comment 7 Nate Graham 2024-06-26 22:29:12 UTC 
Qt 6 stuff can't load plugins built with Qt5, even if all the API calls would otherwise be compatible.
Comment 8 Justin Zobel 2024-09-03 01:02:00 UTC 
I believe this is all done now, no more categories are required?
Comment 9 Nate Graham 2024-09-03 04:30:48 UTC 
From what I can tell, there is still only one: https://store.kde.org/browse?cat=628