Hi All, I recently updated some 8.2 and 9.0 systems to KDE3.2.2 (from ftp.mirror.ac.uk) On all boxes, the KDE ark application fails to open downloaded .tar.gz (or .tgz) archives with the message "I cannot fork a decompressor." KArchiver has no trouble with the same files so I know they are not damaged. However, ark is happy to create a new archive, and then decompress it. Any idea what might be causing this? Cheers Dylan -- "I see your Schwartz is as big as mine" -Dark Helmet
On Friday 30 April 2004 00.13, Dylan wrote:
Hi All,
I recently updated some 8.2 and 9.0 systems to KDE3.2.2 (from ftp.mirror.ac.uk) On all boxes, the KDE ark application fails to open downloaded .tar.gz (or .tgz) archives with the message "I cannot fork a decompressor." KArchiver has no trouble with the same files so I know they are not damaged. However, ark is happy to create a new archive, and then decompress it.
Any idea what might be causing this?
Does it put any error messages in $HOME/.xsession-errors (or, if you use startx, $HOME/.X.err)?
On Thursday 29 Apr 2004 23:17 pm, Anders Johansson wrote:
On Friday 30 April 2004 00.13, Dylan wrote:
Hi All,
I recently updated some 8.2 and 9.0 systems to KDE3.2.2 (from ftp.mirror.ac.uk) On all boxes, the KDE ark application fails to open downloaded .tar.gz (or .tgz) archives with the message "I cannot fork a decompressor." KArchiver has no trouble with the same files so I know they are not damaged. However, ark is happy to create a new archive, and then decompress it.
Any idea what might be causing this?
Does it put any error messages in $HOME/.xsession-errors (or, if you use startx, $HOME/.X.err)?
Nope :(( Dylan -- "I see your Schwartz is as big as mine" -Dark Helmet
On Thu, 2004-04-29 at 23:17, Anders Johansson wrote:
On Friday 30 April 2004 00.13, Dylan wrote:
Hi All,
I recently updated some 8.2 and 9.0 systems to KDE3.2.2 (from ftp.mirror.ac.uk) On all boxes, the KDE ark application fails to open downloaded .tar.gz (or .tgz) archives with the message "I cannot fork a decompressor." KArchiver has no trouble with the same files so I know they are not damaged. However, ark is happy to create a new archive, and then decompress it.
Any idea what might be causing this?
It's a known bug in kdeutils3 listed as a "grave regression", I think, at kde.org. No more ark pro tem. Another one is in kdesu. Patches for both are available from the 3.2.2 page at kde.org, though you'll need to download and recompile the src.rpms, I guess, as so far I haven't seen any revised rpms around. :) Fish
participants (3)
-
Anders Johansson -
Dylan -
Mark Crean