Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the '10.4: Fix a post-10.4.3-update SystemUIServer crash' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
10.4: Fix a post-10.4.3-update SystemUIServer crash
Authored by: chaos215bar2 on Nov 07, '05 03:53:18AM

This isn't exactly a bug. As fracai suggested, the installer is not replacing the bundle. It is only designed to replace a few files within the bundle. If the installer contained all files for all the bundles it updated, it would be much larger than necessary. You might want to suggest having an option to support turning spotlight off, but there is no reason Apple should specifically support renaming that one particular bundle.

You should also re-run the system update with the Search.bundle named properly. This way, you'll get the most up to date version of it and can rename it again afterwards, if you want.



[ Reply to This | # ]
10.4: Fix a post-10.4.3-update SystemUIServer crash
Authored by: paulsomm on Nov 08, '05 03:14:28PM

Agreed, but I'd still classify this as a bug. When updating a system component, the updater should be verifying first if the component to be updated exists. If it does not, ideally the update should abort with an error message (a la trying to update any of the i-applications when you've moved them out of the Applications folder).

While you can argue that Apple expects their bundles to exist, I'd counter with what if disk corruption had caused that folder to be inaccessible or if a third party application made modifications that weren't expected?



[ Reply to This | # ]