latte-dock crashes after upgrade to Plasma 5.11.4

[Ales]

After last big update from PPA Latte Dock keeps crashing every time. When started from konsole it says:

KCrash: Attempting to start /usr/bin/latte-dock directly
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = latte-dock path = /usr/bin pid = 6938
KCrash: Arguments: /usr/bin/latte-dock
KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi directly
KCrash: Attempting to start /usr/bin/latte-dock directly

and this repeats until I kill it with killall latte-dock.

Kubuntu 17.10, Linux 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:04:08 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

[Michail Vourlakos (psifidotos.v)]

in case this is a cache issue:

1. close Latte in case it is open
2. remove everything in folder ~/.cache/lattedock/qmlcache
3. start Latte

when is it crashing? on startup or after a specific event?

[Ales (w-ales)]

Deleting cache actually helped. Latte Dock works again.
It crashed every time right on startup.
Thanks a lot!

[David Rando (david-rando)]

Same problem here. Clearing the cache solved the problem. It also solved the issue trying to open de settings dialog with the latest latte-dock update.

[Ales (w-ales)]

Hi again,

today a new update was installed. After upgrade it was impossible to launch Latte Settings. It crashed every time. Deleting files in ~/.cache/lattedock/qmlcache helped. Please consider adding this to the installation script.

cat /var/log/dpkg.log | grep latte-dock
2018-01-27 13:52:52 upgrade latte-dock:amd64 0.7.2-0ubuntu1~ubuntu17.10~ppa3 0.7.3-0ubuntu1~ubuntu17.10~ppa1
2018-01-27 13:52:52 status half-configured latte-dock:amd64 0.7.2-0ubuntu1~ubuntu17.10~ppa3
2018-01-27 13:52:52 status unpacked latte-dock:amd64 0.7.2-0ubuntu1~ubuntu17.10~ppa3
2018-01-27 13:52:52 status half-installed latte-dock:amd64 0.7.2-0ubuntu1~ubuntu17.10~ppa3
2018-01-27 13:52:52 status half-installed latte-dock:amd64 0.7.2-0ubuntu1~ubuntu17.10~ppa3
2018-01-27 13:52:53 status half-installed latte-dock:amd64 0.7.2-0ubuntu1~ubuntu17.10~ppa3
2018-01-27 13:52:54 status unpacked latte-dock:amd64 0.7.3-0ubuntu1~ubuntu17.10~ppa1
2018-01-27 13:52:54 status unpacked latte-dock:amd64 0.7.3-0ubuntu1~ubuntu17.10~ppa1
2018-01-27 13:52:55 configure latte-dock:amd64 0.7.3-0ubuntu1~ubuntu17.10~ppa1 <none>
2018-01-27 13:52:55 status unpacked latte-dock:amd64 0.7.3-0ubuntu1~ubuntu17.10~ppa1
2018-01-27 13:52:55 status half-configured latte-dock:amd64 0.7.3-0ubuntu1~ubuntu17.10~ppa1
2018-01-27 13:52:55 status triggers-awaited latte-dock:amd64 0.7.3-0ubuntu1~ubuntu17.10~ppa1
2018-01-27 13:52:56 status installed latte-dock:amd64 0.7.3-0ubuntu1~ubuntu17.10~ppa1

[Rik Mills (rikmills)]

I'm not going to let a postinst script mess with files in a user's home dir.

Maybe a better solution would be for latte-dock itself to clear it's qml cache when it detects it is being run for the first time after a version upgrade. However, that is an upstream issue for the KDE developer.

[Michail Vourlakos (psifidotos.v)]

I am not sure this is Latte responsibility, it sounds more as a plasma or qt responsibility to keep the cache consistent... Currently, Latte isnt touching the cache in any way...

[Michail Vourlakos (psifidotos.v)]

@rikmills a kubuntu user discovered a Latte crash from the master version because we were using PlasmaComponents3.ComboBox in the settings window... This crash is appearing only with kubuntu distro... the infos can be found here: https://github.com/psifidotos/Latte-Dock/issues/855

the crash is pointing to :

Thread 1 "latte-dock" received signal SIGSEGV, Segmentation fault.
0x00007fff9e7da921 in Kirigami::PlatformTheme::palette() const () from /usr/lib/x86_64-linux-gnu/libKF5Kirigami2.so.5

based on the user versions, is there any incompatibility between qt 5.9.1 and Kirigami2?

[Simon Quigley (tsimonq2)]

Thank you for taking the time to report this bug and helping to make Kubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Kubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Kubuntu version. If you test it and it is still an issue, kindly upload the updated logs by running only once:
apport-collect 1736765

and any other logs that are relevant for this particular issue.