Summary: | Ark should first extract all files then set permissions | ||
---|---|---|---|
Product: | [Applications] ark | Reporter: | Harald Nikolisin <hochglanz> |
Component: | general | Assignee: | Helio Castro <helio> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Harald Nikolisin
2003-05-31 20:00:40 UTC
In other words: Ark should first extract all files, and only after it is done set permissions. Or at least so for directories. Because in reality you DON'T have permission to write to that directory, since you are the owner and the owner doesn't have write permission. It doesn't matter that you are a member of a writeable group. Also please note that there are some permissions Ark cannot set and this is the case here: you're extracting a file that belonged to user "nobody". But the chown call to set the user can only be issued by root. no, I think that's not correct. the .zip file which I want to extract belongs to me, and I am NOT "nobody". "nobody" is only the user which belongs the current directory (in my example: "demofolder"). therefore I have write permission (because of the membership to "specialgroup") and setting the right group (because of the Group-Bit) is a job for the backend "zip" or not?! In either case extracting the zip file from a command shell with the zip command works fine, and Ark did not. Ok, sorry then. I completely misunderstood your problem. Are you saying then that this problem only happens with that particular directory? And does it happen when saving files into it from another KDE applications? "Are you saying then that this problem only happens with that particular directory? " yes "And does it happen when saving files into it from another KDE applications?" no, other KDE apps (like KEdit) doesn't have a problem with saving a file into that directory. I'm assuming that Ark checks the permission in a own routine, which has a problem with a directory, which owner has no write permission and the group-bit is set. or something like that... Stop with ping pong guys.. :-) I will confirm this and fix tomorrow. Need reproduce this with zip and other formats to see if is a localized problem or affects all. []'s It is not possible to reproduce this bug using current CVS. If you can confirm the existence of the bug in HEAD, please re-open this bug with a testcase. |