Bug 483610 - Application launcher order reset after restart
Summary: Application launcher order reset after restart
Status: REOPENED
Alias: None
Product: krunner
Classification: Plasma
Component: general (show other bugs)
Version: 6.1.1
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords: qt6
Depends on:
Blocks:
 
Reported: 2024-03-14 22:01 UTC by Alexander Stehlik
Modified: 2024-07-22 18:49 UTC (History)
6 users (show)

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


Attachments
Screenshot of Kickoff with initial search and after restart (104.89 KB, image/png)
2024-03-14 22:01 UTC, Alexander Stehlik
Details
Screenshot of Kickoff after first selection with expected order (105.95 KB, image/png)
2024-03-14 22:02 UTC, Alexander Stehlik
Details
Screenshot of Kickoff with initial search and after restart (64.28 KB, image/png)
2024-03-14 22:12 UTC, Alexander Stehlik
Details
Screenshot of Kickoff after first selection with expected order (66.74 KB, image/png)
2024-03-14 22:12 UTC, Alexander Stehlik
Details
Krunner with correct ordering in applications group (23.88 KB, image/png)
2024-06-27 07:23 UTC, Alexander Stehlik
Details
Kickoff with wrong ordering in applications group after Plasma Shell restart (25.78 KB, image/png)
2024-06-27 07:24 UTC, Alexander Stehlik
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Stehlik 2024-03-14 22:01:41 UTC
Created attachment 167208 [details]
Screenshot of Kickoff with initial search and after restart

SUMMARY

The order / sorting based on recent selections in the Kickoff application launcher is lost when plasmashell is restarted.

This does not happen in KRunner.


STEPS TO REPRODUCE
1. Search for an application e.g. "term"
2. You see several results (XTerm, UXTerm, Konsole, ...)
3. Select Konsole and press ENTER
4. Repeat search for "term"
5. Konsole is now displayed on top
6. Restart Plasmashell (systemctl restart --user plasma-plasmashell.service)
7. Repeat search for "term

OBSERVED RESULT

Konsole is no longer displayed on top (order is reset to the state before Konsole was selected / started).

EXPECTED RESULT

Konsole is displayed on top as before the restart.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: EndeavourOS
(available in About System)
KDE Plasma Version: 6.0.2
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2

ADDITIONAL INFORMATION
Comment 1 Alexander Stehlik 2024-03-14 22:02:19 UTC
Created attachment 167209 [details]
Screenshot of Kickoff after first selection with expected order
Comment 2 Alexander Stehlik 2024-03-14 22:12:19 UTC
Created attachment 167210 [details]
Screenshot of Kickoff with initial search and after restart
Comment 3 Alexander Stehlik 2024-03-14 22:12:46 UTC
Created attachment 167211 [details]
Screenshot of Kickoff after first selection with expected order
Comment 4 Nick 2024-03-21 20:26:25 UTC
I can duplicate this on my full updated Neon installation. Easy to duplicate every time. I just had to install xterm to give me the additional option to test with as per the original bug description. Hoping a dev can take a further look at this.
Comment 5 Nate Graham 2024-04-11 21:09:05 UTC
After you reproduce this in Kickoff, does KRunner show the exact same search ordering? Or is it different there?
Comment 6 Alexander Stehlik 2024-06-23 19:42:18 UTC
The ordering of the search results in Kickoff and KRunner seem to be independent from each other.

In the described example I have to open Konsole in both of them one time to make it appear as the first entry.
Comment 7 Nate Graham 2024-06-26 19:19:13 UTC
The ordering should be identical, but I think it seems like favorites runners aren't always sorted to the top in Kickoff the way they are in KRunner. Can you confirm that?
Comment 8 Alexander Stehlik 2024-06-26 20:01:38 UTC
The ordering logic seems to be identical for Kickoff and KRunner. But they seem to use different data sources.

Example: I open KRunner and type "Fire" and select "Firefox" which comes AFTER "Firewall" the first time. When I open KRunner again and type "Fire", "Firefox" will be the first entry. At the same time when I now open Kickoff and type "Fire", then "Firewall" will still be the first entry until I select "Firefox" there also.

I have no idea where KRunner is storing its ordering. I was not able to reset it. I tried to reset the history in the settings but this had no effect. "Firefox" is always the first entry there.
Comment 9 Nate Graham 2024-06-26 22:18:08 UTC
The items should be ordered the same *within* groups, but I'm seeing that the order of groups themselves is different between the two.

Are you seeing that as well, or are you seeing the items in the groups being different or being ordered differently?
Comment 10 Alexander Stehlik 2024-06-27 07:23:39 UTC
Created attachment 171066 [details]
Krunner with correct ordering in applications group
Comment 11 Alexander Stehlik 2024-06-27 07:24:51 UTC
Created attachment 171067 [details]
Kickoff with wrong ordering in applications group after Plasma Shell restart
Comment 12 Alexander Stehlik 2024-06-27 07:26:13 UTC
The ordering is wrong within the "applications" group.

I added two more screenshots to clarify what I'm seeing.
Comment 13 Nate Graham 2024-06-27 16:20:01 UTC
Interesting. I can't reproduce that issue myself.

...Oh, you're still on Plasma 6.0. Right. This was fixed in 6.1.
Comment 14 Alexander Stehlik 2024-06-27 18:55:18 UTC
Hmm, no, I'm already on 6.1 and still experiencing the issue:

KDE Plasma Version: 6.1.0
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.2
Kernel Version: 6.9.6-arch1-1 (64-bit)
Graphics Platform: Wayland
Comment 15 Alexander Stehlik 2024-06-27 19:00:34 UTC
I just updated to 6.1.1 and the problem is still there.
Comment 16 Alexander Stehlik 2024-06-28 09:28:30 UTC
I did some more research and found out that there was an entry in .local/share/krunnerstaterc that looked like this:

[PlasmaRunnerManager]
LaunchCounts=94 exec:///usr/bin/google-chrome-stable,10 exec:///usr/bin/virt-manager

After I deleted the file and restarted krunner it now also looses its ordering after a restart. The LaunchCounts entry does not re-appear in the file.