Bug 498873 - Some search providers e.g. ecosia) don't work as Default Web search Keyword for fallback web search results in KRunner searches
Summary: Some search providers e.g. ecosia) don't work as Default Web search Keyword f...
Status: CONFIRMED
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_webshortcuts (show other bugs)
Version: 6.2.5
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-01-19 03:49 UTC by Jared Adams
Modified: 2025-01-28 16:42 UTC (History)
2 users (show)

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


Attachments
Screen recording showing issue (420.40 KB, video/webm)
2025-01-27 01:59 UTC, Jared Adams
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jared Adams 2025-01-19 03:49:59 UTC
Several searches don't work as the Default Web search Keyword. No results show when they're configured as the default while the others show the expected launch option.

Steps to Reproduce
1. "search tree1" saved search text
2. Open Web Search KCM
3. Change Default Web search Keyword
4. Click Apply
5. Open KRunner with Meta+F2

Switch to a broken provider and there are no results. Switch to a working provider and results show.

I haven't tested every included search provider. Ones that don't work for me include:
Ecosia
Duck Duck Go Info
Duck Duck Go Shopping
All Google searches except the plain Google
Microsoft C++ Documentation

Tested broken providers work with explicit keyword (example: "ec: tree1").

Reddit thread: https://www.reddit.com/r/kde/comments/1i4b05n/krunner_ecosia_search_not_working/

Operating System: CachyOS Linux 
KDE Plasma Version: 6.2.5
KDE Frameworks Version: 6.10.0
Qt Version: 6.8.1
Kernel Version: 6.12.9-3-cachyos (64-bit)
Comment 1 Nate Graham 2025-01-21 22:59:39 UTC
This is working fine for me. Can you attach a screen recording that shows you reproducing the issue?
Comment 2 Jared Adams 2025-01-27 01:59:51 UTC
Created attachment 177702 [details]
Screen recording showing issue

Here's a recording showing "search tree1" not working with one default keyword, but working with another, with both keyword searches tried too.
Comment 3 Nate Graham 2025-01-27 17:52:00 UTC
Where does the word "search" come from? How did you settle on that as a word to use here?
Comment 4 Jared Adams 2025-01-27 18:00:23 UTC
(In reply to Nate Graham from comment #3)
> Where does the word "search" come from? How did you settle on that as a word
> to use here?

I'm not sure why I was using that, but it doesn't matter. Just "tree1" works for Duck Duck Go, but I get no results when Duck Duck Go Info is the default keyword search.
Comment 5 Nate Graham 2025-01-28 00:37:04 UTC
The UI here is rather confusing; setting something as the default web search keyword, as far as I can tell, doesn't make a difference for KRunner; you always need to use the keyword of the search provider you want to use. What it does affect is the first item in the "Search for [text] with" menu items in various KDE apps. For example if you select some text in Okular and right-click it, you'll see that menu item at the bottom, and in its sub-menu, the default web search provider will be on top.

Let's focus on the providers that are broken even when invoking them with their keywords. Can you gather a list of them?
Comment 6 Jared Adams 2025-01-28 00:52:40 UTC
As far as I'm aware, they all work fine. The behavior I'm seeing for KRunner (and others using Plasma Search) is for the Web Search Keywords plugin to be invoked with the configured default keyword for all queries that don't have any other results, as a fallback. Except it only works for some search providers.
Comment 7 Nate Graham 2025-01-28 16:40:26 UTC
> the Web Search Keywords plugin to be invoked with the configured default keyword for all queries that don't have any other results, as a fallback

Does this actually work at all? I don't think I've seen it working.
Comment 8 Nate Graham 2025-01-28 16:42:29 UTC
Oh my goodness, the fact that I've never seen it working is an example of the very bug you're reporting, which is why I'm confused here.

I can clearly reproduce the bug by entering "foooooooooooooooooooooooooooo" into KRunner. With DuckDuckGo as the default web search keyword, I see an item prompting me to do a web search for that term. With Ecosia, I don't.