LatteDock/HowToReportCrashes: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
[[LatteDock|←Latte Dock]] | |||
First try to clean your qt cache, [https://github.com/psifidotos/Latte-Dock/issues/788 #788], [https://bugs.launchpad.net/kubuntu-ppa/+bug/1736765 kubuntu bug 1736765]: | First try to clean your qt cache, [https://github.com/psifidotos/Latte-Dock/issues/788 #788], [https://bugs.launchpad.net/kubuntu-ppa/+bug/1736765 kubuntu bug 1736765]: | ||
Revision as of 16:03, 8 March 2019
First try to clean your qt cache, #788, kubuntu bug 1736765:
- 'Close Latte'
- 'In folder' `~/.cache/lattedock/qmlcache/` 'remove everything'
- 'Start Latte again'
Use the following guidelines:
- Install `ddd`
- `ddd latte-dock`
- in ddd window write and execute, `run`
- when it crashes, click `Status` from the menu, `Backtrace`
- 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:
- run command: `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...