Wiki source for TestForErrorsInLinux

Show raw source

[[HomePage]] > [[ComponentHowTo Components and HowTos]]

====How to test for and report errors in Linux====
~Often if a Linux program encounters an error it will appear to just quit without reporting any message. However, many error messages that are generated are not returned to the GUI (graphic user interface).

~To see the error you need to run the program from the [[terminal]]. This is done by starting a terminal program such as [[rxvt]] or [[RxvtUnicode urxvt]], then entering the name of the program's executable or binary file. The terminal is case-sensitive, most programs use all lowercase, for example ##abiword## or ##inkscapelite##. Note, closing the terminal window will also close any program launched from it.

~Here is an example of [[InkLite Inkscape lite]] returning an error on exit:
# inkscapelite

(inkscapelite:26863): Gtk-CRITICAL **: IA__gtk_style_detach: assertion `style->attach_count > 0' failed
# %%

~A typical error is a missing library when the program loads up. When reporting a program error on a forum for help high-light the error message and use the middle mouse button to paste into the web-browser.

==Finding program execute command==
~If the program has a [[puppymenu menu entry]] but you can't find/ workout its execute command go to to-
~##/usr/share/applications## and open the corresponding ##.desktop## file as text,
~the line starting ##exec=## reveals the command.

Valid XHTML :: Valid CSS: :: Powered by WikkaWiki