Version: 2.5.1 (using KDE KDE 3.4.1) Installed from: Fedora RPMs OS: Linux My system has a small local drive. I have a 4GiB tar.gz file that I wish to extract but there isn't space on the local system so I copied it to a removeable 80GiB drive. When I tried to extract the contents using the context-menu in Konqueror it appeared to copy the large file back to the local drive (into /tmp) and then try to extract the contents. It crashed trying to do this as I ran out of space. Sadly this was whilst I had an audience so that made it more painful. I resorted to cd'ing to the removeable folder and doing 'tar -xvzf' which worked very nicely as I was able to utilise some of the files whilst the rest of the archive was being extracted. I'm not sure why ark doesn't extract files on the fly into the target folder - in my particular use case it meant ark wasn't really the right tool for the job. I'd like to avoid having to train my users on using tar from the command line when ark gets us so close to being a replacement. I accept that you may have made a design decision to have things copied into /tmp but in my world of dynamic disk configurations this didn't work out too well. I noted that "Bug 100556: configure default extract folder" may be related to this bug, but in my case I'd have to keep altering the temporary folder (if that's what the bug is referring to). As ever, please let me know if you'd like more information. Thanks
*** Bug 110622 has been marked as a duplicate of this bug. ***
Bug 113384 and this one probably have the same root cause and solution.
*** Bug 137394 has been marked as a duplicate of this bug. ***
The problem reported has been fixed as of KDE 4.2.2 (and trunk), ark now doesn't copy the archive to a temporary file before extracting. However, I'm marking it as NEW instead of FIXED because it still copies the archive when adding or deleting files from tar archives.
*** Bug 111807 has been marked as a duplicate of this bug. ***
*** Bug 146100 has been marked as a duplicate of this bug. ***
Looks good to me. I only see slave-socket activity when I use Ark from Dolphin. Notably the sockets are deleted before actually doing the extraction so it doesn't look like they are being used (which is obviously good). [david@maple ~]$ inotifywait --recursive --monitor /tmp Setting up watches. Beware: since -r was given, this may take a while! Watches established. /tmp/ksocket-david/ CREATE arkk19270.slave-socket /tmp/ksocket-david/ OPEN arkk19270.slave-socket /tmp/ksocket-david/ CLOSE_WRITE,CLOSE arkk19270.slave-socket /tmp/ksocket-david/ DELETE arkk19270.slave-socket /tmp/ksocket-david/ CREATE arkk19270.slave-socket /tmp/ksocket-david/ DELETE arkk19270.slave-socket /tmp/ksocket-david/ CREATE arkJ19270.slave-socket /tmp/ksocket-david/ OPEN arkJ19270.slave-socket /tmp/ksocket-david/ CLOSE_WRITE,CLOSE arkJ19270.slave-socket /tmp/ksocket-david/ DELETE arkJ19270.slave-socket /tmp/ksocket-david/ CREATE arkJ19270.slave-socket /tmp/ksocket-david/ DELETE arkJ19270.slave-socket /tmp/ksocket-david/ CREATE dolphinY31781.slave-socket /tmp/ksocket-david/ OPEN dolphinY31781.slave-socket /tmp/ksocket-david/ CLOSE_WRITE,CLOSE dolphinY31781.slave-socket /tmp/ksocket-david/ DELETE dolphinY31781.slave-socket /tmp/ksocket-david/ CREATE dolphinY31781.slave-socket /tmp/ksocket-david/ DELETE dolphinY31781.slave-socket Thank you. I'll leave it as "NEW" as it looks like you've got some loose ends you'd like to chase up.
Changing the default assignee for currently open Ark bug reports to me.
Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved.
As the original reporter of the bug, I'm quite comfortable with the revised behaviour and the caveats about other problematic scenarios aren't applicable to me. Thanks for the work to fix it folks.