How to debug OpenOffice problems

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(create page (content moved from Bugs_and_feature_requests), remove some general etiquette bits (should go on the main apge))
 
m (Update category link)
 
(7 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 
This page explains information that should be included when filing bugs related to OpenOffice.org. Problems involving OpenOffice.org should generally be filed against [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&component=openoffice.org openoffice.org].
 
This page explains information that should be included when filing bugs related to OpenOffice.org. Problems involving OpenOffice.org should generally be filed against [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&component=openoffice.org openoffice.org].
 +
 +
==General==
 +
 +
* Mention if you are using KDE or GNOME, as it often matters. If you have non-Fedora-supplied KDE theme engines installed, try one of the supported ones.
 +
* Check that similar applications don't behave the same way, e.g. if Firefox/gedit/glxgears do the same thing as OOo, then it's unlikely to be an OOo bug.
 +
* If you know you have something unusual about your setup, mention it.
 +
** ".doc documents created with msword running under wine don't open in OOo" as opposed to just saying ".doc files don't open in OOo"
 +
** "Saving to a samba share doesn't work" versus "saving doesn't work"
 +
 +
==Crashes==
  
 
* A crash on startup might be a crash in some OpenGL lib, not OOo itself.
 
* A crash on startup might be a crash in some OpenGL lib, not OOo itself.
Line 5: Line 15:
 
** Run <code>gcc testgl.c -o testgl -lX11 -lGL</code> to compile it.
 
** Run <code>gcc testgl.c -o testgl -lX11 -lGL</code> to compile it.
 
** If it also crashes, your bug is probably not an OOo bug.
 
** If it also crashes, your bug is probably not an OOo bug.
* Check that similar applications don't behave the same way, e.g. if Firefox/gedit/glxgears do the same thing as OOo, then it's unlikely to be an OOo bug.
 
 
* If the crash dialog appears, paste the stacktrace it gives you into your bug report.
 
* If the crash dialog appears, paste the stacktrace it gives you into your bug report.
* Mention if you are using KDE or GNOME, as it often matters. If you have non-Fedora-supplied KDE theme engines installed, try one of the supported ones.
 
* If there is an error/warning message, say what the message is.
 
* If it happens with a particular document, attach the document. If you can, trim the document down to the smallest test case that reproduces the problem. "Scroll to page 912 and the graphic is misplaced" is much less appealing than having a one-page example.
 
* If you think there is something wrong with what is being displayed, attach a screenshot. ''I'' might not understand ''your'' description.
 
 
Example: "formula font is wrong"
 
 
Is it the font used in the text area for editing the formula, or is it the font used to display the formula? Did you mean the math editor, or did you actually mean formulas in calc?  A screenshot would solve these kinds of questions.
 
 
* If you know you have something unusual about your setup, mention it.
 
 
Examples:
 
* ".doc documents created with msword running under wine don't open in OOo" as opposed to just saying ".doc files don't open in OOo"
 
* "Saving to a samba share doesn't work" versus "saving doesn't work"
 
 
 
* If you can, install the debuginfo and try:
 
* If you can, install the debuginfo and try:
 
<pre>
 
<pre>
Line 28: Line 22:
 
(gdb) bt
 
(gdb) bt
 
</pre>
 
</pre>
Paste the backtrace in your bug report.
 
  
(<code>-writer</code> should be changed accordingly: <code>-calc -impress -math -draw</code>)
+
:Paste the backtrace in your bug report.
 +
 
 +
:(<code>-writer</code> should be changed accordingly, depending on which application you are using, to one of: <code>-writer -calc -impress -math -draw</code>)
 +
 
 +
==Other bug types==
 +
 
 +
* If there is an error/warning message, say what the message is.
 +
* If it happens with a particular document, attach the document. If you can, trim the document down to the smallest test case that reproduces the problem. "Scroll to page 912 and the graphic is misplaced" is much less appealing than having a one-page example.
 +
* If you think there is something wrong with what is being displayed, attach a screenshot. ''I'' might not understand ''your'' description.
 +
**Example: "formula font is wrong"
 +
 
 +
::Is it the font used in the text area for editing the formula, or is it the font used to display the formula? Did you mean the math editor, or did you actually mean formulas in calc?  A screenshot would solve these kinds of questions.
 +
 
 +
[[Category:Debugging|O]] [[Category:How to]]

Latest revision as of 15:24, 23 October 2009

This page explains information that should be included when filing bugs related to OpenOffice.org. Problems involving OpenOffice.org should generally be filed against openoffice.org.

[edit] General

  • Mention if you are using KDE or GNOME, as it often matters. If you have non-Fedora-supplied KDE theme engines installed, try one of the supported ones.
  • Check that similar applications don't behave the same way, e.g. if Firefox/gedit/glxgears do the same thing as OOo, then it's unlikely to be an OOo bug.
  • If you know you have something unusual about your setup, mention it.
    • ".doc documents created with msword running under wine don't open in OOo" as opposed to just saying ".doc files don't open in OOo"
    • "Saving to a samba share doesn't work" versus "saving doesn't work"

[edit] Crashes

  • A crash on startup might be a crash in some OpenGL lib, not OOo itself.
    • Get the test source at [1] .
    • Run gcc testgl.c -o testgl -lX11 -lGL to compile it.
    • If it also crashes, your bug is probably not an OOo bug.
  • If the crash dialog appears, paste the stacktrace it gives you into your bug report.
  • If you can, install the debuginfo and try:
$> gdb /usr/lib/openoffice.org/program/soffice.bin
(gdb) run -writer
(gdb) bt
Paste the backtrace in your bug report.
(-writer should be changed accordingly, depending on which application you are using, to one of: -writer -calc -impress -math -draw)

[edit] Other bug types

  • If there is an error/warning message, say what the message is.
  • If it happens with a particular document, attach the document. If you can, trim the document down to the smallest test case that reproduces the problem. "Scroll to page 912 and the graphic is misplaced" is much less appealing than having a one-page example.
  • If you think there is something wrong with what is being displayed, attach a screenshot. I might not understand your description.
    • Example: "formula font is wrong"
Is it the font used in the text area for editing the formula, or is it the font used to display the formula? Did you mean the math editor, or did you actually mean formulas in calc? A screenshot would solve these kinds of questions.