Arch Linux

Llama

Banned

From: St.-Petersburg, Russia

Registered: 2008-03-03

Posts: 1,379

Krusader configuration

Hi,

After upgrading to KDEmod4 I reinstalled Krusader. I noticed that it now lives in /usr/bin rather than in /opt/kde/bin. Soon I discovered two quirks:

(1) F2 opens the console not it the current directory, but always in ~/

(2) A real showstopper: it refuses to handle transparently tar.gz archives. "tar:Protocol not supported by Krusader". Of course, all the settings in "Archives" are OK.

Any ideas?

Llama

Banned

From: St.-Petersburg, Russia

Registered: 2008-03-03

Posts: 1,379

Re: Krusader configuration

Mmm... No ideas at all ?

vexxor

Member

Registered: 2008-07-17

Posts: 45

Re: Krusader configuration

Hi,

After upgrading to KDEmod4 I reinstalled Krusader. I noticed that it now lives in /usr/bin rather than in /opt/kde/bin. Soon I discovered two quirks:

(1) F2 opens the console not it the current directory, but always in ~/

(2) A real showstopper: it refuses to handle transparently tar.gz archives. "tar:Protocol not supported by Krusader". Of course, all the settings in "Archives" are OK.

Any ideas?

I'm having similar problems. The old krusader does exactly what you wrote. So i tried krusader-kde4-svn from AUR, and it solved the problem. Only, now RAR files don't work.

I described it on their bugtracker yesterday...

http://sourceforge.net/tracker/index.ph … tid=106488