LatteDock/HowToReportCrashes/en: Difference between revisions
(Importing a new version from external source) |
(Importing a new version from external source) |
||
| (5 intermediate revisions by the same user not shown) | |||
| Line 13: | Line 13: | ||
* Install ''ddd'' | * Install ''ddd'' | ||
* <code>ddd latte-dock</code> | * Run <code>ddd latte-dock</code> | ||
* Inside the text field on the lower side of the ddd window, write and execute <code>run</code> | * Inside the text field on the lower side of the ddd window, write and execute <code>run</code> | ||
* When | * When Latte crashes, click <menuchoice>Status</menuchoice> in the menu and select <menuchoice>Backtrace</menuchoice> | ||
* This will show you a window with numbered lines that | * This will show you a window with numbered lines that can be helpful for the development team to find the issue. | ||
If the crash originates from QML, you should try the following: | If the crash originates from QML, you should try the following: | ||
| Line 25: | Line 25: | ||
* Run the following command: {{Input|1=env QV4_FORCE_INTERPRETER=1 latte-dock -d}} | * Run the following command: {{Input|1=env QV4_FORCE_INTERPRETER=1 latte-dock -d}} | ||
* If the above does not provide enough info you could try: {{Input|1=env QV4_FORCE_INTERPRETER=1 ddd --debugger /bin/gdb latte-dock}} | * If the above does not provide enough info, you could try: {{Input|1=env QV4_FORCE_INTERPRETER=1 ddd --debugger /bin/gdb latte-dock}} | ||
Which should provide more information if the debug packages are installed. | Which should provide more information if the debug packages are installed. | ||
If nothing | If nothing mentioned above succeeds, you could try to check if the crash is related to a specific plasmoid: | ||
# Use Latte with default Layout (does it crash?) | # Use Latte with default Layout (does it crash?) | ||
# If it | # If it doesn't crash, start adding your plasmoids one by one in order to check their behavior and if they crash Latte. | ||
-------- | -------- | ||
Latest revision as of 05:00, 11 April 2019
First try to clean your Qt cache, #788, kubuntu bug 1736765:
- Close Latte
- Delete everything from the folder ~/.cache/lattedock/qmlcache/
- Start Latte again
Use the following guidelines:
- Install ddd
- Run
ddd latte-dock
- Inside the text field on the lower side of the ddd window, write and execute
run
- When Latte crashes, click in the menu and select
- This will show you a window with numbered lines that can be helpful for the development team to find the issue.
If the crash originates from QML, you should try the following:
- Run the following 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
Which should provide more information if the debug packages are installed.
If nothing mentioned above succeeds, you could try to check if the crash is related to a specific plasmoid:
- Use Latte with default Layout (does it crash?)
- If it doesn't crash, start adding your plasmoids one by one in order to check their behavior and if they crash Latte.
If it is expected that Latte will eventually crash throughout the day due to the unresolved issue, the user can use the previous suggestions to provide a meaningful backtrace...
For 95% of the cases, this backtrace can help the development team identify if the crash is a Latte-Dock issue and not caused from upstream.
Any good backtrace is much appreciated! Please report such issues at https://bugs.kde.org/describecomponents.cgi?product=lattedock