<!--#include virtual="/server/header.html" -->
<!-- Parent-Version: 1.76 1.77 -->
<title>Getting help with GNU software
- GNU Project - Free Software Foundation</title>
<!--#include virtual="/help/po/gethelp.translist" -->
<!--#include virtual="/server/banner.html" -->
<h2>Getting help with GNU software</h2>

<p>The Free Software Foundation does not provide technical support.  Our
mission is developing, preserving, and protecting <a
href="/philosophy/free-sw.html">free software</a>.  We leave it to
others to earn a living providing support.  We see programmers as
providing a service, much as doctors and lawyers do now; both medical
and legal knowledge are freely redistributable, but their practitioners
charge for service.  So <strong>please do not email us or call the FSF
Office for technical support.</strong></p>

<p>You can obtain <a href="/doc/doc.html">GNU Project documentation</a>
through various methods, which should answer many of your questions.</p>

<h3>Reporting bugs</h3>

<p>Many companies now redistribute GNU software, often as part of a <a
distribution</a>.  When you find bugs in a GNU program that you
installed with a given GNU/Linux distribution, please first try
reporting the bug directly to the distributor, not to us, using the
distributor's mailing lists or web forms.  It is common for distributors
to modify the original GNU software we release (as they are free to
do!), and/or distribute older versions.  The maintainers of the original
GNU packages usually have no knowledge of what particular distributors
have done.</p>

<p>However, if you find a deficiency in the canonical release of a GNU
package, we want to know.  You can find out where to report bugs for a
given package as follows:</p>

<li>If you run the program on the command line with the <code>--help</code>
    option, you should find the location where to report bugs, usually
    at the end of the help message.</li>

<li>Otherwise, look for the home page of the package.  Usually this is
    <code>http://www.gnu.org/software/</code><em>pkgname</em>.  If this
    doesn't work or you don't know the package name, information for all
    GNU packages is included in the FSF <a
    href="http://directory.fsf.org/wiki/GNU/">Free Software Directory</a>.
    The home page should also be prominently mentioned in the package
    documentation or README files, and is often findable with a general
    Internet search.</li>

<li>The email address <bug-<em>pkgname</em>@gnu.org> will generally work
    for GNU packages, even if it is not a mailing list in its own

<li>The source files for a package may give other clues.</li>

<p>When we receive a bug report for our canonical releases, we usually
try to fix the problem.  While our bug fixes may seem like individual
assistance, they are not; they are part of preparing a new improved
version.  We may send you a patch for a bug so that you can help us test
the fix and ensure its quality.  If your bug report does not evoke a
solution from us, you may still get one from another user who reads our
bug report mailing lists.</p>

<p>In other words, please do not ask us to help you install software or
learn how to use it—but do tell us how an installation script
fails or where documentation is unclear.</p>

<p>If an important bug report goes unheeded by the maintainer after a
reasonable time (please allow at least two weeks), you can
“escalate” the bug by writing to
<maintainers@gnu.org>.  This is especially warranted if you can't
find evidence of recent activity by the maintainer.</p>

<p>When sending a bug report, please do not include very large
attachments.  Messages to GNU mailing lists have a limit of about 200k,
and will reject anything larger than that.  Uploads to <a
href="http://savannah.gnu.org">Savannah</a> have a limit of about 500k.
The best approach is to put the files on the web and include a url in
your message.  If you have no way to do that, then ask about it;
something can be worked out.</p>

<h3>Getting general help</h3>

<p>We host many <a href="http://lists.gnu.org/">mailing lists for GNU
and other free software</a>, both for bug reporting and general
discussion and help.  The mailing lists with names beginning with
<code>help-</code> are lists for getting help from the community.  If
you can't find a mailing list for a particular GNU program, then please
use the <a
mailing list.</p>

<p>The <a href="http://www.fsf.org/resources/service">FSF Service
Directory</a> is a list of people who offer support and other consulting
services.  (Contact information for new and updated listings is on that

<p>There are also <a href="/server/irc-rules.html">active IRC channels
for GNU software</a> in which you can chat with developers and

</div><!-- for id="content", starts in the include above -->
<!--#include virtual="/server/footer.html" -->
<div id="footer">
<div class="unprintable">

<p>Please send general FSF & GNU inquiries to
<a href="mailto:gnu@gnu.org"><gnu@gnu.org></a>.
There are also <a href="/contact/">other ways to contact</a>
the FSF.  Broken links and other corrections or suggestions can be sent
to <a href="mailto:webmasters@gnu.org"><webmasters@gnu.org></a>.</p>

<p><!-- TRANSLATORS: Ignore the original text in this paragraph,
        replace it with the translation of these two:

        We work hard and do our best to provide accurate, good quality
        translations.  However, we are not exempt from imperfection.
        Please send your comments and general suggestions in this regard
        to <a href="mailto:web-translators@gnu.org">

        <p>For information on coordinating and submitting translations of
        our web pages, see <a
        README</a>. -->
Please see the <a
README</a> for information on coordinating and submitting translations
of this article.</p>

<!-- Regarding copyright, in general, standalone pages (as opposed to
     files generated as part of manuals) on the GNU web server should
     be under CC BY-ND 3.0 US.  Please do NOT change or remove this
     without talking with the webmasters or licensing team first.
     Please make sure the copyright date is consistent with the
     document.  For web pages, it is ok to list just the latest year the
     document was modified, or published.
     If you wish to list earlier years, that is ok too.
     Either "2001, 2002, 2003" or "2001-2003" are ok for specifying
     years, as long as each year in the range is in fact a copyrightable
     year, i.e., a year in which the document was published (including
     being publicly visible on the web or in a revision control system).
     There is more detail about copyright years in the GNU Maintainers
     Information document, www.gnu.org/prep/maintain. -->

<p>Copyright © 2008, 2009, 2010 2010, 2014 Free Software Foundation, Inc.</p>

<p>This page is licensed under a <a rel="license"
Commons Attribution-NoDerivs 3.0 United States License</a>.</p>

<!--#include virtual="/server/bottom-notes.html" -->


<p class="unprintable">Updated:
<!-- timestamp start -->
$Date: 2014/06/04 00:29:24 $
<!-- timestamp end -->