Hey friends!

Basically, here is my problem. I open the launcher menu (or KRunner) and start typing. Let’s say I type “firefox”, and hit Enter.

The launcher menu is very slow. It often opens “Files” instead, because that pops up after I type the first two letters.

Basically this means I need to wait a second for the launcher to finish searching, show me firefox, and then press enter.

This is frankly infuriating. Every other launcher on any other desktop or WM does not have this issue.

I have experienced this on two different machines running both Plasma 5 and 6, on different distros, both are beefy machines.

I’m sure there is a way to avoid it, does anybody know?

  • boredsquirrel@slrpnk.net
    link
    fedilink
    arrow-up
    2
    ·
    6 months ago

    The new cache-to-RAM improvements in Plasma 6.1 will help a lot.

    Then, for plasma search, you can configure the placement of the results in systemsettings. This is also Plasma 6 only afaik

    • PotatoesFallOP
      link
      fedilink
      arrow-up
      2
      ·
      edit-2
      6 months ago

      I don’t actually care about speed to be honest, more the correctness. Should have phrased my question differently oops

        • PotatoesFallOP
          link
          fedilink
          arrow-up
          3
          ·
          6 months ago

          Well if I type “discord” then “discover” is an incorrect result, imo.

          • boredsquirrel@slrpnk.net
            link
            fedilink
            arrow-up
            2
            ·
            6 months ago

            Is this an actual example?

            Here the search is so quick, that on “dis” is already has results. But then the delay to search again is too high.

            • PotatoesFallOP
              link
              fedilink
              arrow-up
              1
              ·
              6 months ago

              Yes, actual example.

              I followed the advice of another user and disabled some of the search options and its super fast now and should probably fix my issue. I still went ahead and reported this as a bug though