galaxy001 / theunarchiver

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

Preferences screen displays when UnArchiver is used. #583

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
The UnArchiver's preference screen opens each time the program is tasked.

Have attempted a variety of corrective measures such as uninstall/reinstall, 
conflicting file search, et. al.

Running an IMac, 6 GB memory,  2GHz Intel Core Duo

Original issue reported on code.google.com by CHovey...@gmail.com on 23 Nov 2012 at 8:42

GoogleCodeExporter commented 9 years ago
Moving to the desktop didn't fix the issue. Another one that caused The 
Unarchiver to stop working: "MouseFixer"

Original comment by ashha...@gmail.com on 17 Nov 2014 at 6:36

GoogleCodeExporter commented 9 years ago
Got the same problem.
Console show a message : " The Unarchiver[36148]: Antidote - Texteurs: Module 
texteur installé dans /Applications/The Unarchiver.app (cx.c3.theunarchiver)" 

Seeing all the above reports, maybe is it related to some kind of plugin 
interface you (or apple) are offering to other components that blocks at some 
point... my two cents.

Original comment by GaelCa...@gmail.com on 17 Dec 2014 at 11:58

GoogleCodeExporter commented 9 years ago
Confirmation of my previous post : I put the unarchiver in the exclusion list 
of antidote, and the problem is solved. (note that I did not have to remove 
antidote, just to prevent it from hooking into the unarchiver).
Hope this helps. 

Original comment by GaelCa...@gmail.com on 18 Dec 2014 at 12:05

GoogleCodeExporter commented 9 years ago
I don't have any of the mentioned third-party apps. I am noticing several log 
entries related to SIMBL.osax, and I saw it mentioned online that The 
Unarchiver is one app responsible for installing this ScriptingAddition 
extension.

I'm seeing these error messages in my Console:
----
2014-12-25 1:02:29.891 AM The Unarchiver[36435]: Performance: Please update 
this scripting addition to supply a value for ThreadSafe for each event 
handler: "/Library/ScriptingAdditions/SIMBL.osax"

2014-12-25 1:02:29.893 AM SIMBL Agent[39406]: AppleEvents: Send port for 
process has no send right, port=( port:17511/0x4467 rcv:1,send:0,d:0 limit:5) 
(findOrCreate()/AEMachUtils.cp #526) com.apple.main-thread
----

Original comment by coolfac...@gmail.com on 25 Dec 2014 at 9:04

GoogleCodeExporter commented 9 years ago
Note that this problem didn't start happening for me until I upgraded to 
Yosemite, and then it's been happening very frequently. The Preference window 
appears 90% of the time instead of starting the unarchiving process on my 
selected file. Very frustrating.

Original comment by coolfac...@gmail.com on 25 Dec 2014 at 9:07

GoogleCodeExporter commented 9 years ago
The Unarchiver installs no SIMBL extensions, so whatever you read was mistaken. 
It comes from somewhere else, and is likely responsible for breaking The 
Unarchiver.

Original comment by paracel...@gmail.com on 26 Dec 2014 at 7:23

GoogleCodeExporter commented 9 years ago
I have Afloat installed, which clearly is the reason why I saw a connection 
between SIMBL and The Unarchiver... SIMBL is invoked for every Cocoa app that 
launches.

Note - I finally installed the legacy version of the app and the Preferences 
window problem went away. Do you have a fix for that yet? Do you need more info?

Original comment by coolfac...@gmail.com on 26 Dec 2014 at 8:42

GoogleCodeExporter commented 9 years ago
I have no idea if this is correct, but I've read some of the thread and I've 
had the same issue recently (running OS X 10.10.2) .. however, I managed to 
reproduce it though.

I've installed Mumble 1.2.4 and if I suspend my computer with Mumble running, 
this cause The Unarchive to not function properly and throws me the Preference 
dialog instead. If I just close Mumble, it works just fine again..

Original comment by jesper.w...@gmail.com on 31 Dec 2014 at 6:45

GoogleCodeExporter commented 9 years ago
It's probably a good idea to report the bug to the Mumble developers, too.

Original comment by paracel...@gmail.com on 1 Jan 2015 at 9:47

GoogleCodeExporter commented 9 years ago
I also have this problem and I have SIMBL and  Afloat installed. (running OS X 
10.10.3)

Original comment by mattia...@gmail.com on 23 Apr 2015 at 8:42