Open GoogleCodeExporter opened 8 years ago
Help!!!
Original comment by CHovey...@gmail.com
on 23 Nov 2012 at 8:43
Others have reported this, but I can not reproduce it.
Can you test it on another machine and see if it doesn't work? Can you figure
out if there is some other program you have installed that might cause problems?
Also, can you post any output in Console.app?
Original comment by paracel...@gmail.com
on 23 Nov 2012 at 10:53
I've had to remove it from my system as it's completely unusable in 10.8.2.
This has been occurring for some time now but I'm not seeing a lot of movement
towards a fix.
What can I do to help?
Original comment by mrf064
on 23 Nov 2012 at 6:30
What do you mean by "some time"?
Original comment by paracel...@gmail.com
on 23 Nov 2012 at 7:09
New install on 10.8.1 on a 13" rMBP and I'm getting this issue
Original comment by swrobel
on 29 Nov 2012 at 9:28
Again: As I can't reproduce this, I need more information. I can't do anything
otherwise.
Please test on other machines if you can, to see if you can get it to happen on
some machine and not another.
Also, post any output from Console.app.
Original comment by paracel...@gmail.com
on 29 Nov 2012 at 9:32
What should I look for in Console? I searched for unarchiver and there is
nothing in there.
Original comment by swrobel
on 29 Nov 2012 at 9:36
Try leaving it open while starting up The Unarchiver and testing, and see if
anything new appears.
Original comment by paracel...@gmail.com
on 29 Nov 2012 at 9:48
Nothing
Original comment by swrobel
on 29 Nov 2012 at 9:57
Can you think of any software you have installed that messes with other
programs in any way, and in that case, can you try disabling it?
Also, do you have a second machine you can test on?
Original comment by paracel...@gmail.com
on 29 Nov 2012 at 10:08
Hello,
same problem here for the last 2 updates. I'm also running 10.8.2 on a MacPro...
Each time a drop an archive onto the dock icon the preferences screen opens but
the archive is not unpacked.
CMD-O on the archive does work.
I left the console open and dragged a zip file to the dock icon, no messages
were displayed.
Removed the app and then reinstalled it from scratch, nothing changed.
Original comment by alex.wei...@technolink.lu
on 30 Nov 2012 at 7:55
Issue 592 has been merged into this issue.
Original comment by paracel...@gmail.com
on 30 Nov 2012 at 10:11
Again, what I really need is for someone to figure out what triggers this. As
it does not happen on all machines, there must be something that causes it only
on some machines.
If you have other machines, PLEASE test on them, to see if you can find one
where it doesn't happen. Then, try to figure out what the difference between
machines is.
Original comment by paracel...@gmail.com
on 30 Nov 2012 at 10:31
Also, are any of you using Default Folder X, or anything like it?
Original comment by paracel...@gmail.com
on 30 Nov 2012 at 12:22
Hello,
I'll try to help you and figure it out ... no Folder X. I could offer you a
TeamViewer connection if you wanted to have a look at the problem. Maybe you
have a "debug" version of the program we could try to run on my machine.
Original comment by alex.wei...@technolink.lu
on 30 Nov 2012 at 1:30
Got it .... at least maybe :-)
I have Typinator running. When I shut it down, the unarchiving seems to work.
With Typinator enabled, the unarchiving doesn't work?
Original comment by alex.wei...@technolink.lu
on 30 Nov 2012 at 1:32
Oh, that sounds like a nice hint. Can anyone else confirm if they are or are
not running Typinator?
Original comment by paracel...@gmail.com
on 30 Nov 2012 at 2:28
Yes, I can confirm this. Had the same problem (double click on .zip instead of
drag-on-dock).
Now, I quit Typinator and Unarchiver just worked as it should.
Original comment by andreasm...@gmail.com
on 30 Nov 2012 at 4:26
I just installed Typinator myself, and now I can reproduce the problem.
I will investigate if there is any way to work around this, but in either case,
I suggest people report this problem to the makers of Typinator directly, as it
is definitely a bug in their program.
Original comment by paracel...@gmail.com
on 30 Nov 2012 at 4:28
Typinator is it!
Original comment by swrobel
on 30 Nov 2012 at 9:19
Well, it's looking like Alex got it, then. Big thanks to him!
I've reported the issue to them, but I can't figure out quite what is going on
from here so I don't think I can work around the problem, unless they have some
ideas. I haven't heard from them yet. I guess I will just leave this issue open
until they fix it, so other people can find this if they run into this problem.
Original comment by paracel...@gmail.com
on 30 Nov 2012 at 9:33
Apparently the Typinator 5.4 beta 1 version works better. It seems to let The
Unarchiver work under normal circumstances.
(It still fails for me when I run The Unarchiver in the debugger with
breakpoints set for some reason, though, but that should not affect normal
users. I don't know if there are any other situations that can still trigger
the bug, though.)
Original comment by paracel...@gmail.com
on 1 Dec 2012 at 1:24
Hello,
I also send an email to the authors of Typinator to confirm them the problem
between the 2 applications...
Original comment by alex.wei...@technolink.lu
on 1 Dec 2012 at 4:23
I do not have have Typinator installed and have this issue. However, looking at
Console showed that it was a sandbox error caused by Default Folder. Upgrading
to the newest Default Folder fixed the issue for me.
Original comment by daniel.j...@gmail.com
on 2 Dec 2012 at 4:05
I don't have Typinator nor Default Folder installed, and I saw the bug. My
console output included:
12/11/12 10:59:50.938 AM Dock[416]: no information back from LS about running
process
12/11/12 10:59:51.025 AM quicklookd[58243]: [QL] Can't get plugin bundle info
at XTUM/ -- file://localhost/private/tmp/
12/11/12 10:59:51.306 AM quicklookd32[58248]: *** NSTask: Task create for path
'/Library/QuickLook/BetterZipQL.qlgenerator/Contents/Resources/7z' failed: 22,
"Invalid argument". Terminating temporary process.
12/11/12 10:59:51.000 AM kernel[0]: exec of
/Library/QuickLook/BetterZipQL.qlgenerator/Contents/Resources/7z denied since
it was quarantined by The Unarchiver and created without user consent,
qtn-flags was 0x00000007
12/11/12 10:59:55.878 AM ReportCrash[58249]: Saved crash report for
quicklookd32[58248] version ??? to
/Users/[xx]/Library/Logs/DiagnosticReports/quicklookd32_2012-12-11-105955_[xxxx]
.crash
I deleted BetterZipQL.qlgenerator and then got:
12/11/12 11:04:27.052 AM sandboxd[58428]: ([58427]) mdworker(58427) deny
mach-lookup com.apple.ls.boxd
12/11/12 11:04:27.000 AM kernel[0]: Sandbox: sandboxd(58428) deny mach-lookup
com.apple.coresymbolicationd
12/11/12 11:04:31.011 AM Mail[400]: An instance 0x7f9e2fb2c410 of class
MessageViewingState was deallocated while key value observers were still
registered with it. Observation info was leaked, and may even become mistakenly
attached to some other object. Set a breakpoint on NSKVODeallocateBreak to stop
here in the debugger. Here's the current observation info:
<NSKeyValueObservationInfo 0x7f9e2d45b300> (
<NSKeyValueObservance 0x7f9e30e01610: Observer: 0x7f9e30e01550, Key path:
message.type, Options: <New: NO, Old: NO, Prior: YES> Context: 0x7f9e2f9801b0,
Property: 0x7f9e321f1aa0>
<NSKeyValueObservance 0x7f9e31a28a60: Observer: 0x7f9e2d44b450, Key path:
message.type, Options: <New: NO, Old: NO, Prior: YES> Context: 0x7f9e2f9801b0,
Property: 0x7f9e321f1aa0>
<NSKeyValueObservance 0x7f9e31a3bbc0: Observer: 0x7f9e31a3baf0, Key path:
message.type, Options: <New: NO, Old: NO, Prior: YES> Context: 0x7f9e2f9801b0,
Property: 0x7f9e321f1aa0>
<NSKeyValueObservance 0x7f9e30e19270: Observer: 0x7f9e30e191a0, Key path:
message.type, Options: <New: NO, Old: NO, Prior: YES> Context: 0x7f9e2f9801b0,
Property: 0x7f9e321f1aa0>
)
12/11/12 11:04:33.828 AM Mail[400]: *** Assertion failure in
-[EWSCreateEventReplyResponseOperation executeOperation],
/SourceCache/Message/Message-1499/Message/EWS/Items/EWSCreateItemResponseOperati
on.m:37
EWS sent an unexpected quantify of create item replies: 2
(
0 CoreMessage 0x00007fff8729c8d7 -[MFAssertionHandler _handleFailureWithPreamble:description:arguments:] + 141
1 CoreMessage 0x00007fff8729c748 -[MFAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 215
2 Message 0x00007fff887621cc -[EWSCreateItemResponseOperation executeOperation] + 608
3 Message 0x00007fff88760063 -[EWSCreateEventReplyResponseOperation executeOperation] + 78
4 CoreMessage 0x00007fff872b7f10 -[MonitoredOperation main] + 219
5 Foundation 0x00007fff90fc4986 -[__NSOperationInternal start] + 684
6 Foundation 0x00007fff90fcc1a1 __block_global_6 + 129
7 libdispatch.dylib 0x00007fff90127f01 _dispatch_call_block_and_release + 15
8 libdispatch.dylib 0x00007fff901240b6 _dispatch_client_callout + 8
9 libdispatch.dylib 0x00007fff901251fa _dispatch_worker_thread2 + 304
10 libsystem_c.dylib 0x00007fff92030cab _pthread_wqthread + 404
11 libsystem_c.dylib 0x00007fff9201b171 start_wqthread + 13
)
12/11/12 11:04:36.130 AM Finder[418]: [QL] Can't get plugin bundle info at
XTUM/ -- file://localhost/
12/11/12 11:04:46.674 AM Dock[416]: no information back from LS about running
process
Since then it seems to work. I've added the logs just in case they help figure
out the issue.
Original comment by gilea...@gmail.com
on 11 Dec 2012 at 6:13
Those messages all seem to be different apps than The Unarchiver, though, so
it's a bit mysterious that actually removing that qlgenerator would work. But
if it really did work, that's good, I suppose.
Original comment by paracel...@gmail.com
on 11 Dec 2012 at 6:51
I had the same issue on 10.8.2 on a MacBook Pro retina.
As for my machine, I finally reached the conclusion that SwitchResX's daemon
triggered this.
If SwitchResX's daemon is running, this issue will happen.
Original comment by kanetomo...@gmail.com
on 3 Jan 2013 at 3:06
SwitchResX ver 4.3.3 does not trigger this issue, but older version does.
Original comment by kanetomo...@gmail.com
on 3 Jan 2013 at 5:27
Good to know.
Original comment by paracel...@gmail.com
on 3 Jan 2013 at 5:30
Sorry to bring bad news: I don't have either SwitchResX or DefaultFolder
installed… but I keep seeing the preference dialog whenever I double click
on an archive in the Finder, and the archive is never uncompressed.
I have the latest Mac App Store version, and system 10.8.2.
Original comment by sebastie...@gmail.com
on 19 Feb 2013 at 10:42
Then it is probably some other program that is messing with other apps. Try toi
go through what you have installed and see if you can figure out what.
Original comment by paracel...@gmail.com
on 19 Feb 2013 at 11:36
Hi, thanks for your answer :)
The problem is that the Console doesn't show any error or stacktrace that might
point to the faulty app. Can you give me some advice to find the app that
causes the problem?
Original comment by sebastie...@gmail.com
on 19 Feb 2013 at 1:47
Not really. You just have to figure out what app you are using that hooks into
other apps and modifies their behavior somehow.
Original comment by paracel...@gmail.com
on 19 Feb 2013 at 1:55
I've found it: it's the "Petit Pro Lexis", a french grammar corrector…
I'll contact the devs of that tool to let them know. Do you have any info that
I could give them to make them understand the problem?
Original comment by sebastie...@gmail.com
on 19 Feb 2013 at 4:27
No, but I know the Typinator authors tracked it down and fixed it, so they
might be able to help.
Original comment by paracel...@gmail.com
on 19 Feb 2013 at 4:31
ok thanks
Original comment by sebastie...@gmail.com
on 19 Feb 2013 at 4:34
Issue 647 has been merged into this issue.
Original comment by paracel...@gmail.com
on 18 Mar 2013 at 11:41
I'm having the same problem with v3.8. (I had it in v3.7 too, but 3.8 was on
the way, so waited to see if that made a difference). When I run Unarchiver,
the preferences screen appears.
The unarchive process itself works fine, so for day-to-day I don't really mind
this, but I'm trying to use Applescript to un-archive multiple files and this
is forcing me to manually quit Unarchiver each time.
Seeing the earlier posts, I've quit/disabled everything else that I can, but no
joy. Any suggestions?
Original comment by john.tam...@gmail.com
on 20 Jul 2013 at 2:07
That is not the same problem, and that sounds like the program working as
expected. Just starting the program is supposed to open the preferences.
Original comment by paracel...@gmail.com
on 20 Jul 2013 at 9:12
Issue 722 has been merged into this issue.
Original comment by paracel...@gmail.com
on 8 Dec 2013 at 9:30
Issue 722 has been merged into this issue.
Original comment by paracel...@gmail.com
on 9 Dec 2013 at 10:11
Issue 722 has been merged into this issue.
Original comment by paracel...@gmail.com
on 9 Dec 2013 at 3:53
Issue 728 has been merged into this issue.
Original comment by paracel...@gmail.com
on 28 Jan 2014 at 11:28
My conflicting program was Elite Keylogger. Uninstalling and restarting seems
to have cleared up most issues. Now the only remaining problem is unarchiver
seems to not always have permission to the folder being extracted to.
Original comment by mcdaniel...@gmail.com
on 29 Jan 2014 at 5:51
Can conform Elite Keylogger produced the same issue. After completely removing
Elite Keylogger, The Unarchiver worked as expected again
Original comment by clipsubm...@gmail.com
on 26 Feb 2014 at 1:17
Issue 780 has been merged into this issue.
Original comment by paracel...@gmail.com
on 21 Oct 2014 at 10:34
Issue 785 has been merged into this issue.
Original comment by paracel...@gmail.com
on 31 Oct 2014 at 10:22
Just to add to the list - the program "Smart Scroll" was causing the issue for
me.
Original comment by ashha...@gmail.com
on 3 Nov 2014 at 4:35
Report the bug to them, too, so they can fix it.
Original comment by paracel...@gmail.com
on 3 Nov 2014 at 8:44
I found a solution. I put TheUnarchiver.app on the Desktop. Now it's works
fine. No more problem. May be this solution works only for me, but it's works.
Original comment by naejyl...@gmail.com
on 3 Nov 2014 at 4:46
Original issue reported on code.google.com by
CHovey...@gmail.com
on 23 Nov 2012 at 8:42