yan/archived-lcd4linux
1
0
Fork 0
mirror of https://github.com/netfun2000/lcd4linux.git synced 2026-02-27 09:44:34 +08:00
Code Issues Packages Projects Releases Wiki Activity

[lcd4linux @ 2004-06-02 05:27:59 by reinelt]

Browse Source 
added documentation tree

git-svn-id: https://ssl.bulix.org/svn/lcd4linux/trunk@458 3ae390bd-cb1e-0410-b409-cd5a39f66f1f
This commit is contained in:
reinelt
2004-06-02 05:28:06 +00:00
parent 491dc3d0e3
commit 21d19e4dbe
26 changed files with 2405 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

32
documentation/lcd4linux/bug_report.xml Normal file
View File

@@ -0,0 +1,32 @@
<?xml version="1.0" encoding="UTF-8" standalone="no" ?>
<?xml-stylesheet type="text/xsl" href="../xsl/doc.xsl"?>
<!DOCTYPE doc SYSTEM "../dtd/doc.dtd">
<doc>
<head>
<title>How to report bugs or get support</title>
<ref>bug_report</ref>
<links>
<link ref="contact"/>
</links>
</head>
<body>
You've checked twice your configuration, but &l4l; keeps complaining, prints horrible things on your display or even crashes. What to do ?
<h2>Configuration problems and minor bugs</h2>
<ul>
<li>Your display doesn't want to work, prints strange things or keeps blank ?</li>
<li>You can't get a plugin to work, there are ???? or **** where you wanted to display the temperature ?</li>
<li>You noticed a strange behavior from &l4l; or a plugin ?</li>
</ul>
You should contact the lcd4linux-users maillist, and post a detailled report containing at least :
<ul>
<li>the &l4l; version you use.</li>
<li>a description of what happens</li>
<li>if relevant, a description of your display (especially for HD44780-based displays)</li>
<li>a log of &l4l; output ( <tt>lcd4linux -vvv > log</tt> )</li>
<li>a copy of your lcd4linux.conf file</li>
</ul>
<note>If you use some plugins (mysql, mail, ...), lcd4linux.conf may contain passwords and other private information. For your privacy, we recommend you to replace these information with ***** before attaching your configuration file</note>
</body>
</doc>