(In reply to Rik Mills from comment #12)
> If the issue is that latte cannot run with a stale qml cache in
> ~/.cache/lattedock/qmlcache/ then this is an upstream KDE issue that cannot
> be addressed in distro packaging. We can't and shouldn't act on any file in
> a user home when doing a package upgrade via sudo/admin. This should be
> fixed by KDE by having latte detect that it is being run for the first time
> by a user after a version upgrade, and at that point removing or modifying
> the cache with that user's privileges.
if you have any idea how to do that in Latte, feel free to send a patch,
my important question of course is why this is not needed from plasmashell
(In reply to Rik Mills from comment #12) lattedock/ qmlcache/ then this is an upstream KDE issue that cannot
> If the issue is that latte cannot run with a stale qml cache in
> ~/.cache/
> be addressed in distro packaging. We can't and shouldn't act on any file in
> a user home when doing a package upgrade via sudo/admin. This should be
> fixed by KDE by having latte detect that it is being run for the first time
> by a user after a version upgrade, and at that point removing or modifying
> the cache with that user's privileges.
if you have any idea how to do that in Latte, feel free to send a patch,
my important question of course is why this is not needed from plasmashell