4 Replies Latest reply: Jan 5, 2013 9:19 AM by pictopia
Jeremy Bechtold Level 2 Level 2 (220 points)

Earlier I was attempting to create a new custom trigger in Quicksilver and I believe that it changed something in my Finder... I never ended up actually creating the custom trigger as I could not get the functionality I wanted to work, so I backed out and closed up, assuming nothing was changed or saved (and realy, nothing should have been).

 

Now, when I click on items in my Finder Sidebar, an app launches. ±95% of the time, it's a sidebar folder living in my home folder. Once in a long while, something outside that folder but also only on my boot drive will trigger the action. I have no folder actions turned on that I'm aware of. I looked and unless there is another place, I can find nothing. When I click on my home folder, desktop, docs, downloads, dropbox... it does it. Once in every 10-20 tries it'll do it with apps. nothing when I scroll out of the "Places" section to "Shared" or "Devices" ... only in places items that are on my boot drive.

 

The action that it triggers is a launch (or activation since it's already launched as I test it) of the app Paparazzi. I believe it did do it once or twice to the previous version, but I was in the process of updating the app when I first noticed the issue. I have zipped up both apps and it does not do it with the old version when unzipped, but I really think the versions are not the issue, as it did do it at least once or twice on the old version before I caught on to what was happening. you can see it in action here: http://screencast.com/t/9AxmmmOs

 

I opened the console and this is the content between the markers with the isolated (and repeatable) events:

 

Dec 17 18:30:37 Jeremys-MacBook-Pro-5 Paparazzi![3814]: Couldn't load history: (null)

Dec 17 18:30:37 Jeremys-MacBook-Pro-5 SpiderOak FSEvents[1409]: Notification change 1559963665 in /Users/Jeremy/Library/Application Support/AddressBook/, flags 0

Dec 17 18:30:37 Jeremys-MacBook-Pro-5 SIMBL Agent[310]: received {\n    NSApplicationBundleIdentifier = "org.derailer.Paparazzi";\n    NSApplicationName = "Paparazzi!";\n    NSApplicationPath = "/Applications/Paparazzi!.app";\n    NSApplicationProcessIdentifier = 3814;\n    NSApplicationProcessSerialNumberHigh = 0;\n    NSApplicationProcessSerialNumberLow = 475252;\n    NSWorkspaceApplicationKey = <NSRunningApplication: 0x100170dd0 (org.derailer.Paparazzi - 3814)>;\n}

Dec 17 18:30:39 Jeremys-MacBook-Pro-5 Paparazzi![3814]: Performance: Please update this scripting addition to supply a value for ThreadSafe for each event handler: "/Library/ScriptingAdditions/SIMBL.osax"

Dec 17 18:30:39 Jeremys-MacBook-Pro-5 Paparazzi![3814]: Error loading /Users/Jeremy/Library/ScriptingAdditions/SmartWrap Scripting Addition X.osax/Contents/MacOS/SmartWrap Scripting Addition X:  dlopen(/Users/Jeremy/Library/ScriptingAdditions/SmartWrap Scripting Addition X.osax/Contents/MacOS/SmartWrap Scripting Addition X, 262): no suitable image found.  Did find:\n          /Users/Jeremy/Library/ScriptingAdditions/SmartWrap Scripting Addition X.osax/Contents/MacOS/SmartWrap Scripting Addition X: no matching architecture in universal wrapper

Dec 17 18:30:39 Jeremys-MacBook-Pro-5 [0x0-0x74074].org.derailer.Paparazzi[3814]: Paparazzi!: OpenScripting.framework - scripting addition "/Users/Jeremy/Library/ScriptingAdditions/SmartWrap Scripting Addition X.osax" declares no loadable handlers.

Dec 17 18:30:39 Jeremys-MacBook-Pro-5 Paparazzi![3814]: InjectEventHandler

Dec 17 18:30:40 Jeremys-MacBook-Pro-5 SpiderOak FSEvents[1409]: Notification change 1559963690 in /Users/Jeremy/Library/Application Support/AddressBook/, flags 0

Dec 17 18:30:43 Jeremys-MacBook-Pro-5 SpiderOak FSEvents[1409]: Notification change 1559963918 in /Users/Jeremy/Library/Application Support/AddressBook/Metadata/, flags 0

 

To arrive at this content, I set a marker in console, click over to finder, and then click a known offender folder. Clearly there is something going on with scripts here, but I have no clue what it is. my assumption on the spideroak entries are that those files ar ebeing watched by spider oak (a web-based backup utility) and it's checking to see if they need to be uploaded. My next thought was to quit spideroak to test that thought, but I went out and set a new marker in the console, and now it won't record any data from me clicking the sidebar folders... about 10 tries later and quitting paparazzi will allow the console to update again, and yes, without spideroak running, there is no mention of it, so that's just watching the parent folder. This log example comes after quitting spideroak AND paparazzi (where clicking the folders relaunches paparazzi):

 

Dec 17 19:15:43 Jeremys-MacBook-Pro-5 SIMBL Agent[310]: received {\n    NSApplicationBundleIdentifier = "org.derailer.Paparazzi";\n    NSApplicationName = "Paparazzi!";\n    NSApplicationPath = "/Applications/Paparazzi!.app";\n    NSApplicationProcessIdentifier = 4693;\n    NSApplicationProcessSerialNumberHigh = 0;\n    NSApplicationProcessSerialNumberLow = 606356;\n    NSWorkspaceApplicationKey = <NSRunningApplication: 0x1001ac5a0 (org.derailer.Paparazzi - 4693)>;\n}

Dec 17 19:15:43 Jeremys-MacBook-Pro-5 Paparazzi![4693]: Performance: Please update this scripting addition to supply a value for ThreadSafe for each event handler: "/Library/ScriptingAdditions/SIMBL.osax"

Dec 17 19:15:43 Jeremys-MacBook-Pro-5 Paparazzi![4693]: Error loading /Users/Jeremy/Library/ScriptingAdditions/SmartWrap Scripting Addition X.osax/Contents/MacOS/SmartWrap Scripting Addition X:  dlopen(/Users/Jeremy/Library/ScriptingAdditions/SmartWrap Scripting Addition X.osax/Contents/MacOS/SmartWrap Scripting Addition X, 262): no suitable image found.  Did find:\n          /Users/Jeremy/Library/ScriptingAdditions/SmartWrap Scripting Addition X.osax/Contents/MacOS/SmartWrap Scripting Addition X: no matching architecture in universal wrapper

Dec 17 19:15:43 Jeremys-MacBook-Pro-5 [0x0-0x94094].org.derailer.Paparazzi[4693]: Paparazzi!: OpenScripting.framework - scripting addition "/Users/Jeremy/Library/ScriptingAdditions/SmartWrap Scripting Addition X.osax" declares no loadable handlers.

Dec 17 19:15:43 Jeremys-MacBook-Pro-5 Paparazzi![4693]: InjectEventHandler

 

Here's what I know:

  • it happens with (as activation of app) or without Paparazzi being launched, as well as on both the old version (0.4.3) and the new (0.6.5)
  • Spideroak's lines appear to just be because it watches that folder
  • it happens when I click sidebar items almost exclusively children of the home folder (though sometimes the home folder itself will trigger it too
  • Quicksilver may be related to the cause, but no action was saved (or even successfully executed)
  • I'm in 10.6.8 with NO OTHER known issues, relaunched finder, restarted, all the usual troubleshooting steps that came to mind have been performed

 

I believe this to be a Finder/scripting issue; NOT a Quicksilver/Paparazzi issue as it works also with Quicksilver quit as well. Having an app launch or activate all the time with a simple finder move is exteremely annoying just in the couple hours it's been around. it's going to severely kill normal daily productivity with as much as I used those folders in the sidebar. any help is greatly appreciated!

  • Jeremy Bechtold Level 2 Level 2 (220 points)

    AND I just remembered the first time I noticed this issue manifest itself... when I was downloading files and they hit my download folder. as soon as the downloads completed, Paparazzi launched. just happened again and I remembered it happening that way first.

  • Wevah Level 1 Level 1 (5 points)

    Author here. It's a bug in Paparazzi!'s Info.plist that manifests in OSs < 10.8 (so 10.6 and 10.7) due to me mistakenly using public.item instead of public.data for "any file type".

     

    Can you try this and see if it fixes the issue?

     

    - Right/control-click on Paparazzi! (0.6.5) and "Show Package Contents"

    - Open Contents -> Info.plist with any text editor

    - Do a search/replace for "public.item", replacing with "public.data", then save and close the file

    - Rebuild the LaunchServices database in the terminal via:

     

    /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchSe rvices.framework/Versions/A/Support/lsregister -kill -r -domain local -domain system -domain user

     

    Once that command finishes, see if the problem goes away. Let me know if it doesn't, too, so I can try to figure something else out!

  • Jeremy Bechtold Level 2 Level 2 (220 points)

    Much better... this did kill the constant launch/activation of Paparazzi. but there still seems to be a slight bit of leftover muddiness. I'm not sure if this will have any affect on it, but I have not had a chance to logout or restart since rebuilding the launchservices db. I have too many things open right now and a deadline looming, but I will restart when I break for lunch and see if that makes a difference...

     

    since following your instructions (and thanks for the swift response, Nate/Wevah - dev of Paparazzi), the launch of Paparazzi goes away. great. the first test pass through all the previously-offending items in the finder sidebar only caused a little flicker on the desktop after I passed through all the other items. after that, I could randomly generate the flicker, which tells me it's still trying to do "something" but launching Paparazzi is not what happens. it's very tolerable now since the focus goes right back to finder again after flicker, instead of another app. I'll follow up again after I get a chance to restart and probably repair permisisons since I tend to do that as routine maintenance anyways, esp when I've performed any kind of "fix" or update.

     

    to anyone else who finds this and needs to follow the instructions above -- the forum has broken the text string that should be used in terminal. I just pasted into bbedit first, cleaned up the space (created by the wrap in the middle of LaunchServices at the end of the first line).

  • pictopia Level 1 Level 1 (0 points)

    Thanks guys, I had exactly the same issue which was fixed following Nate/Wevah's solution. Great software by-the-way, thanks for keeping it free nate!