<chapter id="faq">
<!-- **********************************************************************
                               faq.sgml
                          ++++++++++++++++++
  copyright            : (C) 2000, 2001, 2002, 2003, 2004
                          Rafi Yanai, Shie Erlich, Frank Schoolmeesters
                          & the Krusader Krew
  e-mail               : krusader@users.sourceforge.net
  web site             : http://krusader.sourceforge.net
  description          : a Krusader Documentation File

***************************************************************************
* Permission is granted to copy, distribute and/or modify this            *
* document under the terms of the GNU Free Documentation License,         *
* Version 1.1 or any later version published by the Free Software	  *
* Foundation; with no Invariant Sections, no Front-Cover Texts and        *
* no Back-Cover Texts.  A copy of the license is available on the         *
* GNU site http://www.gnu.org/licenses/fdl.html or by writing to:         *
* Free Software Foundation, Inc., 59 Temple Place - Suite 330, Boston,    *
* MA 02111-1307, USA.                                                     *
*********************************************************************** -->
<title>Frequently Asked Questions (&FAQ;)</title>
<!--	&reporting.bugs;
	&updating.documentation; -->

<para>If you have problems with &krusader; please check the &install_proc_lnk;,
       maybe your problem is caused by a bad installation.</para>

<para>The &FAQ; are devided in three sections:
  <itemizedlist>
     <listitem><para><link linkend="faq_installation">Installation &FAQ;</link> (this page)</para></listitem>
     <listitem><para><link linkend="faq_usage">Usage &FAQ;</link>
                      (issues when running/using &krusader;)</para></listitem>
     <listitem><para><link linkend="faq_general">General &FAQ;</link>
                     (bug reports, forum, mailing list, ...)</para></listitem>
  </itemizedlist>
  If you have the feeling that a &FAQ; is missing or if something is not clear to you,
  please <link linkend="editors_note">let us know</link>.
</para>


<sect1 id="faq_installation">
<title>Installation &FAQ;</title>
<qandaset>

   <qandaentry>
   <question id="faqq_missing_libs">
   <para>I have followed all steps but <command>configure</command> complains about missing libs or headers.
         What do I need to do?</para>
   </question>
   <answer>
   <para>Please install them. ;-)</para>
   <para>Here is a (possibly incomplete) list of &krusader;'s dependencies:</para>
   <para><itemizedlist>
     <listitem><para>gcc-cpp gcc-c++ glibc libgcc1 (other compilers may work but haven't been tested)
               </para></listitem>
     <listitem><para>autoconf (&eg; <filename>autoconf-2.x-xmdk.i586.rpm</filename>)
               </para></listitem>
     <listitem><para>automake (&eg; <filename>automake1.x-x.x.x-xmdk.i586.rpm</filename>)
               </para></listitem>
     <listitem><para>XFree: libxfree86 libfreetype6 libfontconfig1 libnas2 libexpat0</para></listitem>
     <listitem><para>libqt3 libqt-devel (all &krusader; versions >=1.02 are &Qt; 3.x only)</para></listitem>
     <listitem><para>kdelibs kdelibs-devel (all &krusader; versions >=1.02 are &kde; 3.x only)</para></listitem>
     <listitem><para>libjpeg62 libjpeg-devel libpng3 libmng1</para></listitem>
     <listitem><para>fam libfam-devel (&eg; <filename>fam-2.x.x-xmdk.rpm</filename> and
                     <filename>libfam0-devel-2.x.x-5mdk.i586.rpm</filename>)</para></listitem>
     <listitem><para>zlib1 arts libart_lgpl2 libstdc++5 libpcre0</para></listitem>
   </itemizedlist></para>
     <para>Most RPM-based distributions separate the headers from the libs. The headers are needed to compile
           &krusader;. Look for packages in the form foo-devel-*.rpm (&eg;
           <filename>kdelibs-devel-3.1-58mdk.i586.rpm</filename>)
           or foo-dev-*.deb for Debian based distributions. They most likely come with your distribution.
      <tip><para>If you can't find the needed package, use the &rpmfind_url; and click
		 'missing lib or header' in the search line.
		 Or use <command>apt-cache search <replaceable>foo</replaceable></command> to find the
		 corresponding package for Debian based distributions.</para></tip></para>
      <para> </para> <!-- Empty line to make it more readable -->
   </answer>
   </qandaentry>


   <qandaentry>
   <question id="path">
   <para>I have successfully installed &krusader; from source. Everything went fine but I can't start it.
   What's going wrong here?</para>
   </question>
   <answer>
   <para><itemizedlist>
          <listitem><para>The &krusader; binary is obviously not in your <envar>PATH</envar>.</para></listitem>
          <listitem><para>Use the find command to locate the binary.
<screen><prompt>$</prompt> <userinput><command> find</command> <option>/usr /opt -name</option>  krusader <option>-type f -perm +111</option></userinput>
<userinput>/usr/local/bin/krusader</userinput></screen>
          Here, the binary somehow made it into <filename class="directory">/usr/local/bin</filename>.
          It is most likely, that your
	  <envar>KDEDIR</envar> enviroment variable wasn't set properly, look at &kdeqtdir_lnk; for more info.</para></listitem>
          <listitem><para>If you don't want to recompile &krusader;, just add
          <filename class="directory">/usr/local/bin</filename> to your <envar>PATH</envar>.
          To do this for all users, append the following line in your
          <filename class="directory">/etc/profile</filename> file (or any other file your shell sources at startup).
         <screen><prompt>$</prompt> <userinput><command>export</command>  PATH=$PATH:<replaceable>/usr/local/bin</replaceable></userinput></screen></para></listitem>
    </itemizedlist></para>
    <para> </para> <!-- Empty line to make it more readable -->
   </answer>
   </qandaentry>

<qandaentry>
<question id="rpm_source">
  <para>I have downloaded the Source RPM <filename>krusader-x.xx.dist.src.rpm</filename>  What now?</para>
  </question>
  <answer>
   <para><orderedlist>
         <listitem><para>Check the ownership and the permissions on
                    <filename class="directory">/usr/src/RPM/</filename> and all recursive directories,
                    that your normal user can read-write-execute in these directories.
         </para></listitem>
         <listitem><para>To produce the binary RPM for your computer, do this:
            <screen><prompt>$</prompt> <userinput><command>rpm</command> <option>--rebuild</option> <replaceable>&lt;/path/to/rpmfile/&gt; krusader-x.xx.dist.src.rpm</replaceable></userinput></screen>
         </para></listitem>
         <listitem><para>If all <link linkend="faqq_missing_libs">dependencies</link> are ok,
                         a binary RPM <filename>krusader-x.xx.dist.rpm</filename> will be created at
                         <filename class="directory">/usr/src/RPM/RPMS/i586</filename> (replace i586 with your architecture).
         </para></listitem>
         <listitem><para>Test the binary RPM before installing:
            <screen><prompt>$</prompt> <userinput><command>rpm</command> <option>-i --test</option>  <replaceable>&lt;/path/to/rpmfile&gt; krusader-x.xx.dist.rpm</replaceable></userinput></screen>
            If the prompt returns without any message, than everything is ok.
         </para></listitem>
	 <listitem><para>Install the binary RPM as usual, for example:
            <screen><prompt>$</prompt> <userinput><command>su -c 'rpm</command> <option>-Uvh</option>  <replaceable>&lt;/path/to/rpmfile&gt; krusader-x.xx.dist.rpm</replaceable>'</userinput></screen>
            You will be asked to enter your root password.
         </para></listitem>
         <listitem><para>Now you can <link linkend="starting-krusader">start</link> &krusader;.
         </para></listitem>
    </orderedlist></para>
    <para> </para> <!-- Empty line to make it more readable -->
        <tip><para>For more information about RPM, take a look at the &maxrpm_url;.
                   This book is verry good but it dates from the year 2000, so some issues are
		   obsolete/changed/improved now. If you now a better (or updated) RPM book on the internet please
                   <link linkend="editors_note">let me know</link>.</para></tip>
    <para> </para> <!-- Empty line to make it more readable -->
   </answer>
</qandaentry>


   <qandaentry>
   <question id="rpm_fails">
   <para>I'm trying to install binary foo (RPM or DEB package), but it fails. What's wrong?</para>
   </question>
   <answer>
   <para>Since we only provide (and use) the source, we don't know.
   Please test the binary RPM before installing:
   <screen><prompt>$</prompt> <userinput><command>rpm</command> <option>-i --test</option>  <replaceable>&lt;/path/to/rpmfile&gt; krusader-x.xx.dist.rpm</replaceable></userinput></screen>
   If the prompt returns without any message, than everything is ok.</para>
   <para>If it is not ok, try to find another package at &Linux; software archives such as &freshmeat_url;
   or &kde_apps_url;. If you still can't find a package for your &Linux; distribution, we recommend searching for it with
   &rpmfind_url; or &rpmpbone_url;.</para>
   <para>In general, a package for an older version of your distrubution or even for an
   other distribution might work on your computer, but it is always the best that
   it matches your distribution.
   If you can't find a package that matches your distribution version, architecture or distribution,
   than use a source RPM.
   Because when you use a source RPM, the Krusader sources will be build on your computer,
   it will build a suitable binary RPM for your distribution and architecture.
   Please read the previous question, it explains howto install a source RPM.
   The best solution is explained in the next question.
   </para>
   <para> </para> <!-- Empty line to make it more readable -->
   </answer>
   </qandaentry>

<qandaentry>
   <question id="rpm_notfound">
   <para>I can't find a RPM or DEB package for &krusader;, What now?</para>
   </question>
   <answer>
   <para>Compile &krusader; from source :)
   Even when you think that you have no skills, you will probably succeed in compiling &krusader;!
   We provide a verry detailled &install_proc_lnk;. This will allow that even newcomers will be able
   to compile &krusader; from source, even when you dit never before a compilation from source.
   Feel free to post a &help_request_lnk; if you encounter problems.
   </para>
   <para> </para> <!-- Empty line to make it more readable -->
   </answer>
</qandaentry>

   <qandaentry>
   <question id="krusaderui_rc">
   <para>I've installed &krusader;, but when I start it, only the <guimenu>"Help"</guimenu>
	 menu appears. Why?</para></question>
   <answer>
   <para>In this case only the <guimenu>"Help"</guimenu> menu is visible and all the other menu items
   like &eg; <guimenu>"File"</guimenu> and <guimenu>"Mark"</guimenu> are gone.
   This is because some distributions put the <filename>krusaderui.rc</filename> file in a wrong directory.
   To solve the problem, just copy the <filename>krusaderui.rc</filename> file
   from the package <filename>krusader_kde3/krusader/krusaderui.rc</filename> to
   <filename>$KDEDIR/share/apps/krusader/krusaderui.rc</filename>
   and <filename>~/.kde/share/apps/krusader/krusaderui.rc</filename> and re-run &krusader;.
   If you have compiled &krusader; from sources this is often caused when the
   &kdeqtdir_lnk; enviroment variables are not right set, the result is that the
   <filename>krusaderui.rc</filename> file is installed in a wrong directory.
   Please read also the next question.</para>
   <para> </para> <!-- Empty line to make it more readable -->
   </answer>
   </qandaentry>

  <qandaentry>
  <question id="missing_menus">
  <para>Some new menu items are missing after updating &krusader;, what is wrong?</para>
  </question>
  <answer>
  <para>The <filename>krusaderui.rc</filename> file is stored in
       <filename>$KDEDIR/share/apps/krusader/krusaderui.rc</filename>.
       When you change the <guilabel>"Toolbar"</guilabel>, &kde; makes a copy of that file in the home directory at
       <filename>~/.kde/share/apps/krusader/krusaderui.rc</filename>.
       If Krusader was previously installed on your computer, and you install a newer &krusader; version the
       <filename>~/.kde/share/apps/krusader/krusaderui.rc</filename> file must be replaced with the newer version.
       </para>

  <para>The first line of <filename>krusaderui.rc</filename> contains the version number.
        After installing a newer &krusader; stable version, &kde; will replace automatiqly the old
        <filename>~/.kde/share/apps/krusader/krusaderui.rc</filename> with the newer version when starting the
        new &krusader; stable for the first time (&kde; will detect the newer version number in the first line).
        In the past this was not the case due to a bug, this bug was resolved since "krusader-cvs-2004-02-24".
        When you install a Krusader CVS or beta version you will have to replace the
        <filename>~/.kde/share/apps/krusader/krusaderui.rc</filename> manually.</para>

  <para>If the <filename>~/.kde/share/apps/krusader/krusaderui.rc</filename> file is too old,
        then the new menu elements will not be shown.
        Read the previous question for information on how to update the <filename>krusaderui.rc</filename> file.
        If <filename>krusaderui.rc</filename> is missing or in a wrong directory,
        only the <guimenu>"Help"</guimenu> menu appears, please read the previous question.
  </para>
  <para> </para> <!-- Empty line to make it more readable -->
  </answer>
  </qandaentry>

  <qandaentry>
  <question id="libfam_la">
  <para>When I run <command>make</command> it complains about <filename>libfam.la</filename></para>
  </question>
  <answer>
  <para>The <command>./configure</command> script does not check for the presence of
	<filename>libfam.la</filename>, and <command>make</command> needs <filename>libfam.la</filename>
	to compile &krusader;. If you know how this can be solved, please let us know.
	Install <filename>libfam0-devel-foo.rpm</filename>.
	Note: when you install <application>Mandrake 9.1</application> with the default settings, this
	package is not installed.
	If you need more information take a look at &missing_libs_lnk;.
   </para>
   <para> </para> <!-- Empty line to make it more readable -->
   </answer>
   </qandaentry>

  <qandaentry>
  <question id="help_request">
  <para>I am having trouble compiling and installing &krusader;, how do I send a help request?</para>
  </question>
  <answer>
  <para>Please read our detailed <link linkend="compilation">installation procedure</link> and the &faq_lnk;.
      If you can't find a solution to your problem then feel free to post a
      <emphasis role="bold">help request</emphasis> at our &krusader; forum.
      But before posting a help request at our &krusader; forum, please regard the following:
      <orderedlist>
      <listitem><para>Use the &kruforumsearch_url; function of the &forum_lnk;
      , your problem might be solved or discussed already.</para></listitem>
      <listitem><para>If you can't find a solution, please take a note of the following issues:
      <itemizedlist>
      <listitem><para>the used &krusader; version</para></listitem>
      <listitem><para>the used &Linux; distribution + version</para></listitem>
      <listitem><para>a good description of the problem</para></listitem>
      </itemizedlist>
      Without this information, it is very difficult for us to help you.
      <note><para>
      If you give us the error messages (&eg; <command>make</command> error messages)
      please start with the FIRST error message, all the error messages who are following the first error
      message are consequences and not the cause of your problem.
      </para></note>
      </para></listitem>
      <listitem><para>Post a help request with the information of the previous point at our &krugenforum_url;.
      </para></listitem>
      </orderedlist>
      </para>
      <para>Thanks for your cooperation!</para>
      <para> </para> <!-- Empty line to make it more readable -->
  </answer>
  </qandaentry>

<qandaentry>
   <question id="rpm_build">
   <para>How can i build a RPM package for &krusader;?</para>
   </question>
   <answer>
   <para>If you have experiance with compiling from source, you will probably be able to build a &krusader; RPM too.
   Follow the next steps to build an RPM.
   </para>
   <warning><para>Never, ever build RPMs when logged in as root. Mistakes in buildings packages (&eg; a bad
   <filename>krusader.spec</filename> file) can serious damage your system when logged in as root.</para></warning>
   <para><orderedlist>
         <listitem><para>Compile &krusader; from source to check that the compilation works fine.
         </para></listitem>
	 <listitem><para>Check the ownership and the permissions on
                    <filename class="directory">/usr/src/RPM/</filename> and all recursive directories,
                    that your normal user can read-write-execute in these directories.
         </para></listitem>
         <listitem><para>Copy <filename>kusader1.xx.tar.gz</filename> to
	 <filename class="directory">/usr/scr/RPM/SOURCE</filename>
         </para></listitem>
         <listitem><para>Copy <filename>kusader.spec</filename> to
	 <filename class="directory">/usr/scr/RPM/SPECS</filename>
	 Tip: the latest <filename>kusader.spec</filename> can be found in CVS.
         </para></listitem>
         <listitem><para>Edit <filename>kusader.spec</filename> and add your name, your e-mail adress,
         the rpm name, ... (please read the comments in <filename>kusader.spec</filename>).
         Maybe other changes are needed if <command>rpmbuild</command> fails.
         </para></listitem>
	 <listitem><para>Build the binary and the source RPM with:
            <screen><prompt>$</prompt> <userinput><command>rpmbuild</command> <option>-ba</option>  <replaceable>/usr/scr/RPM/SPECS/krusader.spec</replaceable></userinput></screen>
	  If everything went ok you will have a binaryRPM in
          <filename class="directory">/usr/src/RPM/RPMS/i586</filename>  (depending on your architecture)
          and a sourceRPM in <filename class="directory">/usr/src/RPM/SRPMS/</filename>
          &eg; <filename>krusader-1.40-beta1.suse90.i586.rpm</filename> and
	  <filename>krusader-1.40-beta1.suse90.src.rpm</filename>
         </para></listitem>
         <listitem><para>If it is not ok you will receive an error message during the rpmbuild process,
	 try to fix it and run <command>rpmbuild</command> again.
         </para></listitem>
         <listitem><para>And final: <link linkend="rpm_source">test</link> the RPM before sending it in.
         </para></listitem>
    </orderedlist></para>

   <para> </para> <!-- Empty line to make it more readable -->
   </answer>
</qandaentry>


</qandaset>
</sect1>


<sect1 id="faq_usage">
<title>Usage &FAQ;</title>
<qandaset>

  <qandaentry>
  <question id="supermount">
  <para>When I try to mount/unmount my cdrom/floppy, &krusader; says
             something about supermount, what's this about? </para>
  </question>
  <answer>
  <para>Supermount is a daemon which handles mounting/unmounting of removable filesystems for you.
       Just insert a floppy, and do
       <userinput><command>cd</command> <option><replaceable>/mnt/floppy</replaceable></option></userinput>
       supermount will do the mount for you automatically and transparently. All this is great, however,
       supermount manipulates the system into thinking that the <hardware>floppy/cdrom</hardware> is mounted
       at all times! This creates a few problems for &krusader;, as it can't really know what's going on -
       is there really a <hardware>floppy</hardware> in the <hardware>drive</hardware>?
       Of course, this can be solved, but as for now, we don't consider it a priority.
       Feel free to write a patch for it ;-).
  </para>
  <para> </para> <!-- Empty line to make it more readable -->
  </answer>
  </qandaentry>

  <qandaentry>
  <question id="resize">
  <para>When I try to resize &krusader;, so that it's smaller, I discover that I can't
        resize it below a certain size. Basically, it doesn't get much smaller. Why?</para>
  </question>
  <answer>
  <para>See the <guibutton>F1, F2</guibutton> (&etc;) buttons? They are not allowing &krusader; to downsize as
      they have a minimum size. Just disable them
      <emphasis role="bold"><menuchoice><guimenu>View</guimenu>
      <guimenuitem>Show FN Keys Bar</guimenuitem></menuchoice></emphasis>
      and you'll be able to resize &krusader; to your liking.
  </para>
  <para> </para> <!-- Empty line to make it more readable -->
  </answer>
  </qandaentry>

  <qandaentry>
  <question id="refresh">
  <para>When I do some file operation, &krusader;'s panel doesn't refresh / i'm using
       &krusader; with fam installed, but updates to the panel are now shown.</para>
   </question>
   <answer>
   <para>The bad news is that we're not sure why, but seems that <command>fam</command>
      (file alteration monitor) sometimes refuses to work.
      Feel free to write a patch for it ;-).
      We've tried the same source code on two different Gentoo installation: one worked,
      the other did not. The good news is that if you disable <application>fam</application>, &krusader; will
      automatically revert to its internal mechanism (which is less efficient, but works) without needing to
      recompile.
      You can disable <application>fam</application> with:
      <screen><prompt>$</prompt> <userinput><command>su -c 'fam -l'</command></userinput></screen>
      Look at the manpages for more information about <application>fam</application>.
  </para>
  <para> </para> <!-- Empty line to make it more readable -->
  </answer>
  </qandaentry>

  <!-- Thanks to Karai Csaba -->
  <qandaentry>
  <question id="samba_codepage">
  <para><application>Samba</application> ISO 8859-x codepage / what to do if &krusader; does not read shared
        directories containing national characters?</para>
  </question>
  <answer>
  <para>&krusader; does not handle (yet) <application>Samba</application> ISO 8859-x codepages, if you use a
        codepage different than 8859-1 you will have to do a manual configuration.
        Create or modify the file: <filename>~/.smb/smb.conf</filename>
        <programlisting>
 	[global]
 	workgroup = MyWorkGroup       (ex. WORKGROUP)
 	client code page = MyCodePage (ex. 852)
 	character set = MyCharSet     (ex. ISO8859-2)</programlisting>

     Unfortunately <application>kcontrol</application> (&kde; 3.1.1) fails to configure it properly, so
     this step must be done with a text editor.
  </para>
  <para> </para> <!-- Empty line to make it more readable -->
  </answer>
  </qandaentry>

  <!-- Thanks to Karai Csaba -->
  <qandaentry>
  <question id="krarc_protocol">
  <para>&krusader; reports "krarc:... protocol not supported" error at opening an archive file.</para>
  </question>
  <answer>
  <para>Solution: install the krarc slave properly:</para>
        <para>Copy the <filename>kio_krarc.so</filename>, <filename>kio_krarc.la</filename> files into
	<filename class="directory">$KDEDIR/lib/kde3</filename></para>
        <para>Copy the <filename>krarc.protocol</filename> file into
	<filename class="directory">$KDEDIR/share/services</filename></para>
        <para>or the directory where the KIO slaves are placed in your &Linux; distribution.
  </para>
  <para> </para> <!-- Empty line to make it more readable -->
  </answer>
  </qandaentry>

  <!-- Thanks to Dirk Eschler -->
  <qandaentry>
  <question id="ftp_firewall">
  <para>When I try to establish an &FTP; connection, I get an error message after 'Connect OK'
        saying 'Could not connect to host'.</para>
  </question>
  <answer>
  <para>You are probably behind a firewall/proxy and haven't enabled "Passive Mode".
      Enable "Passive &FTP;" through &kde;'s <application>Control Center</application> and try again.
      <emphasis role="bold"><menuchoice><guimenu>KDE Control Center</guimenu>
      <guimenuitem>Network</guimenuitem><guimenuitem>Preferences</guimenuitem></menuchoice></emphasis> ,
      <guilabel>Enable Passive Mode (PASV)</guilabel> has to be checked.
  </para>
  <para> </para> <!-- Empty line to make it more readable -->
  </answer>
  </qandaentry>

  <!-- Thanks to Karai Csaba -->
  <qandaentry>
  <question id="ftp_http_proxy">
  <para>I get <errorcode>"FTP protocol not supported by &krusader;"</errorcode> error at trying to open
        a remote &FTP; directory.</para>
  </question>
  <answer>
  <para>The reason of this error is that '&FTP; via &HTTP; proxy' feature is not yet supported by &krusader;.
        This error can occur at misconfiguring the proxy settings in &kde; (Control Center).
        Modify the proxy setting to not use &HTTP; proxy and &FTP; will work.
  </para>
  <para> </para> <!-- Empty line to make it more readable -->
  </answer>
  </qandaentry>


</qandaset>
</sect1>

<sect1 id="faq_general">
<title>General &FAQ;</title>
<qandaset>

  <qandaentry>
  <question id="faqq_wish_patch">
  <para>Where can I report a wish, a patch or a comment?</para>
  </question>
  <answer>
  <para>An open source projects greatest strength is derived from getting user feedback.
      That is why we love to hear what you have to say.
      The most convenient way is to use the &forum_lnk;.
      For information on what remains to be done look at the &online_todolist_url;.
      Posting to the online todo list is for developers only, but feel free to post to the &featureforum_url;
      for things that aren't on the list, but should be. If you have a nice feature request, the &krusader;
      Krew will add your request to the online todo list. You can reach us by &mail_url;
      or drop us a note in our <link linkend="faqq_kru_forum">&krusader; Forum</link>.
  </para>
  <para> </para> <!-- Empty line to make it more readable -->
  </answer>
  </qandaentry>

  <qandaentry>
    <question id="faqq_bug_report">
    <para>Where can I report a bug?</para>
    </question>
    <answer>
    <para>We have a online Bug Tracking System.</para>
    <para>Using the online bug-tracker helps us have a clear and orderly way to know how many bugs are open,
    bug priority and follow-ups. It saves us the long time needed to browse the entire &krusader; forum,
    searching for yesterdays bug. Please use this system.</para>
    <para>Before reporting a bug, please regard the following:
    <orderedlist>
    <listitem><para>Use the &kruforumsearch_url; function of the &forum_lnk;
    , your bug might be solved already. Please DO NOT post new bugs to the &bugforum_url;
    (except if you are not sure that you have found a bug).
    We use it for bug discussions.</para></listitem>
    <listitem><para><emphasis role="bold">Check</emphasis> if the bug is already posted in the
    &online_buglist_url; of the Bug Tracking System.</para></listitem>
    <listitem><para>If you can't find this bug mentioned, please <emphasis role="bold">submit</emphasis> it
    into the bug tracker by clicking the <guibutton>"Submit New"</guibutton> button in the bug-tracker window.
    Please submit the following issues: the used &krusader; version, the used &Linux; distribution + version,
    a good description of the problem.
    </para></listitem>
    </orderedlist></para>
    <para>Thanks for your cooperation!</para>
    <note><para>If possible try todo the same operation with &konqueror;, if you have the same problem than it is
    probably a &kioslave_url; (kdelibs) bug, and not a &krusader; bug.
    &krusader; uses the &kde; libraries and the &kioslaves_url; for several operations.
    </para></note>
    <para> </para> <!-- Empty line to make it more readable -->
    <note><para><remark>If you've got bugs to report please do not use &kde;'s bugzilla http://bugs.kde.org/,
    &kde;'s Bug Tracking System.</remark></para></note>
    <para> </para> <!-- Empty line to make it more readable -->
  </answer>
  </qandaentry>

  <qandaentry>
  <question id="faqq_mail_list">
  <para>Does &krusader; have a mailing list?</para>
  </question>
  <answer>
  <para>Yes, it is called &krunews_url;.
      This list is used to notify &krusader; users about new releases, major bugfixes &etc;
      No spam, no bother, just &krusader;. Feel free to (un)subscribe.
      To see the collection of prior postings to the list, visit the &krunewsarch_url;.
      </para><para>See also &krulatestnews_url; for online announcements.
      </para><para>If you want to follow the &krusader; development ... live! A &krucommits_url; is available.
      That means that everything the development team puts into CVS is reported in the list.
      Want to keep track? Waiting for a certain feature/bugfix? Feel free to (un)subscribe.
      To see the collection of prior CVS commits visit the &krucommitsarch_url;.
  </para>
  <para> </para> <!-- Empty line to make it more readable -->
  </answer>
  </qandaentry>

<qandaentry>
  <question id="faqq_kru_forum">
  <para>How does the &krusader; forum work?</para>
  </question>
  <answer>
  <para>In the spirit of freedom of speech, everything that is &krusader; related can be discussed in our forum.
        It does not matter that you are a newcomer or an advanced user, everybody is welcome.
        An open source projects greatest strength is derived from getting user feedback.
        That is why we love to hear what you have to say.
        With your feedback we can make &krusader; better and better, otherwise we are not aware of issues you may have.
        But please regard the following, so that we can maintain some order in the chaos. ;-)</para>

  <para>If the <link linkend="index">Documentation</link>, &faq_lnk; and the &kruforum_url; can't help you, do not
         hesitate to drop a posting in our forum.
         The &krusader; Krew or the &krusader; forum community is always available to help you.</para>

  <para>Please use the &kruforumsearch_url; function of the &kruforum_url;, your issue may have been
         previously discussed (this allows us to minimze the double/triple/... postings).
         If your issue has already been discussed in the past there is a great chance that you will have an instant solution
	 for your issue/problem.
         Some issues are asked over and over again, for this issues whe have the made the &faq_lnk;. ;-)
         This also allows us also to spend more time in developing &krusader;.</para>

<para>The &kruforum_url; is split up in three major sections:
  <itemizedlist>
     <listitem><para>&bugforum_url;: discussions about bugs, please DO NOT use the forum for &faqbugreports_lnk;
                         (except if you are unsure if you have found a bug).</para></listitem>
     <listitem><para>&featureforum_url;: discussions about new features for future &krusader;
                       versions.</para></listitem>
     <listitem><para>&krugenforum_url;: everything that is &krusader; related and doesn't belong in the other
                       forums.</para></listitem>
  </itemizedlist>
  </para>
  <para>Thanks for your cooperation!</para>
  <para> </para> <!-- Empty line to make it more readable -->
</answer>
</qandaentry>

<qandaentry>
  <question id="faqq_i18n">
  <para>How can i translate &krusader; to my native language?</para>
  </question>
  <answer>
  <para>Please read the &i18nhowto_url;. It's not difficult to translate! Everyone can do it, it just takes some time.
  </para>
  <para> </para> <!-- Empty line to make it more readable -->
  </answer>
</qandaentry>



</qandaset>
</sect1>

<!--
  <qandaentry>
      <question><para> </para></question>
      <answer><para>  </para></answer>
  </qandaentry>
-->

</chapter>
