You are not logged in.

Dear visitor, welcome to KDE-Forum.org. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

1

Tuesday, May 4th 2004, 1:15pm

Ark can't fork a decompressor?

I just upgraded to KDE 3.2.2. I'm running PCLinux. Now when I try to extract a tar or bz or bz2 archive using the "extract here" command in KDE, I get a message "Error, I can't fork a decompressor". Anyone know how I might fix this? It always worked fine before the upgrade.

m4ktub

Intermediate

Posts: 257

Location: Lisbon, Portugal

Occupation: Software Engineer

  • Send private message

2

Tuesday, May 4th 2004, 6:58pm

Maybe ark tries to start the decompression tool with wrong arguments (because of different expected versions). You can try to upgrade your decompression tools.

3

Wednesday, May 5th 2004, 3:02am

I've got the newest versions of all the decompression tools. Tar works fine from the command line. I've heard rumor that Ark is broken in SuSE also? I'm wondering if it's a KDE issue or not. I'm running PC Linux OS.

4

Wednesday, May 5th 2004, 8:01pm

I have the exact same problem with SUSE 9.1... anybody any thoughts?

5

Friday, May 7th 2004, 12:26am

whoohaw me too

I get the same problem too, and yes, it's broken in SuSE 8.2 as well. Happened just after I installed 3.2.2 so I can only assume it's that...

First of all, this may sound dumb, but what the heck is forking anyway?

I tried to actually start up Ark without using the service (right click) menu, and opening any archive file gets the same result. So it's definitely independent of the service menu aspect. Tar does seem to work via commandline...

Luckily konqy gives us the option to browse into an archive and copy stuff out of there, but that's a PITA and I'd rather use ark...

6

Friday, May 7th 2004, 3:31pm

Bug Reported?

I've looked through the Bug DB at KDE.org and haven't found anything. Has anyone reported this bug yet? I don't want to end up reporting it if someone else has...

7

Friday, May 7th 2004, 11:01pm

Re: whoohaw me too

Quoted

Original von shock_ez

...First of all, this may sound dumb, but what the heck is forking anyway?...

Forking is a way of creating a new "child" process from an existing "parent" process which "inherits" certain properties from that parent and assigned a different PID (Process ID number)..................In KDE, when you start an app, it is usually a child process started by 'kdeinit', where 'kdeinit' is a single parent process that will spawn the needed process for the app being started................To see what I mean, run the command 'kpm' (either from the "Run Command..." dialog box or from konsole). When the Process Table window pops up, place a check next to "Tree" at the bottom. Scroll down until you see "kdeinit". There, you should see a bunch of processes branching from "kdeinit". These are the forks, or "child" processes, started by "kdeinit". :)
How long a minute is depends on which side of the bathroom door you're on.

8

Monday, May 10th 2004, 6:27pm

Indeed, that was a stupid question of me to ask.

Has anyone managed to get to the bottom of the ark forking bit?

Has anyone reported the bug?

9

Monday, May 10th 2004, 9:04pm

I found this bug report which says it has something to do with the source file, tar.cpp:

Bug 79713

According to LinuxPackages, there's supposed to be a fix for the ark problem, a patch for kdeutils:

kde 3.2.2


Sorry, but I don't know where to find the patch :(
How long a minute is depends on which side of the bathroom door you're on.

10

Monday, May 10th 2004, 10:41pm

dang...

Well, you can find the package here: http://www3.linuxpackages.net/Slackware-9.1/pcxz/kde/3.2.2/

HOWEVER they are listed as Slackware 9.1 packages. I run SuSE 8.2. They're source tars as far as I can tell...but I'm loathe to try to install anything that's listed as any distro other than my own distro.

Would I blow anything up if I used the package as listed in the URL above?

:?

11

Tuesday, May 11th 2004, 12:09am

Those Slackpacks are not source, but precompiled binaries packed for Slackware (Slackware uses TGZ extension for packages, like BSD does)....................I only used that URL to show that there is supposed to be a patch for kdeutils to fix the ark problem..........

Theoritically, those pkgs might work, but it would depend on where SuSE puts the kde installation directory (Slackware uses /opt/kde).................and then there's the matter of creating the necessary symlinks for the libraries................You would need Slackware's "pkgtools" binaries to make it work properly..........

In short, you're better off compiling from source, but then you'd need to find the patch..........and I don't know where to find it..... :(


-------------------------------------
BTW............They might have a patched package for SuSE already.........try looking in Rpmfind........
How long a minute is depends on which side of the bathroom door you're on.

12

Tuesday, May 11th 2004, 3:02am

Okay....................I found the patch for those interested in compiling KDE-3.2.2:

tar.cpp.diff

This patches the "kdeutils" source tree................That is, unpack the kdeutils-3.2.2.tar.bz2 source tarball and apply the patch before compiling....... :)
How long a minute is depends on which side of the bathroom door you're on.

13

Tuesday, May 11th 2004, 1:01pm

Quoted

Original von thegeekster


This patches the "kdeutils" source tree................That is, unpack the kdeutils-3.2.2.tar.bz2 source tarball and apply the patch before compiling....... :)


So you mean to say get the kdeutils-3.2.2.tar.bz2 package from the same link, right? I had downloaded the daily build from kde.org but I imagine I should d/l the package from the same source as where the patch came, no?

Sorry for the barrage of rather stupid questions...

14

Tuesday, May 11th 2004, 1:39pm

No........this patch is for the KDE-3.2.2 build, not the CVS..................you can download the 3.2.2 source from one of the KDE mirrors (look in the stable/3.2.2/src directory)

But, again, SuSE might have already come out with a patched RPM..............worth checking out unless you want to build from source :)

And the only stupid questions are the ones never asked ;)
How long a minute is depends on which side of the bathroom door you're on.

15

Tuesday, May 11th 2004, 2:28pm

:oops:

So um...to apply the patch, I just put it in the unpacked kdeutils dir and run it? ./tar.cpp.diff ?? Or do I put the tar.cpp.diff into ../kdeutils-3.2.2/ark and run it? Or do I just plop it in there and during configure/make the patch will be applied? I've never gone about applying a patch in linux before, I'm a bit of a n00b.

Sorry...ugh...

I see there is a tar.cpp file in the ark dir but I don't want to do anything stupid ... like paste things in where I shouldn't or something like that ... :?

16

Tuesday, May 11th 2004, 2:41pm

To apply the patch, just put the patch (tar.cpp.diff) and the tarball (kdeutils-3.2.2.tar.bz2) in the same directory and unpack the tarball (tar -xjvf kdeutils-3.2.2.tar.bz2). Now 'cd' into the directory created from unpacking the tarball (cd kdeutils-3.2.2) and run this command: [code:1]cat ../tar.cpp.diff | patch -pl [/code:1]
This is assuming the diff file is named tar.cpp.diff.....That's it's. :)
How long a minute is depends on which side of the bathroom door you're on.

17

Tuesday, May 11th 2004, 10:48pm

This sucks!

So I applied the patch, configured, everything was happy, and now something seems to be missing during make install:

...
test -z "/opt/kde3/lib/kde3" || mkdir -p -- . "/opt/kde3/lib/kde3"
/bin/sh ../libtool --silent --mode=install /usr/bin/install -c -p 'ark.la' '/opt/kde3/lib/kde3/ark.la'
/usr/bin/install: cannot stat `.libs/ark.lai': No such file or directory
make[3]: *** [install-kdeinitLTLIBRARIES] Error 1
make[3]: Leaving directory `/home/Justin/Storage/Downloads/Original_Source/kdeutils-3.2.2/ark'
make[2]: *** [install-am] Error 2
make[2]: Leaving directory `/home/Justin/Storage/Downloads/Original_Source/kdeutils-3.2.2/ark'
make[1]: *** [install-recursive] Error 1
make[1]: Leaving directory `/home/Justin/Storage/Downloads/Original_Source/kdeutils-3.2.2/ark'
make: *** [install-recursive] Error 1

Is this because I didn't compile from source originally (I used SuSE 8.2 rpms)??

18

Wednesday, May 12th 2004, 3:25am

Re: This sucks!

Quoted

Original von shock_ez

So I applied the patch, configured, everything was happy, and now something seems to be missing during make install:

.....

Is this because I didn't compile from source originally (I used SuSE 8.2 rpms)??

Possible.............Did you compile this while still in KDE?
How long a minute is depends on which side of the bathroom door you're on.

19

Thursday, May 13th 2004, 1:46am

possibly...

Yeah I was dumb and did it while still in KDE. I haven't gotten back to that machine yet to try it while not in KDE, but the error I'm looking at doesn't seem like it's the kind of thing that would come up if I were still in KDE. Then again, maybe I should just shut up and try it...

:oops:

20

Thursday, May 13th 2004, 4:25am

LOL....................Have you ever taken a look at BLFS (Beyond Linux From Scratch)?............Has good info on compiling KDE from source. Here's the link to the KDE section..........Definitely worth checking out.... :)
How long a minute is depends on which side of the bathroom door you're on.