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™ 3.3.5 and NOT Krusader. It seems that Qt™ 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™ 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 or a higer version, depending on your distribution. More information is available on our website.

Supermount is a daemon which handles the 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. 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.

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™-mt (the multi threaded version of the Qt™ 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.

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.

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'

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)
          

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.

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.

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

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:

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.

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.

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.

It's explained in the remote connections chapter.

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.

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.

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:

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.

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.

Presuming that the current setup is the good configuration, you can copy the configuration to the other user.

# cp ~/.kde/share/config/krusaderrc /home/foo_user/.kde/share/config

# cp ~/.kde/share/config/krusaderrc /root/.kde/share/config

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:

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