LatteDock/HowToReportCrashes/uk: Difference between revisions
(Created page with "# Вилучіть усі файли з теки {{Path|1=~/.cache/lattedock/qmlcache/}}") |
(Created page with "# Знову запустіть Латте") |
||
| Line 7: | Line 7: | ||
# Закрийте Латте | # Закрийте Латте | ||
# Вилучіть усі файли з теки {{Path|1=~/.cache/lattedock/qmlcache/}} | # Вилучіть усі файли з теки {{Path|1=~/.cache/lattedock/qmlcache/}} | ||
# | # Знову запустіть Латте | ||
Use the following guidelines: | Use the following guidelines: | ||
Revision as of 21:25, 18 March 2019
Спочатку спробуйте спорожнити ваш кеш Qt, #788, вада у kubuntu 1736765:
- Закрийте Латте
- Вилучіть усі файли з теки ~/.cache/lattedock/qmlcache/
- Знову запустіть Латте
Use the following guidelines:
- Встановіть ddd
ddd latte-dock
- In ddd window write and execute,
run
- When it crashes, click from the menu,
- This will show you a window with numbered lines that could be helpful for us...
If the crash is from QML you should try the following:
- Віддайте команду
env QV4_FORCE_INTERPRETER=1 latte-dock -d
- If the above does not provide enough info you could try:
env QV4_FORCE_INTERPRETER=1 ddd --debugger /bin/gdb latte-dock
that should provide more information if the debug packages are installed
If nothing from the above succeeds you could try to check if the crash is related to specific plasmoid:
- Use Latte only with default Layout (does it crash?)
- If it doesnt crash start adding one by one your plasmoids to check their behavior and if they crash Latte...
If anyone knows that during the day Latte will crash, he can use the previous suggestions to give us a meaningful backtrace... For 95% of the cases that backtrace can help us identify if the crash is in our side...