search

jianlinwei / theunarchiver

Automatically exported from code.google.com/p/theunarchiver
Other
0 stars 0 forks source link

Desktop Permissions Not Remembered #721

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
I'm using the MAS version (1.9.1) which should be the latest.

On my iMac I am able to unarchive files without the warning.  I may have 
received it once, but not now.

On my 13" RMBP I always receive the permission warning.  It doesn't remember to 
stop asking me for permission.

Original issue reported on code.google.com by rondfra...@gmail.com on 8 Dec 2013 at 10:18

GoogleCodeExporter commented 9 years ago 
This is a mysterious issue which I don't know why it happens, since it can not 
be reliably reproduced. Running "defaults delete cx.c3.theunarchiver" in a 
terminal should fix it, though.

Original comment by paracel...@gmail.com on 8 Dec 2013 at 10:24

GoogleCodeExporter commented 9 years ago 
I'm receiving this error when running in Terminal:

defaults delete cx.c3.theunarchiver
2013-12-08 04:27:58.983 defaults[934:507] 
Domain (cx.c3.theunarchiver) not found.
Defaults have not been changed.

Perhaps I need to type something first that directs me to the proper folder?

Original comment by rondfra...@gmail.com on 8 Dec 2013 at 10:30

GoogleCodeExporter commented 9 years ago 
Also, I have one zip that will extract to my RMBP desktop without a warning.  
The only differences that I can see are that it doesn't have a folder in the 
archive and the file size is much smaller (29K).

Original comment by rondfra...@gmail.com on 8 Dec 2013 at 10:51

GoogleCodeExporter commented 9 years ago 
I'm alsö seeing this error with 3.9.1 MAS edition.

As an update to comment #1 (@paracel...), "$ defaults delete 
cx.c3.theunarchiver cachedBookmarks" alsö solves the problem. It seems that 
the problem is the bookmarks (cached in order to preserve sandbox exemptions) 
get out of date sometimes. The solution would be invalidate the cache whenever 
a sandboxing error is encountered on an otherwise expected-to-work path. Or, 
perhaps even better, simply replace the cache entry whenever a new sandboxing 
exemption is obtained. This would avoid invalidating the cache unless there is 
newer (better) data to store.

Original comment by j...@gaelicwizard.net on 14 Apr 2014 at 5:22

GoogleCodeExporter commented 9 years ago 
i to have this issue and can not run the terminal command (same error as #2)

Original comment by randyver...@viesign.be on 15 Apr 2014 at 10:10