search

jianlinwei / theunarchiver

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

Dialog about sandoxing permissions problem has text but no window #612

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
The problem which had been discussed earlier in the year regarding being unable 
to write to a folder because of sandboxing is appearing to me now with The 
Unarchiver 3.5.1. This happened when I moved the folder containing the archives 
from ~/Downloads/ into ~/Documents/. (The full path of the folder in question 
is currently ~/Documents/App Installs/Not Yet Installed/. The same folder, 
moved and renamed but otherwise the same, used to be ~/Downloads/ Install/. 
(The space before "Install" is not a typo.)) Since the path is still in 
/Users/, sandboxing shouldn't be the issue, but I cannot find anything in the 
folder permissions that should cause The Unarchiver to not be able to write to 
this folder.

More importantly, though, the dialog that comes up to tell me about this 
problem is not completely there! Here's what is happening: I double-click on 
the archive. The Unarchiver launches and the progress window appears. It 
doesn't start extracting, though; after a moment, the progress window simply 
disappears. No windows or dialogs appear on the screen. (This is with all other 
windows hidden, so nothing should be obscuring it.) All the menus are still 
active, but only commands on the application menu and the Help menu do 
anything. If I double-click another archive, or drag one to the dock icon, or 
try to open one from the File menu, nothing happens. I must quit The Unarchiver 
in order to get it to try to extract something else.

The only reason I know there is a dialog that's supposed to be displayed is 
that I was looking at the app's dock menu to see if anything there might help, 
and I tried "Show All Windows". (That is what in earlier versions of OS X was 
the Exposé option for showing this application's windows.) That brought up a 
small block of text in the center of the screen with no window of any kind 
surrounding it—just a block of text right over the desktop. It says:

"The Unarchiver cannot write to this folder. The Mac OS X sandbox may be 
blocking access to it. To ask the sandbox to allow The Unarchiver to write to 
this folder, simply click "Extract". This permission will be remembered and The 
Unarchiver will not need to ask for it again."

This is shown in the first attached screen shot. (I changed the desktop to 
plain white so that the text would be visible.) When not in "Show All Windows" 
mode, that text sits in the lower left corner of my screen, behind my dock 
(which I keep anchored to the left), as shown in the second screen shot, and 
clicking on it simply brings The Unarchiver frontmost, if it wasn't already, 
and clicking immediately outside of the text area is interpreted as a click on 
the desktop. (I discovered the text was sitting behind my dock only when I 
changed the desktop to white so I could read it when it appeared in "Show All 
Windows".) Pressing any key on the keyboard that might activate a control, such 
as Return or Tab, while The Unarchiver and this text "window" are frontmost 
produces only error beeps.

While obviously I'd like a solution to the permissions and/or sandbox issue, I 
am more concerned by this phantom text that cannot be dismissed except by 
quitting The Unarchiver. I am not seeing any dialog or text from the sandboxing 
system asking for any permissions, and there is no button appearing with the 
text generated by The Unarchiver that would allow me to grant permission as 
indicated in that text.

Specs: I am running The Unarchiver 3.5.1 under Mac OS X 10.8.2 on a 2010 MBP 
17-inch (MacBook 6,1) with 8GB RAM.

Original issue reported on code.google.com by thequant...@gmail.com on 26 Dec 2012 at 8:11

Attachments:

GoogleCodeExporter commented 9 years ago 
The only directory that is writable by default is Downloads. Anything else in 
Users is sandboxed too, so that part is normal.

For the mysterious disappearing dialog, first of all see if you have any 
programs installed that change functionality in other apps, and if so, try 
disabling them and see if the problem persists.

Original comment by paracel...@gmail.com on 10 Jan 2013 at 2:39

GoogleCodeExporter commented 9 years ago 
I did not know that ~/Documents was sandboxed. I have had no difficulties using 
other utilities to expand archives in that location, but none of them came from 
the App Store, so I don't know how well they implement sandboxing (if at all). 
I assume that specifically directing an app to write in another location in 
Users via the save dialog bypasses sandbox limitations? I'm not currently an OS 
X developer, so I haven't studied the current sandbox requirements.

As for the disappearing dialog, the only thing I have installed that modifies 
other apps' dialogs is Default Folder X, and disabling it did not change this 
behavior—I had tried that between when I originally posted this and your 
response based on suggestions from other venues. I did discover, however, that 
the problem seems to be limited to subfolders of ~/Documents. I tried moving an 
archive into just ~/Documents (not inside a subfolder), and this time when I 
double-clicked the archive, the actual dialog box appeared for that text! I 
canceled out of it and tried another subfolder, just to compare, and the dialog 
box still vanished, but for archives loose in ~/Documents, the full dialog 
appeared, and I was able to grant The Unarchiver permission in ~/Documents and 
all its subfolders. So that part is resolved.

Original comment by thequant...@gmail.com on 10 Jan 2013 at 8:46

GoogleCodeExporter commented 9 years ago 
That is very, very strange.

I just tried creating some subfolders in Documents, but it seems to work just 
fine here.

I really have no idea what is triggering this weird bug.

Original comment by paracel...@gmail.com on 10 Jan 2013 at 8:57

GoogleCodeExporter commented 9 years ago 
This happens with me too, two hackintoshes and a 2012 MAcBook Pro. Love the app 
except this makes it unusable.

Original comment by adapptiv...@gmail.com on 14 Feb 2013 at 5:42

GoogleCodeExporter commented 9 years ago 
You can get the legacy version to fix it, but it would help if you could figure 
out what is triggering that behavior. I suspect it's either some third-party 
hack, or an OS X bug, though.

Original comment by paracel...@gmail.com on 14 Feb 2013 at 11:20

GoogleCodeExporter commented 9 years ago 
Closing this for now as I don't think I can do much about it, since it does not 
seem to be reproducible at all.

If there is more information to add, post it here.

Original comment by paracel...@gmail.com on 10 Sep 2013 at 10:56