Chapter 6. Frequently Asked Questions (FAQ)

If you have problems with Krusader please check the installation procedure, your problem maybe due to a bad installation.

The FAQ are divided in three sections:

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

Installation FAQ

1. Does Krusader needs KDE to run?
2. Which libraries needs Krusader to run?
3. I have followed all steps but configure complains about missing libs or headers. What do I need to do?
4. I have successfully installed Krusader from source. Everything went fine but I can't start it. What's going wrong here?
5. I have downloaded the Source RPM krusader-x.xx.dist.src.rpm What now?
6. I'm trying to install binary foo (RPM or DEB package), but it fails. What's wrong?
7. I can't find a RPM or DEB package for Krusader, What now?
8. I've installed Krusader, but when I start it, 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
11. Debian complains about Qt when running ./configure
12. I have a libGLcore.so.1 compile error after using the NVIDIA installer
13. I am having trouble compiling and installing Krusader, how do I send a help request?
14. How can i build a RPM package for Krusader?
1.

Does Krusader needs 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 provides 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 or other window managers if the aproriate libraries are installed on your computer.

2.

Which libraries needs Krusader to run?

For running Krusader (e.g. when you have installed Krusader with a binary RPM) you need less libraries or packages as mentioned in the next question, e.g. 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 library dependencies is available.

3.

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 (e.g. 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 (e.g. kdelibs-devel-3.1-58mdk.i586.rpm) or foo-dev-*.deb for Debian® based distributions. They most likely come with your distribution.

Tip

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

I have successfully installed Krusader from source. Everything went fine but I can't start it. What's going wrong here?

  • The Krusader binary is obviously not in your PATH.

  • Use the find command to locate the binary.

    $  find /usr /opt -name  krusader -type f -perm +111
    /usr/local/bin/krusader
    Here, the binary somehow made it into /usr/local/bin. It is most likely, that your KDEDIR enviroment variable wasn't set properly, look at KDEDIR - QTDIR for more info.

  • If you don't want to recompile Krusader, just add /usr/local/bin to your PATH. To do this for all users, append the following line in your /etc/profile file (or any other file your shell sources at startup).

    $ export  PATH=$PATH:/usr/local/bin

5.

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.

Tip

For more information about RPM, take a look at the Maximum RPM Book. 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 let me know.

6.

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.net or KDE-APPS.org. If you still can't find a package for your Linux® distribution, we recommend searching for it with rpmfind.net or rpmpbone.net.

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.

7.

I can't find a RPM or DEB package for Krusader, What now?

Did you take a look at the URL's on the installation procedure 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 if you encounter problems.

8.

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 e.g. "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 KDEDIR - QTDIR 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.

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 ~/.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.

10.

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 FAQ missing libs or headers.

11.

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 in our forum and at the instructions on how to build a Qt™/KDE3 application on Debian®.

12.

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

13.

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. But before posting a help request at our Krusader forum, please regard the following:

  1. Use the Search function of the Krusader Forum , your problem might be solved or discussed already.

  2. If you can't find a solution, please take a note of the following issues:

    • the used Krusader version

    • the used Linux® distribution + version

    • 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 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 General Discussion Forum.

Thanks for your cooperation!

14.

How can i build a 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.

Warning

Never, ever build RPMs when logged in as root. Mistakes in buildings packages (e.g. a bad krusader.spec file) can serious damage 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/ e.g. 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 final: test the RPM before sending it in.