bruns added a comment.
There are two possible ways of changing the caching, and each one will break
behavior for one of two different groups of users:
1. People who rely on the krunner following the default profile.
2. People who rely on krunner using the dbfile config entry.
I would argue for just removing the `grp.writeEntry("dbfile", m_dbFile)`
line. This keeps the current behavior for the second group, and still solves
the problem for the first group when there is no config yet. Only users of the
second group with an existing config have to do a one-time change to their
config, e.g. resetting/removing the "dbfile" config value.
REPOSITORY
R120 Plasma Workspace
REVISION DETAIL
https://phabricator.kde.org/D28619
To: alex, #plasma, bruns, broulik
Cc: plasma-devel, Orage, LeGast00n, The-Feren-OS-Dev, cblack, jraleigh, zachus,
fbampaloukas, GB_2, ragreen, ZrenBot, ngraham, himcesjf, lesliezhai,
ali-mohamed, jensreuterberg, abetts, sebas, apol, ahiemstra, mart
