Launchpad has imported 15 comments from the remote bug at
https://bugs.kde.org/show_bug.cgi?id=400531.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launc
** Bug watch added: KDE Bug Tracking System #400531
https://bugs.kde.org/show_bug.cgi?id=400531
** Changed in: latte-dock
Importance: Critical => Unknown
** Changed in: latte-dock
Status: Invalid => Unknown
** Changed in: latte-dock
Remote watch: KDE Bug Tracking System #400568 =>
Launchpad has imported 2 comments from the remote bug at
https://bugs.kde.org/show_bug.cgi?id=400568.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launch
0.8.75+git20181023.0746-0~ubuntu18.04~ppa1 is an experimental PPA
package from upstream git, not an official package.
For the record, 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 p
** Bug watch added: KDE Bug Tracking System #400568
https://bugs.kde.org/show_bug.cgi?id=400568
** Also affects: latte-dock via
https://bugs.kde.org/show_bug.cgi?id=400568
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
removing the qmlcache located in ~/.cache/lattedock/qmlcache/
fixed it for me, thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1801290
Title:
Latte dock is not showing on startup and an error m
In many cases, this can be resolved by removing the qmlcache located in
~/.cache/lattedock/qmlcache/
as reported by RiK Mills @
https://launchpad.net/~rikmills/+archive/ubuntu/latte-dock
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I confirm this bug.
It exists in all versions after 0.8.75+git20181023.0746-0~ubuntu18.04~ppa1 (lst
one working correctly) up to 0.8.75+git20181031.1137-0~ubuntu18.04~ppa1
Same software version as above
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub