# Frequently Asked Questions (&FAQ;)

If you have problems with &krusader; please check the &install_proc_lnk;, your problem may be due to a bad installation.

The &FAQ; is divided into three sections:

- Installation &FAQ; (this page)

- Usage &FAQ; (issues when running/using &krusader;)

- General &FAQ; (bug reports, forum, mailing list, ...)

If you have the feeling that a &FAQ; is missing or if something is not clear to you, please let us know.

## Installation &FAQ;

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 &eg; &kde; libraries, &Qt; libraries, &etc; This means that &krusader; runs on &gnome_url;, &afterstep_url; and other window managers if the aproriate packages are installed on your computer.

You don't need to switch to &kde;; you can still use &gnome_url; or another window manager. btw, you can configure the menu font by running `kcontrol`.

But a lot depends on what you would like to do with &krusader;. You should know that &krusader; uses the &kde; &kioslaves1_url; to access remote file systems, and only a limited number of slaves (bad choice of words slaves) are shipped with &kdelibs_url;, most of the &kioslaves2_url; are bundled with &kdebase_url; (including fish,sftp and tar). But ... if the property-dialog should show EXIF-data for .jpeg's, you need &kde;graphics if you want ID3-infos, you need &kde;multimedia, and so on....

To summarize, if you want a working &krusader; - install &kde;libs. If you want a functional &krusader; then you need &kde;libs + &kde;base. If you need more functionality, then &krusader; needs some more &kde; packages.

Which libraries does &krusader; need to run?

For running &krusader; (&eg; when you have installed &krusader; with a binary RPM) you need less libraries or packages as mentioned in the next question, &eg; you don't need the C-compliler &gcc; it's only needed when you compile &krusader; from source.

Here is a (possibly incomplete) list of the required shared libraries when you run &krusader;:

- kdelibs >= 3.2 libqt3

- libxfree86 libfreetype6 libfontconfig1

- libjpeg62 libpng3 libmng1 zlib1 libstdc++5 libgcc1

- libfam0 libpcre0 glibc libart_lgpl2 libexpat0 libnas2

A complete list of &shared_libdeps_url; is available.

I have followed all steps but `configure` complains about missing libs or headers. What do I need to do?

Please install them. ;-)

Here is a (possibly incomplete) list of the required packages when you 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 (&krusader; v1.50 needs &Qt; 3.x)

- kdelibs kdelibs-devel (&krusader; v1.50 needs KDElibs >= 3.2.x)

- libjpeg62 libjpeg-devel libpng3 libmng1

- fam libfam-devel (&eg; `fam-2.x.x-xmdk.rpm` and `libfam0-devel-2.x.x-5mdk.i586.rpm`)

- zlib1 arts libart_lgpl2 libstdc++5 libpcre0

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; `kdelibs-devel-3.1-58mdk.i586.rpm`) or foo-dev-*.deb for &debian; based distributions. They most likely come with your distribution.

If you can't find the needed package, use the &rpmfind_url; 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.

How do i compile &krusader; when i'm using a 64 bit processor ?

We don't have much experiance and feedback with 64 bit processors yet but our &kruforum_url; is a good start. Please look here.

I have downloaded the Source RPM `krusader-x.xx.dist.src.rpm` What 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 before installing:

       $ rpm -i --test  </path/to/rpmfile> krusader-x.xx.dist.rpm

   If the prompt returns without any message, than 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;.

For more information about RPM, take a look at the &maxrpm_url;. This book is very good but it dates from the year 2000, so some issues are obsolete/changed/improved now. If you know a better (or updated) RPM book on the internet please let me know.

I'm trying to install binary foo (RPM or DEB package), but it fails. What's wrong?

Since we only provide (and use) the source, we don't know. Please test the binary RPM before installing:

    $ rpm -i --test  </path/to/rpmfile> krusader-x.xx.dist.rpm

If the prompt returns without any message, than everything is OK.

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;.

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.

I can't find a RPM or DEB package for &krusader;, What now?

Did you take a look at the &URL;'s on the &install_proc_lnk; page? Yes, and nothing found? Then you will have to compile &krusader; from source :) Even if you think that you have no skills, you will probably succeed in compiling &krusader;! We provide a very detailed installation procedure. This howto allows that even newcomers will be able to compile &krusader; from source, even if they have never done a compilation from source before. Feel free to post a &help_request_lnk; if you encounter problems.

I've installed &krusader;, but when I start it, only the "Help" menu appears. Why?

In this case only the "Help" menu is visible and all the other menu items like &eg; "File" and "Mark" are gone. 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_kde3/krusader/krusaderui.rc` to `$KDEDIR/share/apps/krusader/krusaderui.rc` and `~/.kde/share/apps/krusader/krusaderui.rc` and re-run &krusader;. If you have compiled &krusader; from sources this is often caused when the &kdeqtdir_lnk; environment variables are not right set, the result is that the `krusaderui.rc` file is installed in a wrong directory. Please also read the next question.

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 `~/.kde/share/apps/krusader/krusaderui.rc`. If Krusader was previously installed on your computer, and you install a newer &krusader; version the `~/.kde/share/apps/krusader/krusaderui.rc` file must be replaced with the newer version.

The first line of `krusaderui.rc` contains the version number. After installing a newer &krusader; stable version, &kde; will automatically replace the old `~/.kde/share/apps/krusader/krusaderui.rc` 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".

If you install a CVS or beta version and if &krusader; was previously installed on your computer then you should delete the `krusaderui.rc` file in your home directory to activate the new menu entries $ ``rm` `~/.kde/share/apps/krusader/krusaderui.rc``

If the `~/.kde/share/apps/krusader/krusaderui.rc` file is too old, 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.

When I run `make` it complains about `libfam.la`

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;-&Linux; 9.2 with the default settings, this package is not installed. If you need more information take a look at &missing_libs_lnk;.

&debian; complains about &Qt; when running `./configure`

This problem occurs when you use &gcc; 2.95, you will need to install &gcc; 3.2 (or higher). You need also 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 &debian_qt_a_url; and at the &debian_qt_b_url; on how to build a &Qt;/&kde;3 application on &debian;.

I have a `libGLcore.so.1` compile error after using the &nvidia; installer

This problem occurs when you use the &nvidia; installer and not the official &nvidia; packages of your distribution. &krusader; is based on &Qt; 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 doesn't do its job 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. The second solution is a (bad? :) hack, and also the exact commands depends on the used distribution and the version of the &nvidia; driver (6111 in this example), but it should be 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

I am having trouble compiling and installing &krusader;, how do I send a help request?

Please read our detailed installation procedure and the &faq_lnk;. If you can't find a solution to your problem then feel free to post a help request at our &krusader; forum. But before posting a help request at our &krusader; forum, please regard the following:

1. Use the &kruforumsearch_url; function of the &forum_lnk; , 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.

   If you give us the error messages (&eg; `make` 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.

3. Post a help request with the information of the previous point at our &krugenforum_url;.

Thanks for your cooperation!

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. Follow the next steps to build an RPM.

Never, ever build RPMs when logged in as root. Mistakes in building packages (&eg; 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 `kusader1.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, ... (please read the comments in `kusader.spec`). 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 binaryRPM in `/usr/src/RPM/RPMS/i586` (depending on your architecture) and a sourceRPM in `/usr/src/RPM/SRPMS/` &eg; `krusader-1.50-beta1.suse91.i586.rpm` and `krusader-1.50-beta1.suse91.src.rpm`

7. If it 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.

## Usage &FAQ;

When I try to mount/unmount my cdrom/floppy, &krusader; says something about supermount, what's this about?

Supermount is a daemon which handles mounting/unmounting of removable filesystems for you. Just insert a floppy, and do ``cd` `/mnt/floppy`` supermount will do the mount for you automatically and transparently. All this is great, however, supermount manipulates the system into thinking that the floppy/cdrom 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 floppy in the drive? 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 ;-).

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?

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 a lot better: when downsizing the buttons will look like 'F5 ..py', a tooltip will give the complete text. The minimum is 45 for pixels each button, that should give a minimum width of about 500 pixels and seems reasonable to us.

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 not shown.

The bad news is that we're not sure why, but it seems that `fam` (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 fam, &krusader; will automatically revert to its internal 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.

Samba ISO 8859-x codepage / what to do if &krusader; does not read shared directories containing national 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 it properly, so this step must be done with a text editor.

&krusader; reports "krarc:... protocol not supported" error at opening an archive file.

Solution: install the krarc slave properly:

Copy the `kio_krarc.so`, `kio_krarc.la` files into `$KDEDIR/lib/kde3`

Copy the `krarc.protocol` file into `$KDEDIR/share/services`

or the directory where the KIO slaves are placed in your &Linux; distribution.

When I try to establish an &FTP; connection, I get an error message after 'Connect OK' saying 'Could not connect to host'.

You are probably behind a firewall/proxy and haven't enabled "Passive Mode". Enable "Passive &FTP;" through &kde;'s &kcontrolcenter; and try again. KDE Control Center Network Preferences , "Enable Passive Mode (PASV)" has to be checked.

I get "FTP protocol not supported by &krusader;" error at trying to open a remote &FTP; directory.

The reason for 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 &kcontrolcenter;. Modify the proxy setting to not use &HTTP; proxy and &FTP; will work.

How can I disable the default sounds &eg; 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; &kcontrolcenter; (kcontrol): KDE Control Center Sound & Multimedia System Notifications , Event Source: "KDE System Notifications" and uncheck sound items you don't like.

## General &FAQ;

Where can I report a wish, a patch 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. The most convenient way is to use the &forum_lnk;. For information on what remains to be done look at the &todoforum_url;. Adding ToDo items into the &todoforum_url; is for developers only, but feel free to post to the &featureforum_url; for things that aren't on the &todoforum_url;, but should be. If you have a nice feature request, the &krusader; Krew will add your request to the &forum_lnk;. For more information about the forum click here . You can reach us by &mail_url; or drop us a note in our &krusader; Forum.

Where can I report a bug?

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 the long time needed to browse the entire &krusader; forum, searching for yesterdays bug. Please use this system.

Before reporting a bug, please read the following:

1. 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.

2. Check if the bug is already posted in the &online_buglist_url; 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, and a good description of the problem.

Thanks for your cooperation!

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 &kioslaves1_url; or &kde; (kdelibs) bug, and not a &krusader; bug. &krusader; uses the &kde; libraries and the &kioslaves2_url; for many operations. In some cases you can encounter problems if your distribution is incorrectly configured, please test it first as explained above, thanks!

Does &krusader; have a mailing list?

Yes, we have 3 mailing lists. No spam, no bother, just &krusader;. Feel free to &mailing_subscribe_url;.

Tip. our mailing lists are archived and with the &URL;'s below you can view them with a browser, so that you don't even have to subscribe to see the mailing lists.

- &krunews_url; is used to notify &krusader; users about new releases, major bugfixes &etc; . The news can also been read online at &krulatestnews_url; and in the &newsforum_url; who are basically the same but displayed in another format.

- &krucommits_url; when the &krusader; Krew commits code into CVS, it will be reported into this mailing list. This allows you to follow the &krusader; development ... live! Want to keep track? Waiting for a certain feature/bugfix?

- &krudevel_url; is the developer mailing list of the &krusader; Krew. If you are considering to join the &krusader; Krew or if you want to follow the development on the bleeding edge, this is the place to be!

Does &krusader; have a IRC channel?

Yes, we have. Feel free to talk to the &krusader; Krew, and of course fellow-users via &freenode_url; servers. The server is irc.freenode.org, the channel is #krusader. Everyone is welcome.

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 that you are a newcomer or an advanced user, everybody 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 you may have. But please remember the following, so that we can maintain some order in the chaos. ;-)

If the Documentation, &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.

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 these issues we have the made the &faq_lnk; ;-) This also allows us also to spend more time in developing &krusader;.

The &kruforum_url; is split into six sections:

- &newsforum_url; all the latest news.

- &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).

- &featureforum_url;: discussions about new features for future &krusader; versions.

- &todoforum_url; 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 &todoforum_url;. The &todoranking_url; 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.

- &useractionsforum_url; discussions about &useractions_lnk;. Posting your own UserActions is greatly appreciated. We plan to include the best ones in the next &krusader; releases.

- &krugenforum_url;: everything that is &krusader; related and doesn't belong in the other forums.

Thanks for your cooperation!

We are providing 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 &rss_url;.

How can I translate &krusader; to my native language?

Please read the &i18nhowto_url;. It's not difficult to translate! Everyone can do it, it just takes some time.