path: root/FAQ

--------------------------------------------
- Documentation version:  1.90.0
- Documentation date:  2008-03-06
- Parsing date: Thu Mar  6 22:31:20 UTC 2008
--------------------------------------------
 

This file contains the Krusader FAQ
This file is parsed from Docbook/XML source files
with the 'make_doc' script (krusader-handbook-1.80.0.source.tar.gz ).


Note:
-----
after the parsing process to generate this TXT file all te URL's are gone,
to see the URL's again please take a look at the HTML version of this file.


Feedback:
---------
Feedback for the documentation is always welcome.

Frank Schoolmeesters, documentation coordinator
[frank_schoolmeesters {*} yahoo {.} com]

Latest version:
---------------
The latest version of this document is available online at: 
http://krusader.sourceforge.net/handbook/faq.html

Latest version of the Krusader documentation should always be available:
- online reading (Krusader-CVS):
    http://krusader.sourceforge.net/handbook/index.html
- most recent documentation tarball
    http://sourceforge.net/project/showfiles.php?group_id=6488&package_id=125990
- when downloading and installing the most recent Krusader from the
    CVS repository (the doc's will be available via the Help menu) 
     http://krusader.sourceforge.net/cvs.php
	 http://krusader.sourceforge.net/handbook/installation.html


            as always, enjoy
                 Krusader Krew.

                      http://krusader.sourceforge.net


db   dD d8888b. db    db .d8888.  .d8b.  d8888b. d88888b d8888b.
88 ,8P' 88  `8D 88    88 88'  YP d8' `8b 88  `8D 88'     88  `8D
88,8P   88oobY' 88    88 `8bo.   88ooo88 88   88 88ooooo 88oobY'
88`8b   88`8b   88    88   `Y8b. 88~~~88 88   88 88~~~~~ 88`8b
88 `88. 88 `88. 88b  d88 db   8D 88   88 88  .8D 88.     88 `88.
YP   YD 88   YD ~Y8888P' `8888Y' YP   YP Y8888D' Y88888P 88   YD 

------------------------------------------------------------------------


IMPORTANT: Crashes in Krusader caused by Qt 3.3.5
*************************************************
We've been getting a lot of emails and bug reports regarding random
crashes in Krusader, especially during some file operations (copy/move
etc.). These crashes are related to Qt 3.3.5 and NOT Krusader. It seems
that Qt 3.3.5 introduced a serious bug which is now causing random
crashes in many KDE applications including Konqueror. You can google for
it to find out more. 

As far as we know, debian and suse already posted new Qt binaries that
fix the problem, and gentoo has masked Qt 3.3.5 completely. As for now,
you either need Qt 3.3.4 or a fixed Qt 3.3.5, depending on your
distribution. For more information is available on our website at
http://krusader.sourceforge.net/phpBB/viewtopic.php?t=1407 


------------------------------------------------------------------------


Chapter 13. Frequently Asked Questions (FAQ)
Table of Contents
  Installation_FAQ
  Usage_FAQ
  General_FAQ
If you have problems with Krusader please check the Installation_procedure, as
your problem may be caused by a bad installation.
The FAQ is divided into three sections:
    * Installation_FAQ (this page)
    * Usage_FAQ (issues with running/using Krusader)
    * General_FAQ (bug reports, forum, mailing list, ...)
If you feel that a FAQ is missing or if something is not clear to you, please
let_us_know.
Installation FAQ
  1. Does_Krusader_need_KDE_to_run?
  2. Which_libraries_does_Krusader_need_to_run?
  3. I_have_followed_all_the_steps_but_configurecomplains_about_missing_libs_or
  headers._What_do_I_need_to_do?
  4. How_do_I_compile_Krusader_when_I'm_using_a_64_bit_processor_?
  5. I_have_downloaded_the_Source_RPM_krusader-x.xx.dist.src.rpm,_what_to_do
  now?
  6. I'm_trying_to_install_binary_foo_(RPM_or_DEB_package),_but_it_fails.
  What's_wrong?
  7. I_can't_find_an_RPM_or_DEB_package_for_Krusader,_what_to_do?
  8. I've_installed_Krusader,_but_when_I_start,_only_the_"Help"_menu_appears.
  Why?
  9. Some_new_menu_items_are_missing_after_updating_Krusader,_what's_wrong?
  10. When_I_run_make,_it_complains_about_libfam.la,_what's_wrong?
  11. Debian_complains_about_Qt_when_running_./configure,_what's_wrong?
  12. I_have_a_libGLcore.so.1_compile_error_after_using_the_NVIDIA_installer,
  what_to_do?
  13. Why_Krusader-1.60.x_does_not_compile_with_gcc4?
  14. I_am_having_trouble_compiling_and_installing_Krusader,_how_do_I_send_a
  help_request?
  15. How_can_I_build_an_RPM_package_for_Krusader?
  16. Why_does_Krusader-cvs_show_an_old_version_number_in_the_about_box?
1.  Does Krusader need KDE to run?
    No, Krusader does not need the KDE window manager to run on your computer
    but Krusader's natural environment is KDE, because it relies on services
    provided by the KDE base libraries. Only some shared libraries are needed
    e.g. KDE libraries, Qt™ libraries, etc. This means that Krusader runs
    on GNOME, AfterStep, XFce and other window managers provided the approriate
    libraries are installed on your computer. All this is not a problem since
    the apt-get world can resolve these dependencies instantly.
    You do not need to switch to the KDE window manager to use Krusader; you
    can still use GNOME, AfterStep, XFce or another window manager. However,
    the configuration of the Krusader fonts and some behavior is done by
    running kcontrol.
    A lot depends on what you want to do with Krusader. You should know that
    Krusader uses the KDE KIOSlaves to access remote file systems, and support
    for only a limited number of file system types are shipped with KDElibs,
    most of the KIOSlaves are bundled with KDEbase (including fish, sftp and
    tar). However, if you want the property-dialog to show EXIF-data for
    .jpeg's, you need KDEgraphics. If you want ID3-infos, you need
    KDEmultimedia, and so on.
    To summarize, if you want a working Krusader - install KDElibs. If you want
    a functional Krusader then you need KDElibs + KDEbase. For maximum
    functionality, Krusader needs all of the KDE package libraries, but the KDE
    window manager is optional.
2.  Which libraries does Krusader need to run?
    For running Krusader (e.g. when you have installed Krusader with a binary
    RPM) you need less libraries than if you compile Krusader from source. e.g.
    you only need the C-compliler gcc when you compile Krusader from source
    (see the next question).
    Here is a list of the required shared libraries when you run Krusader:
        * kdelibs (for the required KDE version see the Installation_procedure)
        * libacl1 libart-2.0 libattr1 libaudio2 libc6 libfam0 libfontconfig1
        * libfreetype6 libgcc1 libgcc2 libice6 libidn11 libjpeg62 libkjsembed1
        * libkonq4 libpcre3 libpng12 libqt3-mt libsm6 libstdc++6 libunwind7
          libx11-6
        * libxcursor1 libxext6 libxft2 libxi6 libxinerama1 libxrandr2
          libxrender1 libxt6 zlib1g
    If you need more info please take a look at the requirements_on_Debian� .
3.  I have followed all the steps but configurecomplains about missing libs or
    headers. What do I need to do?
    Install the missing packages.
    Here is a list of the required packages to compile Krusader from source:
        * gcc-cpp gcc-c++ glibc libgcc1 (other compilers may work but haven't
          been tested)
        * autoconf automake XFree
        * libqt3 libqt-devel
        * kdelibs kdelibs-devel
        * libjpeg62 libjpeg-devel libpng3 libmng1
        * fam libfam-devel
        * zlib1 arts libart_lgpl2 libstdc++5 libpcre0
        * libkjsembed, if you use the JavaScript_console, often found in a
          package called KDEbindings(-devel) and libkonq-dev for the Konqueror
          right-click menu entries.
    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 (e.g. kdelibs-devel-foo.i586.rpm) or foo-dev-*.deb for Debian�
    based distributions. These are usually included with your distribution.
    **** Tip ****
    If you ca not find the needed package, use rpmfind and click 'missing lib
    or header' in the search line. Or use apt-cache search foo to find the
    corresponding package for Debian� based distributions.
4.  How do I compile Krusader when I'm using a 64 bit processor ?
    As far as we know, there are no issues. Krusader is also available on many
    other_architectures.
5.  I have downloaded the Source RPM krusader-x.xx.dist.src.rpm, what to do
    now?
       1. Check the ownership and the permissions on /usr/src/RPM/ and all
          recursive directories that your normal user can read-write-execute in
          these directories.
       2. To produce the binary RPM for your computer, do this:
          $ rpm --rebuild </path/to/rpmfile/> krusader-x.xx.dist.src.rpm
       3. If all dependencies are OK, a binary RPM krusader-x.xx.dist.rpm will
          be created at /usr/src/RPM/RPMS/i586 (replace i586 with your
          architecture).
       4. Test the binary RPM for errors before installing:
          $ rpm -i --test </path/to/rpmfile> krusader-x.xx.dist.rpm
          If the prompt returns without any message, then everything is OK.
       5. Install the binary RPM as usual, for example:
          $ su -c 'rpm -Uvh </path/to/rpmfile> krusader-x.xx.dist.rpm'
          You will be asked to enter your root password.
       6. Now you can start Krusader.
    **** Tip ****
    For more information about RPM, visit rpm.org and read the RPM_Guide by
    Eric Foster-Johnson.
6.  I'm trying to install binary foo (RPM or DEB package), but it fails. What's
    wrong?
    Since we only prepare (and use) the source, we have no way of knowing this.
    Did you test the binary RPM before installing?
    $ rpm -i --test </path/to/rpmfile> krusader-x.xx.dist.rpm
    If the prompt returns without any message, then everything is OK. RPM's
    downloaded from our website are usually provided by Krusader users. Visit
    your distro website and search for an updated RPM.
    If the RPM is not OK, try to find another package at Linux� software
    archives such as freshmeat.net or KDE-APPS.org. If you still can't find the
    appropriate package for your Linux� distribution, we recommend searching
    for it with rpmfind or rpmpbone.
    In general, a package for an older version of your distrubution or even for
    another distribution might work on your computer (e.g. FC RPM's often work
    on Mdk and RH, and vice versa), but it is always the best that you install
    only RPM's that exactly match your distribution. If you can't find a
    package that matches your distribution version, architecture or
    distribution, then use a source RPM. When you use a source RPM, the
    Krusader sources will be built, on your computer, guaranteeing a suitable
    binary RPM for your specific distribution and architecture. In addition,
    this method results in maximum system speed, since the resulting binary is
    customized for your computer. Please read the previous question, it
    explains how to install a source RPM. The best solution is explained in the
    next question.
7.  I can't find an RPM or DEB package for Krusader, what to do?
    Check if your distribution provides Krusader, if it doesn't then contact
    your distribution creator and ask them to include Krusader!
    Did you take a look at the URL's on the Installation_procedure page? If you
    have and found nothing, you can always compile Krusader from source. Even
    if you feel you haven't got the necessary skills, you will probably succeed
    in compiling Krusader: we provide a very detailed installation procedure.
    This HowTo enables newcomers to compile Krusader from source, even if they
    have never done a compilation from source before, just follow the
    instructions carefully. Feel free to post a help_request if you encounter
    problems.
8.  I've installed Krusader, but when I start, only the "Help" menu appears.
    Why?
    In this case only the Help menu is visible and all other menu items like
    e.g. File and Select are missing. This is because some distributions put
    the krusaderui.rc file in the wrong directory. To solve the problem, just
    copy the krusaderui.rc file from the package krusader_trinity/krusader/
    krusaderui.rc to $KDEDIR/share/apps/krusader/krusaderui.rc and ~/.trinity/
    share/apps/krusader/krusaderui.rc and re-run Krusader. If you have compiled
    Krusader from sources this is often caused if the KDEDIR_-_QTDIR
    environment variables are not correctly set. The result is that the
    krusaderui.rc file is installed in the wrong directory. Please read the
    following question, as well.
9.  Some new menu items are missing after updating Krusader, what's wrong?
    The krusaderui.rc file is stored in $KDEDIR/share/apps/krusader/
    krusaderui.rc. When you change the "Toolbar", KDE makes a copy of that file
    in the home directory at ~/.trinity/share/apps/krusader/krusaderui.rc. If
    Krusader was previously installed on your computer, and you install a newer
    Krusader version the ~/.trinity/share/apps/krusader/krusaderui.rc file must be
    replaced with the newer version. Note: this will also reset all your
    changes on toolbars and shortcuts!
    The first line of krusaderui.rc contains the version number. After
    installing a newer Krusader version, KDE will automatically replace the old
    ~/.trinity/share/apps/krusader/krusaderui.rc with the newer version when
    starting the new Krusader for the first time (KDE will detect the newer
    version number in the first line).
    If you install a CVS or beta version and Krusader was already installed on
    your computer then you should delete the krusaderui.rc file from your home
    directory to activate the new menu entries $ rm ~/.trinity/share/apps/krusader/
    krusaderui.rc
    If the ~/.trinity/share/apps/krusader/krusaderui.rc file is older, then the new
    menu elements will not be shown. Read the previous question for information
    on how to update the krusaderui.rc file. If krusaderui.rc is missing or in
    a wrong directory, only the "Help" menu appears, please read the previous
    question.
10. When I run make, it complains about libfam.la, what's wrong?
    The ./configure script does not check for the presence of libfam.la, and
    make needs libfam.la to compile Krusader. If you know how this can be
    solved, please let us know. Install libfam0-devel-foo.rpm. Note: when you
    install Mandrake&#8482;-Linux� 9.2 with the default settings, this package
    is not installed. If you need more information take a look at FAQ_missing
    libs_or_headers.
11. Debian� complains about Qt&#8482; when running ./configure, what's wrong?
    This problem occurs when you use gcc 2.95, you need to install gcc 3.2 (or
    higher). You also need to set the enviroment variables "CC, CPP and CXX"
    before running the ./configure script.
    $ export CC=/usr/bin/gcc-3.2
              $ export CXX=/usr/bin/g++-3.2
              $ export CPP=/usr/bin/cpp-3.2
    For more information please take a look in_our_forum and at the
    instructions on how to build a Qt&#8482;/KDE3 application on Debian�.
12. I have a libGLcore.so.1 compile error after using the NVIDIA� installer,
    what to do?
    This problem occurs when you use the NVIDIA� installer and not the official
    NVIDIA� packages of your distribution. Krusader is based on Qt&#8482; which
    can be linked against the X OpenGL libraries. As a result Krusader may look
    for OpenGL as well. The problem is that the NVIDIA� installer (prior to
    version 7xxx) doesn't perform it's task properly: it replaces the OpenGL
    header files (which get included into Krusader) but doesn't set the libGL
    links correctly. The best solution is to use the NVIDIA� packages provided
    by your distributor or a new NVIDIA� installer, the current version at the
    moment of writing is 7114. If, for some reason, you must use an old NVIDIA�
    driver, one solution is the following hack, the exact commands depend on
    the distribution used and the version of the NVIDIA� driver (6111 in this
    example), but it should read something like this:
    $ ln -s libGLcore.so.1.0.6111 libGLcore.so.0
              $ ln -s libGLcore.so.1.0.6111 libGLcore.so
              $ ln -s libGLcore.so.1.0.6111 libGLcore.so.1.0.0
              $ ln -s libGLcore.so.1.0.6111 libGLcore.so.0.0.0
              $ ln -s libGLcore.so.1.0.6111 libGL.so
              $ ln -s libGLcore.so.1.0.6111 libGL.so.0
              $ ln -s libGLcore.so.1.0.6111 libGL.so.0.0.0
              $ ln -s libGLcore.so.1.0.6111 libGL.so.1
              $ ln -s libGLcore.so.1.0.6111 libGL.so.1.0.0
              $ ln -s /usr/lib/libGLU.la /usr/X11R6/lib/libGLU.la
13. Why Krusader-1.60.x does not compile with gcc4?
    Because Krusader-1.60.x was not gcc4 compatible, it first needs some
    patches:
        * add 'class ListPanelFunc;' in krusader/Panel/listpanel.h
        * add 'class KMountManGUI;' in krusader/MountMan/kmountman.h
        * add 'class KrDetailedViewItem;' in krusader/Panel/krdetailedview.h
    More information can be found in our forum.
14. I am having trouble compiling and installing Krusader, how do I send a help
    request?
    Please read our detailed installation_procedure and the FAQ. If you can't
    find a solution to your problem then feel free to post a help request at
    our Krusader forum or use the Krusader-users mailing list. But before
    posting a help request, please try the following:
       1. Use the Search function on the Krusader_Forum, your problem might be
          solved or discussed already.
       2. If you can't find a solution, please make a note of the following
          issues:
              * the Krusader version used
              * the Linux� distribution + version used
              * a good description of the problem
          Without this information, it is very difficult for us to help you.
          **** Note ****
          If you give us the error messages (e.g. make error messages) please
          start with the FIRST error message, all the error messages which
          follow the first error message are consequences and not the cause of
          your problem.
       3. Send out your help request.
    Thank you for your co-operation!
15. How can I build an RPM package for Krusader?
    If you have experience with compiling from source, you will probably be
    able to build a Krusader RPM too. Information about RPM can be found at
    rpm.org and in the RPM_Guide by Eric Foster-Johnson. The following is the
    short procedure howto on building an RPM.
    **** Warning ****
    NEVER build RPMs when logged in as root. Mistakes in building packages
    (e.g. a bad krusader.spec file) can do serious damage to your system when
    logged in as root.
       1. Compile Krusader from source to check that the compilation works
          fine.
       2. Check the ownership and the permissions on /usr/src/RPM/ and all
          recursive directories that your normal user can read-write-execute in
          these directories.
       3. Copy kusader-1.xx.tar.gz to /usr/scr/RPM/SOURCE
       4. Copy kusader.spec to /usr/scr/RPM/SPECS Tip: the latest kusader.spec
          can be found in CVS.
       5. Edit kusader.spec and add your name, your e-mail address, the rpm
          name, ... Other changes may be needed if rpmbuild fails.
       6. Build the binary and the source RPM with:
          $ rpmbuild -ba /usr/scr/RPM/SPECS/krusader.spec
          If everything went OK you will have a binary RPM in /usr/src/RPM/
          RPMS/i586 (depending on your architecture) and a source RPM in /usr/
          src/RPM/SRPMS/ e.g. krusader-1.70-beta1.suse10.i586.rpm and krusader-
          1.70-beta1.suse10.src.rpm
       7. If the build is not OK you will receive an error message during the
          rpmbuild process, try to fix it and run rpmbuild again.
       8. And finally: test the RPM before sending it in.
16. Why does Krusader-cvs show an old version number in the about box?
    Because we only change the version number just before we do a new release.
    Krusader-cvs will show an older version number, so ignore the version
    number and check the download date. We simply haven't yet decided what the
    next version number will be.
Usage FAQ
  1. Krusader_keeps_crashing,_why?
  2. When_I_try_to_mount/unmount_my_cdrom/floppy,_Krusader_reports_something
  about_a_supermount,_what's_this_about?
  3. Why_does_Krusader_freeze_or_hang_on_a_dead_mountpoint?
  4. When_I_try_to_resize_Krusader_to_make_it_smaller,_I_discover_that_I_can't
  resize_it_below_a_certain_size._Why?
  5. When_I_perform_some_file_operations,_Krusader's_panel_doesn't_refresh_/
  I'm_using_Krusader_with_fam_installed,_but_updates_to_the_panel_are_not
  shown._Why?
  6. Samba_ISO_8859-x_codepage_/_What_to_do_if_Krusader_does_not_read_shared
  directories_containing_special_international_characters?
  7. Krusader_reports_"krarc:..._protocol_not_supported"_error_at_opening_an
  archive_file,_what_to_do?
  8. I_get_the_error_message_"Protocol_not_supported_by_Krusader:_"krarc:/path/
  to/foo-archive",_when_I_try_to_open_foo-Archive,_what_to_do?
  9. What_todo_if_an_extenal_tool_doesn't_seem_to_work?
  10. Howto_executing_jar_files_(and_not_enter_the_jar_archive)?
  11. Why_do_I_have_trouble_with_my_FTP_connection?
  12. I_get_"FTP_protocol_not_supported_by_Krusader"_error_when_trying_to_open
  a_remote_FTP_directory,_what_to_do?
  13. How_don't_add_".part"_suffix_when_copying_files_via_ftp?
  14. How_can_I_close_a_remote_connection_(e.g._a_FTP_connection)?
  15. I_am_experiencing_problems_with_the_media://_protocol,_why?
  16. How_can_I_disable_the_default_sounds,_e.g._when_I_do_a_delete_action_?
  17. Where_is_RemoteMan,_the_remote_connection_manager_?
  18. Why_doesn't_mimetype_magic_sometimes_work_inside_archives?
  19. Where_is_Konfigurator,_do_i_need_to_install_the_KDE_Desktop_Enviroment_to
  use_it?
  20. How_can_I_set_the_look_&_feel_of_2_different_users_to_be_the_same?
  21. Why_doesn't_"save_last_location"_work?
  22. Why_doesn't_the_handbook_work?
1.  Krusader keeps crashing, why?
    We've been receiving a lot of emails and bug reports (December 2005)
    regarding random crashes, especially during file operations such as copy,
    move, etc. These crashes are related to Qt&#8482; 3.3.5 and NOT Krusader.
    It seems that Qt&#8482; 3.3.5 introduced a serious bug which is currently
    (December 2005) causing random crashes in many KDE applications including
    Konqueror. You can use Google to find out more. As far as we know, Debian�-
    Sid and SuSE� already posted new Qt&#8482; binaries that fix the problem,
    and Gentoo� has masked Qt&#8482; 3.3.5 completely. As for now, you either
    need Qt&#8482; 3.3.4 or a fixed Qt&#8482; 3.3.5 or a higer version,
    depending on your distribution. More information is available on our
    website.
2.  When I try to mount/unmount my cdrom/floppy, Krusader reports something
    about a supermount, what's this about?
    Supermount is a daemon which handles the mounting/unmounting of removable
    filesystems for you. Just insert a floppy, and do cd /mnt/floppysupermount
    will do the mount for you automatically and transparently. Usually this
    works fine. However, supermount misleads the system into thinking that the
    floppy/cdrom is mounted at all times! This creates some problems for
    Krusader, as it cannot really know when the floppy or CD has been removed
    because the system information is not correctly updated by supermount - is
    there really a floppy in the drive? Of course, this can be solved, but as
    for now, we don't consider it a priority.
3.  Why does Krusader freeze or hang on a dead mountpoint?
    When Krusader is e.g. browsing an NFS share and the NFS server goes down,
    Krusader will freeze. This Krusader (and all other open internal viewers/
    editors) freeze is fatal, and can only be corrected with the kill -9. We
    have no solution for this. This is an issue not confined to file managers,
    or even the Linux� OS! The problem is that you "hang" on the first access
    to the dead share - so there is no way around it, no check to avoid it,
    even ls will freeze. Just trying to read something - anything - is enough
    to get you stuck. The one and only way around this architectural problem is
    using a multi-threaded design - this way if we get stuck, we don't hang the
    entire application event loop, but we don't think that the time is right
    for adding threads, we are not sure that *all* the KDE systems out there
    are using Qt&#8482;-mt (the multi threaded version of the Qt&#8482;
    library), and the Krusader Krew may not be the right people to address this
    major issue in any case; so currently this is just a bug we have to learn
    to live with.
4.  When I try to resize Krusader to make it smaller, I discover that I can't
    resize it below a certain size. Why?
    See the F1, F2 (etc.) buttons? They are not allowing Krusader to downsize
    as they have a minimum size. Just disable them View->Show FN Keys Bar and
    you'll be able to resize Krusader to your liking. Since version 1.51 we
    have improved this greatly: when downsizing the buttons will look like 'F5
    ..py'. When the button faces are too small to read a tooltip will give the
    complete text. The minimum width is 45 pixels for each button.
5.  When I perform some file operations, Krusader's panel doesn't refresh / I'm
    using Krusader with fam installed, but updates to the panel are not shown.
    Why?
    The bad news is that we're not sure why, but it seems that fam (file
    alteration monitor) sometimes refuses to work. We are looking into this
    problem to make sure it is not our problem. We've tried the same source
    code on two different Gentoo installations: one worked, the other did not.
    The good news is that if you disable fam, Krusader will automatically
    revert to its internal update mechanism (which is less efficient, but
    works) without needing to recompile. You can disable fam with:
    $ su -c 'fam -l'
    Look at the manpages for more information about fam.
6.  Samba ISO 8859-x codepage / What to do if Krusader does not read shared
    directories containing special international characters?
    Krusader does not handle (yet) Samba 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: ~/.smb/smb.conf
    [global]
              workgroup = MyWorkGroup (ex. WORKGROUP)
              client code page = MyCodePage (ex. 852)
              character set = MyCharSet (ex. ISO8859-2)
    Unfortunately kcontrol (KDE 3.1.1) fails to configure smb.conf properly, so
    this must be done manually with a text editor.
7.  Krusader reports "krarc:... protocol not supported" error at opening an
    archive file, what to do?
    Install the krarc slave properly:
    Copy the kio_krarc.so, kio_krarc.la files into $KDEDIR/lib/trinity
    Copy the krarc.protocol file into $KDEDIR/share/services
    or the directory where the KIO slaves are placed in your Linux�
    distribution.
8.  I get the error message "Protocol not supported by Krusader: "krarc:/path/
    to/foo-archive", when I try to open foo-Archive, what to do?
    The icons, kio_slaves and documentation must be installed in the correct
    places in the KDE directory tree. The kio_krarc.* files must be in the same
    directory with the other KIO slaves. Try this: locate kio_tar.* and copy/
    link the kio_krarc.* files to the same location. Don't forget to run #
    ldconfig on this directory when you're done. For more information click
    here.
9.  What todo if an extenal tool doesn't seem to work?
    Krusader uses several programs as external_tools, and sometimes they appear
    not to work. Open a terminal and check if tool foo is installed.
    $ foo
    Check if tool foo is properly configured in the Konfigurator_Dependencies
    page. For Archiving tools: autodetect the archives again with the Auto
    Configure button in the Konfigurator_archive_page. Check the Konfigurator
    Protocol_page If it doesn't work, backup your ~/.trinity/share/config/
    krusaderrc configuration file and remove it from this location, Restart
    Krusader, Krusader will now start the first start configuration wizard,
    follow these guidelines.
10. Howto executing jar files (and not enter the jar archive)?
    Go to the Konfigurator_Protocol_page and remove application/x-jar from the
    krarc node, Krusader should no longer enter the archive. Global file
    associations are handled by KDE and not by Krusader. To assosiate the jar
    extension:
        * Open KDEs control center: kcontrol
        * KDE Components->File Associations
        * Enter jar as filename pattern
        * Add java as application
11. Why do I have trouble with my FTP connection?
    This problem often occurs when you are behind a firewall or proxy. Open KDE
    Control Center->Network->Preferences, "Enable Passive Mode (PASV)" has to
    be turned on or off, depending on it's current setting. Now try your FTP
    session again to see if it works. Also, make sure you have no other FTP
    sessions open (using web browsers, etc.), they can cause complications.
    More information can be found in Active_FTP_vs._Passive_FTP,_a_Definitive
    Explanation.
12. I get "FTP protocol not supported by Krusader" error when trying to open a
    remote FTP directory, what to do?
    The reason for this error is that 'FTP via HTTP proxy' feature is not yet
    supported by Krusader. This error may be caused by a misconfiguration of
    the proxy settings in KDE Control Center. Modify the proxy settings to not
    use HTTP proxy and FTP will work.
13. How don't add ".part" suffix when copying files via ftp?
    When uploading files a .part suffix is added to the filename, once the
    upload is complete the filename is renamed automagically to remove the
    .part suffix. This works great but sometimes some ftp-servers don't allow a
    rename operation. You can solve this by unchecking the checkbox Mark
    partially uploaded files in KDE's control center. The checkbox is located
    at Internet and Network->Connection Preferences.
14. How can I close a remote connection (e.g. a FTP connection)?
    It's explained in the remote_connections_chapter.
15. I am experiencing problems with the media:// protocol, why?
    At the moment of writing the media:// protocol is instable, we need to wait
    until the KDE team corrects it, every other protocol works properly with
    Krusader, only media fails. More information regarding this issue is
    available in our_forum.
16. How can I disable the default sounds, e.g. when I do a delete action ?
    Those are the default KDE System sounds, and not related to Krusader. If
    you want to disable them globally open your KDE KDE Control Center
    ( kcontrol): KDE Control Center->Sound & Multimedia->System Notifications,
    Event Source: "KDE System Notifications" and uncheck sound items you don't
    like.
17. Where is RemoteMan, the remote connection manager ?
    RemoteMan has been replaced by our Bookmark Manager since Krusader 1.25-
    beta1. The Bookmark Manager handles local files and remote_URL's the same
    way. RemoteMan was left as a selection until Krusader-1.51 to allow an
    easier transition and give you a chance to move your Bookmarks. RemoteMan
    was disabled, as announced, in Krusader-1.60.
    URL transition procedure:
       1. install Krusader-1.51
       2. open the RemoteMan and connect to an FTP
       3. once inside, bookmark the current location, select a name and save.
       4. do this for all your connections, all the Bookmarks are now stored in
          krbookmarks.xml
       5. install Krusader-1.60, it will use krbookmarks.xml or import it if
          needed.
18. Why doesn't mimetype magic sometimes work inside archives?
    When you enter an archive and press F3 to view a file that has no known
    extension, e.g. README, INSTALL etc.. And if the viewer opens in hex-mode
    instead of the usual mode, than you need to configure: KDE Control Center-
    >KDE components->File Associations->Application->octet-stream, binary
    viewer needs to be removed.
19. Where is Konfigurator, do i need to install the KDE Desktop Enviroment to
    use it?
    Konfigurator is Krusaders configuration module, when you have installed
    Krusader than you have also Konfigurator. For some reason some people think
    it's an other KDE application, but it is not, so you don't need to install
    the KDE Desktop Enviroment to use Konfigurator. When runnig Krusader, use
    Settings->Configure Krusader, and it will start Konfigurator. Please read
    the manual, Krusader has many many configuration options, a lot of things
    can be customized to your needs with Konfigurator.
20. How can I set the look & feel of 2 different users to be the same?
    Presuming that the current setup is the good configuration, you can copy
    the configuration to the other user.
    # cp ~/.trinity/share/config/krusaderrc /home/foo_user/.trinity/share/config
    And when the other user is Root use:
    # cp ~/.trinity/share/config/krusaderrc /root/.trinity/share/config
21. Why doesn't "save last location" work?
    Unfortunately the 1.70.x version contains a bug. The tabs are not saved if
    a "Panels Save Settings=Tabs" item is present in the configuration files.
    The fix is easy:
        * open and edit ~/.trinity/share/config/krusaderrc
        * remove the "Panels Save Settings" item
    and it'll work with the <Last Session> feature in Konfigurator. More info
    can be found in our_forum.
22. Why doesn't the handbook work?
    This error will happen on Debian� (or Debian� based) distro with the
    krusader_1.51-1_i386.deb package. You will see the next error message if
    you try to open the handbook: "The requested help file could not be found.
    Check that you have installed the documentation." To fix it go to /usr/
    share/doc/tde/HTML/en/krusader/, you will see the foo.docbook.gz files.
    Now, you need to extract all these files with root privileges ("File-
    >Unpack" with Krusader) to create foo.docbook files. Now the handbook will
    work. This error is fixed in the krusader_1.60.0-1_i386.deb package and
    higher versions.
General FAQ
  1. How_can_I_report_a_wish,_a_suggestion,_or_a_comment?
  2. How_can_I_send_a_patch?
  3. How_can_I_report_a_bug?
  4. How_can_i_send_good_debug_or_crash_reports?
  5. What_todo_if_the_KDEcrashhandler_sends_no_usefull_backtrace_information?
  6. Does_Krusader_have_a_mailing_list?
  7. Does_Krusader_provide_newsfeeds?
  8. Does_Krusader_have_an_IRC_channel?
  9. How_does_the_Krusader_forum_work?
  10. How_can_I_translate_Krusader_into_my_native_language?
  11. How_can_I_support_Krusader?
  12. Is_there_a_Mac_OS_X_port?
  13. Is_there_a_Windows_port?
  14. Why_is_Konqueror_in_"midnight_commander_style"_not_an_OFM?
  15. Why_should_I_use_an_OFM?
1.  How can I report a wish, a suggestion, or a comment?
    An open source project's greatest strength is derived from getting user
    feedback. That is why we love to hear what you have to say. Your "gripes"
    are our instructions. After about 6 months, programmers can no longer see
    their own mistakes. It's natural. We want the ideas, qritiques, and
    feedback because we all want to make Krusader the best and most useful file
    manager available anywhere.
    The most convenient way to contact us is to use the Krusader_Forum, or the
    krusader-users mailing_lists. For information on what remains to be done
    look at the ToDo_Forum. Adding ToDo items into the ToDo_Forum is for
    developers only, but feel free to post to the New_Features_Discussion/
    Requests_Forum for things that aren't on the ToDo_Forum, but should be. If
    you have a nice feature request, the Krusader Krew will add your request to
    the ToDo_Forum. We review and discuss every submission. For more
    information how the forum works click here.
2.  How can I send a patch?
    It's not easy to write patch guidelines, but here are some.
       1. Patches, new code or new features are always welcome!
       2. Focus only on one problem at a time, so the developers can easily
          understand you, and commit your patch it works.
       3. Preferrably, you can start a discussion with the developers on the
          krusader-devel mailing_lists or on the Krusader_Forum. Unfortunatly,
          we can't apply a patch if the patch is in conflict with the "general
          design" of the Krusader code (read for more instructions in this
          FAQ). Please send only one change request per mail, so that the
          discussion is easier to follow. The modifications should be committed
          step by step, checking each line.
       4. Submit your patch files into our Patch_Tracker, so that all patch
          proposals stay organised and don't get lost, tar.gz archives or diffs
          are usually ok. Do not copy changes into a mail. Most mailers will
          change the white spaces, so that the diff will not apply or the code
          snipped does not diff. In the past, patch mails went lost or
          disorganized in many many mails, so please use the Patch_Tracker,
          thanks!
       5. Use portable solutions, Krusader should run on:
              * All POSIX (Linux�/BSD/UNIX�-like OSes), Solaris&#8482;.
              * All BSD Platforms (FreeBSD�/NetBSD�/OpenBSD�/Mac� OS).
              * KDE 3.3- KDE 3.5 and even on GNOME with KDElibs (for krusader-
                2.x KDE 4) .
              * GCC 2.95 - GCC 4.1
          Architecture changes are made by the team only.
       6. A final note: always keep in mind a patch might be rejected. Either
          it has side effects, which we could not fix or it contradicts with
          the idea behind the patched module. In this sense, a software project
          differs from, let's say a wiki: a software project has to have
          someone to make all the final decisions. Otherwise the software will
          not work. Furthermore: keep in mind that the examination of patches
          might take time, as we all have private lives.
3.  How can I report a bug?
    Bugs?!?!? Well, ok.... We have an online Bug Tracking System.
    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 from
    browsing through the entire Krusader forum, searching for yesterdays bug.
    Please use this system.
    Before reporting a bug, please read the following:
       1. Use the Krusader_Forum's Search function , your bug might be already
          solved . Please DO NOT post new bugs to the Bug_Discussion_Forum
          (except if you are not sure that you have found a bug). We use it for
          bug discussions.
       2. Check if the bug is already posted in the online_bug_list of the Bug
          Tracking System.
       3. If you can't find this bug mentioned, please submit it into the bug
          tracker by clicking the Submit New button in the bug-tracker window.
          Please submit the following issues: the Krusader version used, the
          Linux� distribution + version used, processor type, and as good a
          description of the problem as you can manage.
    Thank you for your co-operation!
    **** Note ****
    If possible, try to do the same operation with Konqueror or another KDE
    application. If you encounter the same problem then it is possibly a
    KIOSlaves or KDE (kdelibs) bug, and not a Krusader bug. Krusader uses the
    KDE libraries and the KIOSlaves for many operations. In some cases you can
    encounter problems if your distribution is incorrectly configured, please
    test it first as explained above.
    **** Note ****
    If you've got bugs to report please do not use KDE's bugzilla http://
    bugs.kde.org/, KDE's Bug Tracking System. Report Krusader bugs directly to
    us.
4.  How can i send good debug or crash reports?
    Usually binary packages that are been used by your distribution do not
    contain debug information. Since we usually only develop and fix Krusader-
    cvs, compile Krusader-cvs in debugmode and install it, than check if the
    bug still exist.
    $ ./configure --enable-debug=full
    Install valgrind, a suite of tools for debugging and profiling Linux�
    programs. Run Valgrind/Krusader
    $ valgrind --tool=memcheck {foo_path}/krusader
    The valgrind tool will write to stdout, what really happens. If you could
    send these informations before the crash, it's almost sure, that we may fix
    or tell you what to do.
5.  What todo if the KDEcrashhandler sends no usefull backtrace information?
    Usually binary packages that are been used by your distribution do not
    contain debug information. Since we usually only develop and fix Krusader-
    cvs, compile Krusader-cvs in debugmode and install it, than check if the
    bug still exist.
    $ ./configure --enable-debug=full
    If the KDEKrashhandler still doesn't provide usefull backtrace information,
    than sometimes a coredump will give better information. Run Krusader, with
    disabled crashhandler.
    $ krusader --nocrashhandler
    On a crash you will get a .core file, usually in your home directory. Run
    gdb, the GNU Project Debugger
    $ gdb -c corefile krusader
    Now type bt to get the backtrace and type q to quit gdb. Often the best
    debug results will be given when using the valgrint tool.
6.  Does Krusader have a mailing list?
    Yes, currently we have 6 mailing_lists. No spam, no bother, just Krusader.
    Feel free to subscribe and unsubscribe.
    Tip. our mailing lists can be browsed online or read with a newsreader, so
    that you don't even need to subscribe to follow the action on the mailing
    lists.
        * Krusader-news is a very low volume list, used for newsletters and
          announcements of new versions or critical bugfixes. The news can also
          be read online at latest_news and in the News_and_Announcements_Forum
          which are basically the same but displayed in another format.
        * Krusader-devel is the developer mailing list (read-only). If you want
          to follow the development of Krusader on the cutting edge, this is
          the list to follow.
        * Krusader-users is the Krusader users mailing list. Here you can ask
          for help and talk with the Krusader users and developers.
        * Krusader-i18n is the translations mailing list.
        * Krusader-doc is the documentation mailing list.
        * Krusader-commits (read-only): when the Krusader Krew commits code
          into CVS, it will be reported in this mailing list. Want to keep
          track? Waiting for a certain feature/bugfix? Follow Krusader's
          development here.
7.  Does Krusader provide newsfeeds?
    Yes, we do. Several newsfeeds in various formats are available. rss-
    filerelease_feed, rss-forumfeed, krusader-news_feed, krusader-devel_feed
    and even additional_feeds by gmane.org. krusader-users_feed, krusader-i18n
    feed, krusader-doc_feed.
8.  Does Krusader have an IRC channel?
    Yes, we do. Feel free to talk to the Krusader Krew and fellow-users via
    freenode.org servers. The server is irc.freenode.org, the channel is
    #krusader. Everyone is welcome.
9.  How does the Krusader forum work?
    In the spirit of freedom of speech, everything that is Krusader related can
    be discussed in our forum. It does not matter if you are a newcomer or an
    advanced user, everyone is welcome. An open source project's 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 and ideas you may have. But
    please remember the following, so that we can maintain some order in the
    chaos.
    If the Documentation, FAQ, Krusader_Forum and Krusader-devel (please use
    the search function ) can't help you, do not hesitate to post on our forum.
    The Krusader Krew or the Krusader community is always available to help
    you.
    Please use the Search function of the Krusader_Forum, your issue may have
    been previously discussed (this allows us to minimize 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 to your problem. If the
    issue is currently being discussed, you can join in the discussion. Some
    questions are asked over and over again, that's why we have created this
    FAQ. This allows us to spend more time developing Krusader.
    The Krusader_Forum is split into seven sections:
        * News_and_Announcements_Forum: all the latest news.
        * NewsLetter_Forum: all newsletters.
        * Bug_Discussion_Forum: discussions about bugs, please DO NOT use the
          forum for bug_reports (except if you are unsure if you have found a
          bug).
        * New_Features_Discussion/Requests_Forum: discussions about new
          features for future Krusader versions.
        * ToDo_Forum here you will find the list of the planned features.
          Registered users will be able to VOTE and COMMENT on the TODO items.
          Here you get the chance to push your favourite features (+3) and
          still prefer certain features over others (+1), if you don't care
          about a feature just simply don't vote on that feature. Unregistered
          users may only browse the ToDo_Forum. The ToDo_ranking_system
          contains the results based on the votes. Adding_ToDo_items or
          removing ToDo items which have been implemented will be done by the
          Krusader Krew.
        * UserActions_Forum: discussions about UserActions. Posting your own
          User Actions is greatly appreciated. We plan to include the best ones
          in the next Krusader releases.
        * General_Discussion_Forum: everything that is Krusader related and
          doesn't belong in the other forums.
    Thank you for your co-operation!
    We provide RSS feeds for our forums. You don't have to check for new posts
    all the time, instead the news will come to you! To make use of them,
    simply point your RSS aggregator to here.
10. How can I translate Krusader into my native language?
    Please read the i18n_page. It's not difficult to translate! Most anyone can
    do it, it just takes some time.
11. How can I support Krusader?
    You can support Krusader in many different ways. Please send us feedback,
    bug_reports, patches, donations, translations, ...
12. Is there a Mac� OS X port?
    Yes, there is Mac� OS X port, but you will not have the all the power you
    would have on Linux�. Please read the Mac�_OS_X_port_section for more
    information. A recommended native file manager for Mac� OS is Disk_Order�
    (shareware).
13. Is there a Windows� port?
    No, but this might change in the future. Please help_us with this project,
    contributions are greatly appreciated. A recommended native file manager
    for Windows� is Total_Commander� (shareware).
14. Why is Konqueror in "midnight commander style" not an OFM?
    The two panels and a commandline are available, all the other stuff like
    OFM_features and the OFM interaction with the user is missing from this
    profile.
15. Why should I use an OFM?
    An Orthodox_File_Manager_(OFM) is much faster than a one panel filemanager
    and faster than the command line. If you would like to know how_Krusader
    feels, there is only one way to discover: install it on your computer and
    use it for a while. If you prefer to waste time and lose productivity,
    continue to use one panel filemanagers which are based on Windows�
    Explorer. Matej Urban&#269;i&#269; has written a blogon why OFM is better
    than a one panel filemanager.