Re: Self corruption in CFBundle
Re: Self corruption in CFBundle
- Subject: Re: Self corruption in CFBundle
- From: Rosyna <email@hidden>
- Date: Tue, 7 Feb 2006 11:07:42 -0700
Hmm, I think if the NFS mount is a mount point on an HFS+ disk, this
could still occur.
The reason I brought that up because we've also had the bundle IDs
die, but that happens when the user had their home folder in a
different case as the one in NetInfo. Oddly, System Preferences goes
completely crazy in this situation. If you try to double click on a
preference pane in the home folder in this case, System Preferences
will ask to install it, then delete it if you click "Install". If you
have a home folder that's really on another disk, it'll make a new
entry in the /Volumes/ folder with a different case. This means when
you log out and back in, all your user files are "gone" since it
cannot fine any files in your home folder. Remember, never, ever use
isEqualToString: to determine if paths are equal on OS X.
Your issue does look different although I wonder why LaunchServices
would go psycho in this case.
Ack, at 2/7/06, Timothy J. Wood said:
On Feb 7, 2006, at 9:34 AM, Rosyna wrote:
This isn't the Metadata.framework doing it, so it has nothing to do
with the search field. It's the DesktopServicesPriv private
framework that's doing this. It's getting all the kind strings
strings to display in the open panel, which is ultimately a job of
the LaunchServices framework (the functions beginning with LS
below).
Ah, I was just mislead by the 'MetaData' in the backtrace and
wasn't paying attention to that part much :)
I have to wonder, is this on your computer? If so, does the case of
your home folder on the hard drive differ from the case of the path
of the home folder as listed in NetInfo manager? Such as Tim vs tim
or something?
The running copy of OmniOutliner is on a local HFS+ disk. The
other copy is on a NFS mount (case-sensitive) in a directory
generated by our automated build system. My home folder is on the
NFS mount, too, but that should have nothing to do with this as
neither copy of the app is near my home directory.
We should really just move our /Network/Applications folder to
/Network/DontLetLaunchServicesSeeMe. We've run into bugs with this
with Spotlight importers (random copy picked), and Automator actions
also (Automator loads duplicate actions from multiple copies of the
app w/o regard for version numbers, etc).
We tried switching our file server to AFP a while back and it was
totally great in that we could easily unmount it (thus avoiding all
the fragility in the frameworks with multiple copies of an app), but
really lame in that the AFP server doesn't handle any significant
load w/o going insane.
-tim
--
Sincerely,
Rosyna Keller
Technical Support/Holy Knight/Always needs a hug
Unsanity: Unsane Tools for Insanely Great People
It's either this, or imagining Phil Schiller in a thong.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden