LatteDock/HowToReportCrashes: Difference between revisions

Latest revision as of 09:54, 28 November 2021

Other languages:

English
українська

←Latte Dock

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 Status in the menu and select Backtrace

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

@@ Line 1: / Line 1: @@
-<languages>
+<languages />
 <translate>
-[[LatteDock|←Latte Dock]]
+[[File:LLoXdgK.png|right|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]:
+<!--T:1-->
+[[Special:mYLanguage/LatteDock|←Latte Dock]]
-# Close Latte
+<!--T:2-->
-# In folder {{Path|1=~/.cache/lattedock/qmlcache/}} remove everything
+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]:
+<!--T:3-->
+# Close Latte</translate>
+<translate>
+<!--T:17-->
+# Delete everything from the folder {{Path|1=~/.cache/lattedock/qmlcache/}} </translate>
+<translate>
+<!--T:18-->
 # Start Latte again
+<!--T:4-->
 Use the following guidelines:
+<!--T:5-->
 * Install ''ddd''
-* <code>ddd latte-dock</code>
-* In ddd window write and execute, <code>run</code>
-* When it crashes, click <menuchoice>Status</menuchoice> from the menu, <menuchoice>Backtrace</menuchoice>
-* 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:
+<!--T:6-->
+* Run <code>ddd latte-dock</code>
+<!--T:7-->
+* Inside the text field on the lower side of the ddd window, write and execute <code>run</code>
+<!--T:8-->
+* When Latte crashes, click <menuchoice>Status</menuchoice> in the menu and select <menuchoice>Backtrace</menuchoice>
+<!--T:9-->
+* This will show you a window with numbered lines that can be helpful for the development team to find the issue.
+<!--T:10-->
+If the crash originates from QML, you should try the following:
+<!--T:11-->
+* Run the following command: {{Input|1=env QV4_FORCE_INTERPRETER=1 latte-dock -d}}
+<!--T:12-->
+* If the above does not provide enough info, you could try: {{Input|1=env QV4_FORCE_INTERPRETER=1 ddd --debugger /bin/gdb latte-dock}}
-- Run command: {{Input|1=env QV4_FORCE_INTERPRETER=1 latte-dock -d}}
+<!--T:20-->
-- If the above does not provide enough info you could try: {{Input|1=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:
+<!--T:13-->
+If nothing mentioned above succeeds, you could try to check if the crash is related to a specific plasmoid:
-# Use Latte only with default Layout (does it crash?)
+<!--T:14-->
-# If it doesnt crash start adding one by one your plasmoids to check their behavior and if they crash Latte...
+# Use Latte with default Layout (does it crash?)</translate>
+<translate>
+<!--T:19-->
+# If it doesn't crash, start adding your plasmoids one by one in order 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...
+<!--T:15-->
+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...
+<!--T:21-->
+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.
+<!--T:22-->
+Any good backtrace is much appreciated! Please report such issues at https://bugs.kde.org/describecomponents.cgi?product=lattedock
+<!--T:16-->
 [[Category:Desktop]]
 [[Category:Plasma]]
 </translate>