Posted: Wed May 31, 2006 9:52 am
I am just curious then, why sometimes it isn't started at all.Ethion wrote:Why can't it just be rosettta, being in the background.
As, it will start processing if a PPC binary is activated?
I am just curious then, why sometimes it isn't started at all.Ethion wrote:Why can't it just be rosettta, being in the background.
As, it will start processing if a PPC binary is activated?
If you want to know more about lsof and fs_usage, fire up your Terminal application (in /Applications/Utilities) and type man lsof or man fs_usage.arnoz wrote:Well, for me you're talking japanese right nowBut anyway, thanks a lot for all your help! Will continue to read this thread.
i really doubt it's Rosseta, considering the fact that rosseata would have to be universal...Ethion wrote:Why can't it just be rosettta, being in the background.
As, it will start processing if a PPC binary is activated?
Actually (and I hate to be a nitpicker) Rosetta wouldn't be Universal - it would be Intel only. Having a PPC translator on a PPC architecture would be weird at bestyelly wrote:i really doubt it's Rosseta, considering the fact that rosseata would have to be universal...Ethion wrote:Why can't it just be rosettta, being in the background.
As, it will start processing if a PPC binary is activated?
good point.bgannin wrote:Actually (and I hate to be a nitpicker) Rosetta wouldn't be Universal - it would be Intel only. Having a PPC translator on a PPC architecture would be weird at bestyelly wrote:i really doubt it's Rosseta, considering the fact that rosseata would have to be universal...Ethion wrote:Why can't it just be rosettta, being in the background.
As, it will start processing if a PPC binary is activated?
Two things to check:Travis wrote:OK, Adium definetly does cause the Translate process. I logged in holding down Shift, opened Activity Monitor – no Translate process. Then, before doing anything else, I launced Adium (1.0 SVN). The Translate process appeared in Activity Monitor right when Adium launched.
Wow, the first tip helped. It looks like Adium does cause Translate, but only because Adium launches Growl (for me, and many others), which then causes Translate.Catfish_Man wrote:Two things to check:
Get info on it in activity monitor and see what files it has open, and
Get FSEventer from versiontracker and see what files are touched while Adium opens.
Code: Select all
/
/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Support/mdimport
/System/Library/CoreServices/CharacterSets/CFUnicodeData-B.mapping
/System/Library/CoreServices/CharacterSets/CFCharacterSetBitmaps.bitmap
/System/Library/CoreServices/CharacterSets/CFUniCharPropertyDatabase.data
/Users/julian/Library/PreferencePanes/Growl.prefPane/Contents/Resources/GrowlHelperApp.app/Contents/Library/Spotlight/GrowlImporter.mdimporter/Contents/MacOS/GrowlImporter
/Library/Caches/com.apple.LaunchServices-014501.csstore
/usr/share/icu/icudt32b.dat
/usr/lib/dyld
/usr/lib/libSystem.B.dylib
/System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreText.framework/Versions/A/CoreText
/System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/ATS
/System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics
/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
/usr/lib/libicucore.A.dylib
/usr/lib/libobjc.A.dylib
/usr/lib/libstdc++.6.0.4.dylib
/usr/lib/libgcc_s.1.dylib
/usr/lib/libauto.dylib
/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore
/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServices.framework/Versions/A/OSServices
/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Metadata
/System/Library/Frameworks/Security.framework/Versions/A/Security
/System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
/System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration
/System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ColorSync.framework/Versions/A/ColorSync
/System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/HIServices.framework/Versions/A/HIServices
/System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/LaunchServices
/System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/DesktopServicesPriv
/System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
/usr/lib/libxml2.2.dylib
/usr/libexec/oah/translate
/dev/null
/dev/null
count=0, state=0x2
/tmp/com.apple.csseed.97
apple.shm.notification_center
/Library/Spotlight
/System/Library/Spotlight
/Users/julian/Library/Preferences/.DS_Store
count=0, state=0x2
/Users/julian/Library/Safari/.DS_StoreBeautiful. Works great.evands wrote:Download http://evands.penguinmilitia.net/GrowlI ... porter.zip
Replace with its contents the version in this location:
/Users/julian/Library/PreferencePanes/Growl.prefPane/Contents/Resources/GrowlHelperApp.app/Contents/Library/Spotlight/
(You can get there quickly via Go->Go to Folder in Finder).
My feeling is that given that the release project is nearly automatic (it's the Growl scripts which were modified for Adium, right?), this plus one other bug fix would justify a minor release since (1) it's been quite a while since the last one and (2) it's still probably a while for Growl Y.X, where Y.X is whatever that next big release is named.The_Tick wrote:The only reason I haven't released another Growl update to resolve this is that it isn't really a big issue. Thoughts?
I'd say release an update. Most of the people who use Growl are fairly technical, right? So they won't be bugged or confused by an update, because it'll take them 2 seconds to install. (Not that with Growl's update system there's anything confusing, but people are confused by anything.)The_Tick wrote:The only reason I haven't released another Growl update to resolve this is that it isn't really a big issue. Thoughts?
evands wrote:My feeling is that given that the release project is nearly automatic (it's the Growl scripts which were modified for Adium, right?), this plus one other bug fix would justify a minor release since (1) it's been quite a while since the last one and (2) it's still probably a while for Growl Y.X, where Y.X is whatever that next big release is named.The_Tick wrote:The only reason I haven't released another Growl update to resolve this is that it isn't really a big issue. Thoughts?