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 do not hang the entire application event loop, but we do not think that the time is right for adding threads, we are not sure that *all* the KDE Frameworks™ 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 Settings → Show FN Keys Bar and you will 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.

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)
          

You can try to configure smb.conf with appropriate System Settings module.

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 does not work, backup your XDG_CONFIG_HOME/krusaderrc (default is $HOME/.config/krusaderc) configuration file and remove it from this location. Restart Krusader, Krusader will now start the first start configuration wizard, follow these guidelines.

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 Plasma™ and not by Krusader. To associate the jar extension:

This problem often occurs when you are behind a firewall or proxy. Open System Settings → Network → Settings → Connection Preferences, Enable Passive Mode (PASV) has to be turned on or off, depending on its 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 System Settings. 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 do not allow a rename operation. You can solve this by unchecking the checkbox Mark partially uploaded files in Plasma™ System Settings. The check box is located at Network → Settings → Connection Preferences.

It is explained in the remote connections chapter.

The media:/ protocol was removed since KDE 4. Please use mtp:/ protocol instead.

Those are the default Plasma™ System sounds, and not related to Krusader. If you want to disable them globally open your Plasma™ System Settings ( systemsettings): Personalization → Notifications → Manage Notifications, Event Source: "Plasma Workspace" and uncheck sound items you do not like.

Use our Bookmark Manager. Use a remote URL and bookmark it.

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 System Settings → File Associations → Application → octet-stream, binary viewer needs to be removed.

Konfigurator is Krusaders configuration module, if you have installed Krusader then you have also Konfigurator. For some reason some people think it is an other Plasma™ application, but it is not, so you do not need to install the full fledged Plasma™ to use Konfigurator. When running 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 ~/.config/krusaderrc /home/foo_user/.config

And when the other user is Root use:

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

In order to change properties of the embedded terminal emulator of Krusader: you can right-click on it and choose an option, and if you don't find there what you are looking for, you can use the Settings menu of Konsole (because Krusader uses a Konsole KPart for its embedded terminal). In that menu, other items are seen (like "Manage Profiles...").