LatteDock/HowToReportCrashes/en: Difference between revisions

From KDE Wiki Sandbox
(Importing a new version from external source)
(Importing a new version from external source)
Line 15: Line 15:
* <code>ddd latte-dock</code>
* <code>ddd latte-dock</code>


* In 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 it crashes, click <menuchoice>Status</menuchoice> from the menu, <menuchoice>Backtrace</menuchoice>
* When it crashes, click <menuchoice>Status</menuchoice> from the menu, <menuchoice>Backtrace</menuchoice>

Revision as of 05:00, 11 April 2019

←Latte Dock

First try to clean your Qt cache, #788, kubuntu bug 1736765:

  1. Close Latte
  2. Delete everything from the folder ~/.cache/lattedock/qmlcache/
  3. Start Latte again

Use the following guidelines:

  • Install ddd
  • ddd latte-dock
  • Inside the text field on the lower side of the 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 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
    that should provide more information if the debug packages are installed

Which 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:

  1. Use Latte only with default Layout (does it crash?)
  2. If it doesnt crash start adding one by one your plasmoids 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