Difference between revisions of "LatteDock/HowToReportCrashes"

Jump to: navigation, search
(Marked this version for translation)
m (Some corrections and additions to text)
Line 6: Line 6:
  
 
<!--T:2-->
 
<!--T:2-->
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]:
  
 
<!--T:3-->
 
<!--T:3-->
Line 12: Line 12:
 
<translate>
 
<translate>
 
<!--T:17-->
 
<!--T:17-->
# In folder {{Path|1=~/.cache/lattedock/qmlcache/}} remove everything</translate>
+
# Delete everything from the folder {{Path|1=~/.cache/lattedock/qmlcache/}} </translate>
 
<translate>
 
<translate>
 
<!--T:18-->
 
<!--T:18-->
Line 24: Line 24:
  
 
<!--T:6-->
 
<!--T:6-->
* <code>ddd latte-dock</code>
+
* Run <code>ddd latte-dock</code>
  
 
<!--T:7-->
 
<!--T:7-->
* 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>
  
 
<!--T:8-->
 
<!--T:8-->
* When it crashes, click <menuchoice>Status</menuchoice> from the menu, <menuchoice>Backtrace</menuchoice>
+
* When Latte crashes, click <menuchoice>Status</menuchoice> in the menu and select <menuchoice>Backtrace</menuchoice>
  
 
<!--T:9-->
 
<!--T:9-->
* This will show you a window with numbered lines that could be helpful for us...
+
* This will show you a window with numbered lines that can be helpful for the development team to find the issue.
  
 
<!--T:10-->
 
<!--T:10-->
If the crash is from QML you should try the following:
+
If the crash originates from QML, you should try the following:
  
 
<!--T:11-->
 
<!--T:11-->
* Run 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}}
  
 
<!--T:12-->
 
<!--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}} that should provide more information if the debug packages are installed
+
* 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.
  
 
<!--T:13-->
 
<!--T:13-->
If nothing from the above succeeds you could try to check if the crash is related to specific plasmoid:
+
If nothing mentioned above succeeds, you could try to check if the crash is related to a specific plasmoid:
  
 
<!--T:14-->
 
<!--T:14-->
# Use Latte only with default Layout (does it crash?)</translate>
+
# Use Latte with default Layout (does it crash?)</translate>
 
<translate>
 
<translate>
 
<!--T:19-->
 
<!--T:19-->
# If it doesnt crash start adding one by one your plasmoids to check their behavior and if they crash Latte...
+
# If it doesn't crash, start adding your plasmoids one by one in order to check their behavior and if they crash Latte.
 
--------
 
--------
  
 
<!--T:15-->
 
<!--T:15-->
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...
+
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
  
 
<!--T:16-->
 
<!--T:16-->

Revision as of 17:53, 10 April 2019

Other languages:
English • ‎українська

←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
  • 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:

  1. Use Latte with default Layout (does it crash?)
  2. 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


Content is available under Creative Commons License SA 4.0 unless otherwise noted.