Version: (using KDE 4.3.0) Compiler: x86_64 architecture OS: Linux Installed from: Ubuntu Packages Currently, when you try to extract a file to a device with no enough space left Ark just get stuck while the message "extracting all files" and the progress bar continue moving, as if it really were doing something. The user get no error message and, although he can wait, the operation will never be completed. Ark should abort the operation when the device gets full and report the problem to the user. Additionally, it would be nice if Ark let the user to cancel the currently running operation. Please note that this happens with zip archives. With tar.gz archives Ark just extracts a 0 bytes file and DOESN'T report the problem to the user.
I confirm this bug on Gentoo and ark 2.13. It takes me 5 minutes to check what is going on while i am not novice user. I think beginner could have great problem to investigate what is wrong.
*** Bug 237653 has been marked as a duplicate of this bug. ***
I've reported bug 237653, duplicate of this. I think what's happens it's the command line utilities shows messages like "the disk is full, try again? abort?", and ark do not detect this.
This appears to be fixed in KDE trunk. I tried recreating it and work on it as a junior job, but it does not seem to be a problem anymore.
Are you sure? I've created a 5MB ext2 file system on a file here, mounted it and tried to extract a 7MB zip file to it. Ark kept showing "Extracting all files" while there was a message on the terminal saying "/tmp/test-partition-dir: write failed, filesystem is full".
For now, marking it as NEW as I've just been able to reproduce it.
Indeed you are right. The bug still exists. I will try and have a go at it.
Changing the default assignee in the currently open Ark bug reports to me.
*** Bug 308560 has been marked as a duplicate of this bug. ***
I'd like to work on this bug!
*** Bug 360763 has been marked as a duplicate of this bug. ***
Git commit 7f65f9112b6574fc6477c240bea6c138a1494dbb by Ragnar Thomsen. Committed on 20/03/2016 at 17:55. Pushed by rthomsen into branch 'Applications/16.04'. Handle "no space left" messages from cliplugins Previously, Ark didn't handle "no space left" error messages from the cliplugins. This resulted in either the gui being "busy" continously (clizip), or that the user didn't get any indication that there was a problem extracting the archive (cli7z and clirar). This commit adds a pattern (DiskFullPatterns) for catching these errors. An errorbox is then displayed to the user. Some of the programs used in the cliplugins, such as 7z v9.38, doesn't output a specific message, but then a generic "Extraction failed" message is displayed instead. Related: bug 206385 FIXED-IN: 16.04.0 Differential Revision: D455 M +10 -1 kerfuffle/cliinterface.cpp M +5 -0 kerfuffle/cliinterface.h M +2 -1 plugins/cli7zplugin/cliplugin.cpp M +2 -1 plugins/clirarplugin/cliplugin.cpp M +2 -0 plugins/clizipplugin/cliplugin.cpp http://commits.kde.org/ark/7f65f9112b6574fc6477c240bea6c138a1494dbb
Extracting from the Dolphin context menu with Ark 16.04.3 to a ramdisk (tmpfs directory) just says "Extraction failed because of an unexpected error." when it reaches the size limit.