Version: (using KDE KDE 3.3.0) Installed from: Gentoo Packages You'll end with one completely extracted archive, while the other ones stopped at X percent. I'm not sure, if this is a konqueror, kio or ark part issue.
The same thing happens when creating an archive in KDE 3.4. I don't recall this happening with KDE 3.2. Open Konqueror, right-click a directory, choose Compress > Compress As > ___.tar. While it's compressing, right-click another directory and do the same thing. Repeat for several directories. After a few moments, all the archives stop, but they are incomplete. There is *no* warning to the user whatsoever about this. If the user weren't paying attention, he/she could assume that the archives are complete and delete the original files. I think this should be marked with severity "grave," and "data loss" added to the summary.
Has anyone looked at this yet? It makes Ark almost completely unusable. If I accidentally forget about this bug and begin extracting or creating more than one archive at a time, they're all instantly ruined as soon as one finishes. I could save far more time (not to mention make the operation much safer) just opening a terminal and using tar instead. :-( I just tried this with KDE 3.4.2, and the problem is still there. Compress more than one file at a time using the Konqueror context menu. You'll notice that the file sizes are unusually small. Try to extract the archives, and Ark gives errors and crashes because the archives are corrupt (incomplete).
*** Bug 95443 has been marked as a duplicate of this bug. ***
Are you really sure these are the same bugs ?
Both of the bug reports state that when using right click to decompress a lot of files only one (or some) of theme are actually decompressed. I think #95443 is a duplicate
*** Bug 119864 has been marked as a duplicate of this bug. ***
*** Bug 107760 has been marked as a duplicate of this bug. ***
*** Bug 65584 has been marked as a duplicate of this bug. ***
*** Bug 128174 has been marked as a duplicate of this bug. ***
*** Bug 128173 has been marked as a duplicate of this bug. ***
*** Bug 128376 has been marked as a duplicate of this bug. ***
*** Bug 136795 has been marked as a duplicate of this bug. ***
I can comfirm that this is still in ark 2.6.4 in kde 3.5.5 Extracting more than one rar(that's what i tried at least) at a time will give you at least 50% corruption of the files. I have lost several files to this bug because i have deleted the archives only to later notice that the extraction wasn't successfull. I think this bug should be upgraded from normal to SEVERE/DATA LOSS. Also: If you hit cancel in one of the two extaction dialogs both will close. I'm using: * app-arch/unrar Latest version available: 3.6.8 Latest version installed: 3.6.8 Size of files: 122 kB Homepage: http://www.rarlab.com/rar_add.htm Description: Uncompress rar files License: unRAR
It does not happen when you choose extract to.... (which will bring up the actual ark window instead of just the "Extracting files..." window), only when you choose "Extract here"
OK, i've done some more investigation and it happends for all types of archives but only when you choose "Extract here" and "Extract to ArchiveName/"
When the first one closes, the other windows closes at the same time, but the extraction (atleast when its .zip files that are being extracted) doesnt stop until the file it is working on is finished.
Also, the bug is in ark, not arkplugin
The bug also apears when compressing two archives at the same time. The problem seems to be that both extractions/compressions are being run from the same ark process, and when one is finished it tells ark to close (thereby killing the other extraction/compression)
Commenting out the line 'close();' inside MainWindow::window_close() in mainwindow.cpp stops the bug from appearing but it also means that the windows won't close automatically when its finished.
This bug is grave due to dataloss.
This bug and others make Ark quite unpractical to use as a good archive manager. Adding my full votes.
this bug is still present on kde 3.5.8 from kubuntu packages.
see https://bugs.launchpad.net/ubuntu/+source/kdeutils/+bug/175177
Will this EVER be fixed?!!!!!!!!! This is the same as CPUs being ok with div-by-zero errors, like nothing wrong has happened. This is a critical error which leads to data loss! Please fix this! 2.6.4 (KDE 3.5.9, Debian Package 4:3.5.9.dfsg.1-2 (lenny/sid)) Linux (x86_64) release 2.6.21-2-amd64 Qt: 3.3.8b KDE: 3.5.9 Ark: 2.6.4
Confirmed on Mandriva 2008.1 with KDE 3.5.9 distribution packages. Unpacking several archives at once via the context menu only unpacks some of them. Also, for each archive an instance of Ark pops open. A better approach would be to add support for extracting multiple archives to Ark.
I agree; I don't like it when programs handle multiple input files all at once, as that can really kill system performance. I think Ark should use a queueing mechanism that only unpacks one file at a time by default, but with an option to choose how many to process at once so users can take advantage of SMP.
The kde4 ark has this functionality available with the batch extract interface. It's a little rough around the edges still, but it does indeed accept multiple files as input. Since kde3 ark will not receieve any development at this scale, I am closing this bug.
Do you think it's right to mark it as "resolved"?, I'd rather mark it as "won't fix". I understand that ark for KDE4 is the next version of ark, but I think there will be many people around there that won't be migrating anytime soon. Since the bug was reported for kde3, I would expect to see it's status for this major version of KDE.
I agree I was a bit quick on that one. Will reopen and mark it as wontfix.
...and making it WONTFIX. Again, about kde3 version, a quick fix might be to add a condition that returns a visible error if more than one input is provided. This would probably again mean more strings that would have to be translated. An even simpler fix would maybe be to check if the service menu maybe mistakenly is set to show up at all when more than one file is selected. I will have a quick look at it.
2008/8/4 Harald Hvaal <haraldhv@stud.ntnu.no>: > Again, about kde3 version, a quick fix might be to add a condition that returns a visible error if more than one input is provided. This would probably again mean more strings that would have to be translated. An even simpler fix would maybe be to check if the service menu maybe mistakenly is set to show up at all when more than one file is selected. I will have a quick look at it. I think it is not sufficient. AFAIR Ark in KDE 3 is KUniqueApplication so calling it to unpack single-file from different callers at the same time would cause the problem also (though it is harder to achieve). The solution IMO could be queueing unpack ing requests and doing it one-by-one.
It should be easier to make an error msg window to pop up, than to implement a queueing system (which is the (almost) ideal solution). I prefer to have an error msg than to end up with corrupt files and finding out when it's too late. The questions are: - how long would it take to implement the error msg window? - how long would it take to implement a queueing mechanism? - how long will it take to get ark4 working and available in most distros (e.g. debian/ubuntu)? I already have okular (KDE4 app) available in debian repositories... but no ark4. On Mon, Aug 4, 2008 at 11:53 AM, Krzysztof Lichota <krzysiek@lichota.net> wrote: [bugs.kde.org quoted mail]
> The questions are: > - how long would it take to implement the error msg window? Not long > - how long would it take to implement a queueing mechanism? Rather than a question of time, it's a question of workforce. Personally I won't develop any features for kde3 ark (both because I don't know kde3 ark/qt3, and because I don't want to). I think people would probably agree with me on this one. > - how long will it take to get ark4 working and available in most > distros (e.g. debian/ubuntu)? Ark4 is already there, but multiple extract service menu won't be out before 4.2. It does compile easily on kde 4.1 libraries, however, so there shouldn't be any problem to run it along with kde 4.1 (or even 3.5 by just installing the libs).
My questions were more or less retoric. What I meant is that is preferable to have an error msg pop up than ending up with corrupt files (while the new feature gets implemented *or* ark4 finally gets into most distro repositories) On Sat, Aug 9, 2008 at 3:19 PM, Harald Hvaal <haraldhv@stud.ntnu.no> wrote: [bugs.kde.org quoted mail]