Some iCal users have noticed a problem whereupon trying to publish their calendars to Apple's MobileMe service, they receive an error claiming the MobileMe configuration is not correct.

KiltedGreen:

"I try to publish [using iCal] it comes up with a dialog with the Subject above and says inside: 'Calendar could not be published. MobileMe member name is not correct. Publishing to PubSubErrors requires a properly configured NSBundle /Applications/iCal.app (loaded) account.'"

Despite this error, when users go to the MobileMe System Preferences pane the credentials seem to be accepted. Additionally users can access their iDisks, send and receive email, and otherwise use MobileMe perfectly fine.

For some, this happens with only with one or two calendars, but for others this affects all calendars. Users have had temporary success in resetting the sync data for the calendars, but this seems to result in the problem recurring.

There are several things users can try to correct this problem:

Fixes

Completely sign out of MobileMe Quit iCal and then in the MobileMe system preferences click the "Sign Out..." button and confirm signing out. Log back in to the account, and then in the "Sync" tab click the "Sync Now" button and ensure Calendars are checked.

Reset sync data In addition to logging out of MobileMe, users can try resetting the sync data on their computer, or on MobileMe. This is done in the "Sync" tab of the MobileMe system preferences by clicking the "Advanced" button. For the sync reset, choose "Calendars" from the drop-down menu instead of "All Data".

For some iCal users the search functions, which rely on Spotlight indexing of the calendars, has suddenly stopped working.

Apple Discussions poster chris_hb writes:

"Yesterday, when I tried to search for an event in iCal the search came up empty. At that time the search in spotlight was still working and gave me the correct link to iCal. However, the search using the search field directly in iCal always fails."

This problem may exist only with iCal's search, as users have been able to find calendar events through the system's Spotlight search. Users have tried forcing Spotlight to index the calendar folder, as well as reinstalling the latest Mac OS X update and removing old calendar data from previous versions of iCal, but these efforts have not been successful.

It seems this problem can manifest itself in a variety of situations, and as such, there are several fixes for this problem that users have found:

Fixes

Put an end date on recurring events It appears that, in some instances, the omission of an end date on repeating calendars can cause problems with Spotlight indexing. It is recommended to add an end date to all repeating calendars, even if the date is 100 years in the future.

Temporarily exclude Macintosh HD from spotlight indexing It is possible that the inclusion and exclusion of the hard drive in Spotlight's privacy list may toggle proper spotlight indexing of the hard drive again. To do this, go to the spotlight system preferences and in the "Privacy" tab click the "+" and add the Macintosh HD to the list. Then wait a while for spotlight to index again, and ten remove Macintosh HD from the privacy list and wait for the index to be rebuilt again.

Remove iCal cache and preference files Locate and remove the com.apple.iCal.plist file from the /username/Library/Preferences/ folder and also remove any iCal-related files and folders from the /username/Library/Caches/ folder. Corruption in these files may prevent iCal from functioning properly.

Rebuild the launch services database Its possible that spotlight searching is being inhibited by another program users may have installed which has reset the launch services, making indexing require the presence of a plugin from the application. To rebuild the launch services, enter the following command in the Terminal (copy and paste):

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

When the command has run, reboot the computer and then run the command again.

Workaround: Use another search application While Spotlight is a fast and well integrated search solution, it is not always the best and can have problems. Users can opt for another search program to find files, though non-indexing solutions will take longer to find the desired files. One of these options is EasyFind from Devon technologies.

Some owners of unibody (Late 2008) MacBook Pros have experienced an issue in which the laptop's screen will suddenly start blinking.

Apple Discussions poster Hoojiemoster writes:

"My computer had a hard time digesting all of the new messages being added in Mail. Everything slowed down temporarily and Mail disappeared and was inaccessible. When it finally reappeared with the new emails, I noticed the intermittent blinks."

This problem seems to be relatively random, although, for some users, it seems to have started after a period of heavy workload. It may occur only once or twice, but for some users, the blinking happens rapidly. This is clearly an issue with the MacBook Pro only, and has something to do with the graphics drivers trying to manage the dual GPU setup. Non-pro MacBooks do not have this issue, and it only happens on the MacBook Pro when users are utilizing the GeForce 9400M integrated GPU, which gives it the same graphics configuration as the non-pro MacBooks.

This problem will most likely need to be addressed by Apple in a software update, but until then users may try the following:

Potential Fixes

Reset PRAM Reset the computer's parameter RAM by rebooting and holding the options-command-P-R keys until the machine cycles through a few restarts. Then let the keys go and allow the machine to boot properly.

Reset and adjust display settings Go to the "Displays" system preferences and toggle between a few resolution settings. Additionally, users might try clicking the "Detect Display" button.

Workaround

Currently the problem seems to disappear when users run off the dedicated GeForce 9600M processor, and it is recommended to do this unless battery conservation is of the utmost importance. Using the dedicated graphics processor will also increase the computer's performance. To do this, go to the "Energy Saver" system preferences and check the option to enable "Higher Performance" graphics. This will only take effect after a logout and login again.

Several users have reported an issue in which QuickTime cannot display web-based media content. When embedded media is accessed, the QuickTime plugin will display an error symbol.

Apple Discussions poster swairah writes:

"I have a problem with my Quick time player which is i cant see any trailers in apple site and i also cant download any mp3 whenever i try to download or watch a trailer the page turn black and there is a Question mark on the Quick time player logo."

For some users, this problem results in the question-mark symbol, but for others the QuickTime plugin gives an error message stating the users should download and install the latest version of quicktime, even though they are fully updated with the software. Users have tried addressing this problem by reapplying the quicktime update, but this has not fixed the issue.

There are a couple of procedures users can try, but this problem remains largely unresolved.

Fixes

Remove "QuickTime Plugin.webplugin" component QuickTime installs two plugins into the /Macintosh HD/Library/Internet Plug-Ins/ folder: The "plugin" and the "webplugin". While both of these items should work fine together, some users have found that removing the "webplugin" file has fixed playback issues in QuickTime. Alternatively, users might try reinstalling quicktime after removing one or both of these plugins, just in case one became corrupted.

Remove unneeded components and plugins For web browsers, users should try disabling or removing all internet plugins from the /Macintosh HD/Library/Internet Plug-Ins/ folder except for the QuickTime plugins. Additionally, in the /Macintosh HD/Library/QuickTime/ folder, remove all third-party components (if unsure which are third-party, just remove them all temporarily). Then restart the computer and try loading the media in the browser again. If all is well, add components and internet plugins back in small groups, restarting between each group to troubleshoot them.

Clear Safari Cache, or even reset Safari For Safari, users might try resetting the temporary internet data such as cache files and cookies. The Cache is usually the main culprit of pages not working well, and while a few reloads of the page should reset the cache for that page, users can ensure the page is loaded fresh by going to the "Safari" menu and choosing "Empty Cache". Additionally, users might try completely resetting Safari by using the "Reset Safari" option in the same menu.

Several users have described an issue where, upon activating the screensaver, the computer crashes.

Apple Discussions poster alamosakid writes:

"Whenever I turn my screensaver on, my MacBook freezes. My screensaver is set to mosaic pictures, I think. When I drag my mouse to the lower right corner, the screensaver doesn't start and all I can see is the time (if the time ever shows up). Then I shake my mouse, etc, to try to get back to my desktop and my computer freezes and I have to restart it."

This problem may occur with third-party screensavers, but also has happened with some of the built-in screensavers that deal with the iPhoto library. Problems can include a full system crash, or a System Preference crash, but, most often, the system will hang with the screensaver starting up. For instance, with the photo gallery screensaver, users might just get a black screen with the text "Searching for photos" in the center.

The fixes for this issue include reinstallation the affected screensaver, or in the case of built-in screensavers, tackling potential problems with the iPhoto libraries that might be causing the hangups. However, while the specific problems might be anything, users can regain control of their computers with the following suggestions:

Fixes and Workarounds

Use the terminal to kill the screensaver When the screen is frozen or is hanging with the screensaver activated, users may not be able to interact with their machines through the keyboard, even with a force-quit key sequence (opt-cmd-exc). Using screen sharing will only show the same screen on the remote computer as well, so the only way to regain control is to kill the screensaver using the terminal.

To do this, with a second computer on the local network, open the terminal and enter the following:

ssh username@COMPUTER

In this command "username" is the name of the administrator account on the affected computer, and "COMPUTER" is the name of the computer (ie: Johnnys-Laptop). Alternatively, it could be the IP address of the affected computer.

NOTE: This requires the computer to have "Remote Login" enabled in the sharing preferences.

After logging in, enter the command "top" to display the running processes on the computer. Search in the list for the "Screen Saver" application, and note the number to the left of it (should be a four-digit number). Press "Q" to quit "top", and then enter "sudo kill number", where "number" is the four-digit number noted earlier.

Upon pressing enter the screensaver should exit and reveal the desktop again. From here, it is recommended that users change the screensaver to prevent any further hang-ups.

Manually edit the screensaver preferences For users where the screensaver preference pane causes crashes, editing the screensaver preferences manually may be the only option. To do this, go to the /username/Library/Preferences/ByHost/ directory and open the com.apple.screensaver.(number).plist file in a text editor. From here users can do the following:

Set the screensaver activation time to infinity Under the "idleTime" key, set the integer to "0" and save the file.

Change the screensaver to a built-in one In the "moduleName" key, change the name to "Flurry", and in the "modulePath" key, change the path to /System/Library/Screen Savers/Flurry.saver. Alternate names can be used from the files in the /System/Library/Screen Savers/ folder.

Users have reported a number of issues with iPhone OS 2.2 including:

• Disappearing applications (both Apple's and third-party), loss of WiFi connectivity, loss of 3G or EDGE signal strength and an inability to sync with iTunes.
• Fuzzy, pixelated images
• Weak or non-existent signal, failed installation, and more.

For the past few months, MacFixIt has reported several issues in which users have had problems with strange time offsets when using 24-hour formats, as well as problems with the time zone formatting between iCal and Exchange calendars. Recently for some users have reported problems with iCal and the synchronized MobileMe calendars having shifted event times.

Apple Discussions poster Jack McDonald writes: "I've been having a HUGE issue with events posted to iCal and Mobile Me. No matter where I post/create and event/appointment, it shows up on the iCal/MM one hour different. [As such], my iCal on my Mac, my Mobile Me and my iPhone do not have the same start times."

iCal and MobileMe are integrated with the system's time settings but in addition both have their own time settings. If any of these settings are improperly set, users can experience time mismatches in their calendars.

Fixes

Set system Time Zone The first thing to do: check that the system's time zone is set correctly. Go to the "Date & Time" system preferences pane and in the "Time Zone" tab ensure both the correct time zone and closest city in that time zone are selected for the user's location.

Set the iCal and MobileMe Time Zone In both MobileMe and iCal there is support for time zone offsets to calendar data, which can be useful for users who travel between different time zones and need calendar data to always be accurate to the current time zone. To set this option in iCal, go to iCal's preferences and in the "Advanced" section check the option to "Turn on time zone support". Upon doing this a menu will appear at the top of the iCal window where users can select the current time zone. For users who do not use iCal in multiple time zones, it is recommended to disable this option. Likewise, this option is available in MobileMe. To access it, log into MobileMe and select the calendar. Then click the gear menu and select "preferences", and in the "Advanced" selection turn on the time zone support option. Then select the desired time zone.

NOTE: Users might try removing iCal's preferences file (named "com.apple.ical.plist" and located in /username/Library/Preferences/) as well, since a problematic preferences file can result in preferences not being saved or accessed properly.

Reset calendar sync date It may be possible that this time problem could be caused by a corruption in the synchronized data between iCal and the MobileMe "cloud". To reset the calendar sync data, open the "MobileMe" system preferences and click the "Advanced" button in the "Sync" tab. Then click the "Reset Sync Data" button and from the drop-down menu choose "Calendars" and then select the right arrow to replace the content on the MobileMe servers. Click "Replace" and the calendar data should be reset.

Completely reset synchronization resources If users cannot get the aforementioned fixes to work, a complete reset of synchronization data should fix the problem. This procedure will completely revert the system to the way it was before the initial synchronization with MobileMe, and then resync all data back to MobileMe again. The procedure for doing this is outlined in this MacFixIt article.

Some users have found that sound output is not working after the Mac OS X 10.5.5 update.

Apple Discussions poster TurkiSh writes:

"I just finished updating my Leopard from 10.5.4 to 10.5.5 and I noticed when it booted that... I have no sound at all."

This issue seems, in most cases, to be caused by a faulty PRAM setting. For users who have just updated to Mac OS X 10.5.5 and are experiencing this problem, the common PRAM reset may be a quick fix.

Fix: Reset the PRAM Reboot the computer and immediately hold down the options-command-P-R keys all at once. The computer will continually reset and make the boot chimes while these keys are held. Let the computer go through a few of these cycles and then release the keys, allowing the computer to boot normally.

Feedback? http://www.macfixit.com/contact.

Some users who have updated to iTunes 8.0.2 are experiencing an issue in which no movies or songs can be purchased. This problem occurs despite having ample credit users cannot purchase any songs or movies, but also if users are purchasing directly with charge cards.

Apple Discussions poster Bryce Lim writes:

"After updating to 8.0.2, I can't purchase anything on iTunes account. Every time I try to purchase music, a TV show or an application I get the error message that '...due to a problem with the iTunes store I have no available store credit for purchasing...' 'I don't have any store credit, I've been trying to purchase with my credit card like I always have been.'"

For many users affected by this problem, credit on the accounts seems to disappear and then reappear at seemingly random times, which can be concerning to users with large amounts of credit. Luckily it seems the amount of credit is still there, just inaccessible for a while. Additionally, users with gift cards are having problems redeeming them.

If users are concerned about their accounts and the credit amount on them, it is recommended to call Apple directly for confirmation on the credit available. Apple's support is available at this link or users can try calling Apple at 1-800-MY-APPLE. Meanwhile, users can try re-logging into their iTunes accounts to help fix the problem.

Fix: Reset iTunes' account login It appears that this problem might be with how iTunes is logging into the iTunes store, and as such users have had success by resetting their logins to the store. To do this, from within iTunes sign out of the store account, and then quit the program. Relaunch iTunes and sign back in, then try the account again.

There is a small problem affecting some iTunes users in which, upon trying to purchase songs from the iTunes Store, the program reports and error regarding not enough memory available to complete the purchase.

Apple Discussions poster Mike-F writes:

"When trying to buy a track from the iTunes store, I'm getting the message "Could not purchase (track name). There is not enough memory available" I have plenty of space on my hard-drive."

This problem seems to stem from error in the iTunes code interacting with the iTunes servers, as opposed to any corruption in support files; it seems to occur for both Windows and Mac users. To overcome this problem, some users have been trying to clear their systems of various files in fear that they were running out of space. Users should not do this. If computers are running low on hard drive space the system software will issue a warning and the system will exhibit other odd behavior such as generally running slow. Additionally, users have been concerned about available RAM for programs to use, but this problem has cropped up on systems with 4+GB of RAM.

After complaining to Apple support, some users received a response indicating that this this problem resided with iTunes servers. However, despite Apple's claim that the problem was fixed, users are still experiencing problems.

It seems Apple has addressed this issue for iTunes 8 users with the latest iTunes 8.0.2 update, but this might not be an option for users who either do not wish to use iTunes 8, or who cannot upgrade because of system requirements.

Feedback? http://www.macfixit.com/contact.

Safari 3.2, released a few weeks ago, has been prone to crashes when users attempt links in tabs. The release of Safari version 3.2.1 specifically addresses the issue of crashes pertaining to opening links in new tabs. While this has solved crashing problems for some users, it has not for all users. Some users have found that certain pop-up window behavior still causes the program to crash, regardless of whether or not popup blocking is turned on (see our previous coverage).

Apple Discussions poster Raymond Smith writes:

"3.2.1 still crashed for me. U dud the auto update, repaired disk permissions, and started surfing the APPLE STORE (how ironic). I clicked on iPod Touch, clicked on "laser engraving" icon. A smaller window started to appear (a pop up)... crashed - multiple time - same sequence."

It should be noted that while this update fixes a prominent cause for crashing in Safari 3.2, there are other causes for Safari crashing which have known fixes.

More Fixes

Reset Safari Users who're experiencing persistent crashing in Safari should first reset Safari using the option in the "Safari" menu. It is recommended to check all options to reset and hopefully this will fix the problem.

Remove Input Managers As described previously, users might try removing any input managers installed in the mentioned folders. Additionally, users might try disabling the new anti-phishing features in Safari 3.2.x.

Delete the history plist file Some users have cured certain crashes by removing Safari's history file, which is located in the /username/Library/Safari/ directory and is called History.plist. Upon removing this file, Safari will create another one. Beyond just this file, users may also try removing others in the same "Safari" directory. It is recommended to first back up these files, as they may contain important information such as bookmarks.

Remove the Safari cache database While resetting Safari should empty and reset the caches, it is possible that corruption in the database file could prevent it from being accessed properly, even for emptying. As such, users should try removing it manually by entering the following command in the terminal (copy and paste):

rm $(getconf DARWIN_USER_CACHE_DIR)com.apple.Safari/Cache.db

Feedback? http://www.macfixit.com/contact.

An issue in which movies purchased from the iTunes store will not play on external displays has plagued owners of the Late-2008, "unibody" MacBook computers. When playback on external displays is attempted, iTunes will give an error claiming the display is not authorized.

Apple Discussions poster maxyourmacs writes:

"I rented a movie from the iTunes store yesterday and when I tried to play it on my external display, it gave me a warning/error that the display was 'not an authorized HDCP display' and it would not play. Plays fine on the small MacBook screen, just nothing external."

This issue was first thought to be an incompatibility in the Display Port, or at least the conversion of the Display Port to legacy connectors. However, Apple has released a QuickTime update that resolves the issue, specifically for Display Port-equipped Macs.

The QuickTime update is available through Software Update, and should be available as a standalone update on Apple's Download page soon.

Unfortunately, this update does not address a limitation in which users not being able to view HD content on external displays. It seems only to be a fix for the issue in which non-HD movies trigger Apple's implementation of HDCP copy protection. Currently, the only "HDCP compliant" devices are internal displays as well as those that are connected natively via DisplayPort.

Feedback? http://www.macfixit.com/contact.

Crashes Users report persistence of crashes under Safari 3.2.1. Hundreds of users reported similar crashes after updating to Safari 3.2, which was released a little more than a week ago.

A sampling of reader reports:

• "Still crashing. Safari 3.2 was crashing, I changed back a version. Tonight I went to 3.2.1 and it has crashed every two or three minutes. Going back again. "
• "PithHelmet still crashes it. AdBlock for Safari works, but I like PithHelmet's contextual selections and the ability to reload unfiltered."

The first workaround you should try when encountering this issue is to turn off the "Warn when visiting fraudulent websites" option in Preferences.

Next, you might need to get rid of Input Managers. Look in the following folders:

• /Library/Internet Plug-Ins
• ~/Library/Internet Plug-Ins
• /Library/InputManagers
• ~/Library/InputManagers

and remove any third-party items.

Possible culprits include PithHelmet, SafariStand and Concierge.

As we stated after the release of Safari 3.2, Input Managers reach right into an application and alter its code. This puts the behavior of the affected application outside the control and responsibility of its developers: a recipe for troubleshooting problems. That's not to say that issues absolutely will ensue as a result of Input Managers, but you, as a user, must do some cost/benefit analysis. If the functionality of a specific Input Manager or set thereof proves crucial, you may well choose to assume the associated risk.

Slowness Meanwhile, some users report significant slowdown in loading pages and performing other operations under Safari 3.2.1. One MacFixIt reader wries:

"I updated as soon as Software Update said 3.2.1 was available and was sorry within 10 minute. It loads sites extremely slowly. Common sites that I visit that normally load immediately in 3.2 take a very long time in 3.2.1."

See our guide to improving Safari's performance and our follow-up collection of tips for procedures that might remediate the poor performance.

Feedback? http://www.macfixit.com/contact.

Apple has released Safari 3.2.1, which the company says includes "stability improvements and is recommended for all Safari users."

The new release is available in both Tiger and Leopard editions.

Safari 3.2.1 requires Security Update 2008-007 and Mac OS X 10.5.5.

Problems after updating? Please let us know.

Several users have noted recurrence of a relatively longstanding issue in which iTunes suddenly stops connecting to the iTunes store. When users try to enter the store they may receive a "network connection timed out error".

Apple Discussions poster ruffstuff writes:

"I keep on getting this error now "We Could Not Complete your iTunes Store Request. The Network Connection Timed Out". What is depressing is that about 24 hours ago, i was still able to download a video from the iTunes store? Now I can't even sign into the iTunes Store."

The iTunes store uses standard web port numbers and protocols for network communications, which makes accessing the store essentially like viewing a web page. As such, if the web is working, the iTunes store should work. However, users experiencing this issue are otherwise access the internet and do other network-based activity, only receiving a timed-out error when accessing the store. Users have tried targeting the application itself by removing various preferences as well as repairing permissions on the boot drive, but this has not resolved the issue.

This problem has affected both Mac and Windows users, and indicates that there is a problem with the user's firewall or router connections, because the problem seems to suddenly appear and not be caused after any updating or program modification. In support of this postulation, one user took his Mac Mini to another location and was able to connect properly, which indicates the problem is either in the broadband router or in the ISP's account settings.

Additionally, one user replaced his home router and the problem went away. As such, users (especially laptop owners) are encouraged to try their iTunes connections through different broadband accounts and setups.

While replacing the router and other network hardware seems to fix the problem for some users, there are several things users can try before spending money on a new router. For some of these fixes, users will have to edit the settings on their routers, and should consult their user manual for exact instructions.

Potential Fixes

Wait it out For some users, the problem seems to suddenly disappear just as fast as it arrived. This indicates the problem can be overcome, but it also indicates potential conflicts between iTunes and the router software which could crop up again in the future.

Setup DMZ for the affected computer Routers contain firewalls and other network technology that may be causing this problem, but most also have support for a "Demilitarized Zone" (DMZ) computer which is not put behind the firewall. This is a convenient way to test the router, and users should first find what IP address is being given to their computer, and then set that IP address as the DMZ computer. If iTunes connectivity works, then the problem is clearly with the firewall settings in the router.

Ensure ports 80 and 443 are open The router should have internet ports 80 (http) and 443 (https) open by default, but it is possible some setting has changed to restrict these ports in some situations, possibly by them being reserved for a specific IP address on the network through port forwarding. These settings can be automatically set in some cases, so users should check and remove any port forwarding or port triggering settings that might include these numbers.

Disable Firewalls Routers usually contain some sort of firewall which is enabled by default. As a test, users might try disabling the various firewalls that are on the router. These might include NAT, SPI, or content filters, in addition to "true" firewalls which block specific ports and services. If any options to disable firewalls are available in the router's settings, users are encouraged to try turning them off.

Toggle UPnP settings Most modern routers support a network technology called Universal Plug and Play (UPnP) which automatically assigns ports and other network settings to computers behind routers in an "on-demand" fashion, which helps reduce the amount of configuration that needs to be done. Users might try connections with UPnP both enabled and disabled.

Update Router Firmware If various settings do not work, users might ensure their router's firmware is up to date. Many have an automatic-update feature, but most require a user to download a file from the manufacturer's support site and then upload it to the router. If this does not fix the problem then users may have to replace their routers. Unfortunately there seems to be a trend that this problem revolves around several Linksys Wireless router models, and it could be an bug in the firmware of these models that's causing the problem.

Some users have experienced an issue in which iTunes 8.0.2 will not open. When users try to launch the application it quits and gives an "unknown error".

Apple Discussions poster ChkRazr writes:

"[My mac crashed and] I needed to hold down the "Power" key, which I did. Upon restarting, however, the Mac seems to be running okay but now my iTunes application refuses to load and I get the following error message: The iTunes application could not be opened. An unknown error occurred (13010)."

This problem has affected users who have crashed with a kernel panic (where the screen dims and displays white text explaining the computer needs to be restarted), but it has also happened for users who have updated iTunes. When applications crash or if the system freezes in the middle of an operation, it is possible for essential files to beoe corrupt. iTunes 8 contains support files for the "Genius" feature, which seems to be the root of this problems, and users have been able to successfully launch iTunes by first removing the Genius database.

Fix: Remove the Genius database In the "Finder" go to the /username/Music/iTunes/ directory and delete the "iTunes Library Genius.itdb" file. This should allow the program to launch again. This file will be recreated upon first use of the "Genius" feature.

Users who have updated to iPhone OS 2.2 are facing some significant issues, including problems with third-party apps, Internet connection issues, problems deleting email and more.

Read More...

We continue to report on dropped, slow or sporadic wireless connections after AirPort Update 2008-004. Among the common symptoms:

• After systems wake from sleep, they must be rebooted in order to recognize the AirPort network.
• Wireless network is at full strength, but the actual connection drops off repeatedly
• Slow transfers

The problem is surprisingly widespread--reports in the MacFixIt inbox and Apple's discussion ports are rampant. Yesterday we reported two potential solutions for the problem (deleting AirPort-related plist files and changing DNS entries), and today we introduce two more fixes that, based on reader reports, are proving more effective.

Fix #1: One particularly effective fix, noted in our AirPort/Wireless troubleshooting tutorial, involves switching wireless channels. In order to switch channels on AirPort Base stations, use this process:

• Open AirPort Admin Utility, located in /Applications/Utilities.
• Select the appropriate (afflicted) base station and click Configure.
• Enter the base station password if necessary.
• Click AirPort, and then choose a new channel from the Channel pop-up menu.

Anecdotal reports of success:

• "I experienced severe AirPort dropout last night, until I went into three AirPort routers and changed the channel. [...] Everything appears fine now!"
• "I've experienced dropped connections for a few months now on both the early and late 2008 Macbooks and with different routers. After numerous changes, the one that has work for me was to simply change the channel from "Auto" to channel "6". Knocking on wood here, but so far so good."

Fix #2: Turn off WPA Try turning off any wireless encryption methods in place. This can be accomplished using the AirPort Admin Utility (located in Applications/Utilities). Alternatively, try switching to a different encryption method.

This fix is obviously less than ideal, but is the only procedure that allows a stable connection in some cases.

In iTunes, users usually can click and rename songs, as well as edit metadata in the "info" window; however, some users may find that songs in their iTunes libraries are not directly editable.

Apple Discussions poster stn774477 writes:

"I have a MP3 called "Ain't Talking 'Bout Dub" by Apollo 440. Itunes has it as Apollo Four Forty. Itunes allows me to change it to Apollo 440 and it keeps the change but then when I play the song it instantly changes back to Apollo Four Forty."

For some users, this problem may be due to user-level restrictions. This can occur either if permissions on the files are incorrect, or if files are locked. Users should check the individual files by right-clicking them in iTunes and selecting the "Show in Finder" option. Next, users should get info on the file and ensure that their username is listed in the "Sharing & Permissions" section and has been granted both "Read & Write" privileges (users may need to click the lock and authenticate to make changes). Additionally, in the "General" section, ensure the "Locked" checkbox is unchecked.

If this is a problem for many song files, especially after a restore (such as from Time Machine), users can try changing permissions on their whole iTunes library by locating the parent folder for the iTunes library (usually /username/Music/iTunes/) and get info (Command-I) on that folder. Next, ensure the username and permissions are correct for that folder and use the gear menu at the bottom of the info window to propagate permissions to all enclosed files. This should reset all files' permissions according to those set on the parent folder.

If the files are properly accessible and users cannot edit any song in their library then this problem may be due to a corrupt iTunes library. Users should try removing the file from the iTunes folder and then relaunch the program. iTunes will create a new library, and users can then drag the "iTunes Music" folder to the iTunes window to reimport their songs.

Apple has released iPhone OS 2.2. Among the listed improvements:

Enhancements to Maps:

• Google Street View
• public transit and walking directions
• display address of dropped pins
• share location via email

Read More...

Apple has released iTunes 8.0.2, which Apple says improves stability and performance and provides a number of important bug fixes, including:

• Addresses a quality issue creating MP3s on some computers.
• Fixes a connectivity issue with the iTunes Store when using some Internet proxies with Mac OS X.
• Improves accessibility with VoiceOver.

The new release is available as a 57.8MB standalone download, or through Software Update.

Problems after updating? Please let us know.

When Software Update detects newer versions of software available, users may be required to enter an administrator password and the updater should then apply the updates, sometimes requiring a restart to go into a special "update" mode. Some Mac OS X users have experienced problems with this procedue, in which trying to install an available update they get a privileges error.

Apple Discussions poster BJ Bignell writes:

"This morning there were four updates available for my Mac...During the install, I received an error message: Some of the checked updates couldn't be saved. You do not have appropriate access permissions."

This problem has affected users through various iterations of Mac OS X, and might apply either to all updates, or to only certain updates while allowing others to be installed properly.

This problem involves the location where the updates are being downloaded to not being accessible by the system. This is most likely due to a permissions problem that can be addressed manually, and as such there are several things users can do:

Fixes: Reset permissions on the updater directory The folder in which Software Update stores updater packages should be readable by the system. As such users should ensure the ownership and permissions for this folder are set properly. To do this, first locate and get information on the /Library/Updates/ folder. At the bottom of the "get info" window the ownership and permissions should be as follows:

If the permissions are different, click the lock to authenticate and then change the permissions accordingly. Then click the gear menu and choose "apply to enclosed items". When this is completes, try the updates again.

Remove files in the updater directory In addition to resetting the permissions on the updater directory, users can remove all downloaded packages from the folder and re-download them again using Software Update.

Workarounds: Manually apply updates All updates that are available through the Software Update utility should be available for download from Apple's support website. To obtain a desired download, search or browse for it here.

While this ability to install use multiple operating systems on Macs is convenient, in some instances problems with a non-Mac OS X system installation can prevent users from being able to boot back into Mac OS X.

Apple Discussions poster clv92 writes:

"I have parellels on my iMac but I sometimes still restart in windows using boot camp. When I tried to restart using boot camp today I am stuck in a loop of windows xp starting and trying to run diskcheck, not finding it and trying to restart windows again. It just goes in a loop."

Holding various key combinations to boot into a healthy OS X partition may not work for users, resulting in no apparent way to get the computer to boot again. This kind of problem usually indicates the computer's PRAM, which holds boot volume information, is set to boot from the problematic drive partition. Additionally, the PRAM settings might be corrupt, which may prevent some of the bootup key commands from working properly. For users stuck with this kind of problem, the key is to reset the PRAM and then immediately manually choose the desired boot system.

Fix: Reset the PRAM and choose the boot system When the system resets again, hold down the options-command-P-R keys all at once and let the system go through a few reset cycles before releasing the keys to let the computer boot normally. Immediately after releasing the keys, users should hold the options key so the system goes right to the boot menu instead of attempting to boot from the default OS (which could be the corrupted OS that could have caused the problem in the first place). When the boot menu loads, select the healthy operating system disk and press enter. This should allow the system to boot properly.

Apple has released Apple TV software update 2.3, which includes the following significant enhancements:

• AirTunes Streaming from Apple TV: Music can be streamed via AirTunes to Airport Express speakers or other Apple TVs in your house.
• Third-party Remote Controls: Apple TV can now learn other remote controls and use them in addition to the Apple Remote.
• Playlists: Playlists in iTunes that contain Movies, TV Shows, Podcasts, and Music Videos can now be seen on Apple TV.
• Music Volume Control: Support for volume control in Music.

To update your Apple TV to the current software version, select Settings > General using your Apple Remote, then Update Software. You can then download the update and choose Update Now.

Problems after updating? Please let us know at http://www.macfixit.com/contact.

When users wish to list and manually choose from all available boot volumes, holding the options key down will display locally bootable volumes. Some users have noticed that this boot menu has started displaying other boot options than the desired and expected ones.

Apple Discussions poster Richard Pini writes:

"I have two volumes on [my computer]; one large ('Macbook') with all my work, etc. on it, and one small ('Rescue')...When I hold down the option key to switch between boot volumes, my choices are now 'EFI Boot' (instead of 'Macbook') and 'Rescue', even though in the finder, 'Macbook' shows up normally."

This change seems to have occurred as a result of some modification to the volume structure on the drive. For the most part, this issue has occured upon restoring a clone of the hard drive after upgrading the drive to a larger one, specifically when users move their internal drives to an external drive enclosure, then clone the data to new hardware installed in the computer.

Despite the "EFI Boot" name showing in the boot menu options, volumes can boot normally, and the drive will appear with the proper name in the Finder. As such, users might safely opt to do nothing; however, users might try the following to prevent the name change.

Potential Fixes

Try a different cloning scheme While cloning should be a bit-for-bit transfer, it is possible that small differences in the drive structure can be overlooked by cloning software in certain situations. As such, users might try alternate cloning methods, such as the following:

• Clone to a temporary external disk, then replace the internal disk and clone back.
• Put the new disk in an external enclosure and clone to it, then replace the internal disk with the newly cloned one.

Use a disk utility to repair the drive Obtain a copy of "TechTool Pro", "Drive Genius", or "DiskWarrior" and perform a repair on the drive. Users can try running the verification routine available via "Disk Utility", but this has generally not been as in depth of a scan as third-party disk utility software.

Change the default startup disk in the System Preferences This may not do the trick, but users can try changing or reassigning the default startup volume in the "Startup Disk" system preferences. This might have an effect on firmware settings which could be displaying the volume name in the boot menu.

Reset the PRAM PRAM holds some boot information, and as such users might benefit from a PRAM reset. To do this, reboot the system and hold the options-command-P-R keys all at once until the system goes through a few reset cycles, and then release the keys and allow the computer to boot normally.

Several users have noted dropped wireless connections after AirPort Update 2008-004. The problem appears to be widespread, with dozens of MacFixIt readers and hundreds of Apple Discussions threads posters reporting it. Among the symptoms:

• After systems wake from sleep, they must be rebooted in order to recognize the AirPort network.
• Wireless network is at full strength, but the actual connection drops off repeatedly
• Slow transfers

The following fix may provide, at least temporary, relief:

Navigate to /Library/Preferences/SystemConfiguration (this is the Library folder at the root level of your hard drive) and delete the following files:

• com.apple.airport.preferences.plist
• com.apple.network.identification.plist
• NetworkInterfaces.plist
• preferences.plist

restart your Mac.

Next, add a different DNS servers, such as those from OpenDNS, to Mac OS X's repertoire. Open System Preferences and click "Network." Select "Built In Ethernet" and click Advanced. Select the DNS tab and add:

• 208.67.222.222
• 208.67.220.220

If you are experiencing similar issues, please let us know at http://www.macfixit.com/contact.

Yesterday, Apple released a firmware update for the glass trackpads on the new MacBook and MacBook Pro computers to "address an issue where trackpad clicks may not be recognized." For most users this update has been a welcome solution the ongoing problem of glass trackpads periodically losing functionality, but some users are having trouble with the update.

Some users are experiencing installation failures, accompanied by the error message 'The Firmware update did not complete. Communication with the device failed."

By now the update should be available both through Apple's Software Update as well as via this link.

Users experiencing problems with the automatic update might try the standalone updater. While the update should technically install without having to restart the computer, users should at least quit all running applications to install the update. Alternatively, we recommended that users download the update and then boot into "Safe" mode by holding the shift key down at startup. When booted into Safe Mode, first run Disk Utility and perform a permissions fix on the boot drive before applying the update.

Feedback? http://www.macfixit.com/contact.

A few users have reported problems with the built-in key shortcuts (command-C specifically), in which the keys appear to have lost functionality.

Apple Discussions poster Pchittt writes:

"My shortcut 'command + C' does not work any more (all my other shortcuts work, 2 touches work). I have already tried to put back my shortcuts by default, to make a repair of authorizations or to connect an external keyboard but nothing works!"

Users affected by this problem have tried fixing permissions on the drive, as well as ensuring the key combination is not reserved for another application in the "Keyboard and Mouse" system preferences. However, these efforts have not fixed the issue.

Despite some users' suspicions of this problem being caused by a defective keyboard, other combinations or the keys by themselves would not work if that were the case. Instead, this problem seems to be caused by a software configuration in the text-to-speech or voiceover features in OS X, which are part of the universal access aspects of the OS. It could be due to some conflict or bug in the programming, or could be due to users inadvertently setting the speakable items hotkey to the one in question.

Fixes

Turn off VoiceOver One user with this problem was able to fix it by activating and deactivating the "VoiceOver" option in the "Universal Access" system preferences. This might toggle faulty settings to be reset, resulting in the problematic hotkey sequence freeing itself.

Check Text to Speech hotkey While toggling VoiceOver might work for some users, this problem is more likely due to the "Text to Speech" hotkey being inadvertently set to the problematic hotkey sequence. Mac OS X supports a user-defined command to speak any selected text, and unfortunately this command does not double-check whether or not the supplied command is used elsewhere. As such users can easily override commands defined elsewhere. To check this, go to the "Speech" system preferences and in the "Text to Speech" tab either uncheck the "Speak selected text when the key is pressed" option, or click the "Set Key..." button to reset this command to a different hotkey sequence.

Several users have reported an issue in which their function keys not working properly on their laptop computers. With relatively new computers, users have had various warning beeps or complete lack of function occur upon pressing any of the function keys.

Apple Discussions poster SPOB writes:

"I've had a MacBook for a couple months now and just recently i've been having a problem where when i try using any of the keys in the top row of the keyboard it just beeps and does nothing only the eject key works and the increase volume button opens dashboard."

This problem may have started after the latest Mac OS X update, or could be due to some faulty system setting that was inadvertently set. Additionally, in some applications, certain function keys are not supported, which will cause an error sound when users press them.

Things to Try

Toggle Keyboard layout While it is unlikely that a specific keyboard layout would change the function key mappings, users might try resetting the keyboard layout to "US" or other desired language. To do this, open the "International" system preferences and in the "Input Menu" tab uncheck all but the desired keyboard layout.

Toggle function key vs special features In the "Keyboard and Mouse" system preferences, uncheck the option to "Use all F1, F2, etc. keys as standard function keys." This option will prevent the volume or other "special" functions from working unless users also hold down the "Fn" key, and instead will give a system error sound if applications do not support the F-keys.

Reapply the latest OS update For users who have experienced this problem directly after an update, and for whom the previous fixes do not work, it is recommended to reapply the latest Mac OS X update by downloading the "Combo" update from Apple's website and applying it when booted in Safe Mode (hold shift during boot).

Reset PRAM It is possible some PRAM setting could cause input malfunction, so affected users might try to reset the computer's PRAM.

Apple has released an update for QuickTime 7.5, that "improves QuickTime compatibility with iChat." No further notes regarding enhancements brought about by the update are included.

We've recently reported on a rash of iChat issues affecting users of QuickTime 7.5.5 and Mac OS X 10.5.5. One issue in particular appears ripe for a fix with this update. Some users found that (after the QuickTime 7.5.5), shortly after starting a video chat, iChat will freeze and sometimes require a force-quit to get things back up and running.

Previously, MacFixIt recommended that users reapply the recent QuickTime updates as well as the Mac OS X 10.5.5 update, but according to more recent posts both here at MacFixIt, some users have found that this problem could be due to faulty QuickTime preference files. As such, in addition to the previous suggestions, it is recommended that users remove the file named com.apple.QuickTime.plist from their /username/Library/Preferences/ folder, and restart the computer.

This update may eliminate the need for the aforementioned fix or resolve other iChat/video related issues.

Feedback? http://www.macfixit.com/contact.

Apple has released a firmware update for the Late-2008 (unibody) MacBooks and MacBook Pros. The new update "addresses an issue where trackpad clicks may not be recognized."

We've reported extensively on the trackpad issues afflicting the new MacBooks, which include, as Apple describes, lack of click recognition and complete disfunction of the trackpad, wherein neither clicks nor movement register and the system must be restarted.

Like other firmware updates, this package will install an updater application into the Applications/Utilities folder and will launch it automatically. Users can then follow the onscreen steps to apply the update.

The firmware update requires Mac OS X 10.5.5 and is available through Software Update or via this Apple download page.

Feedback? http://www.macfixit.com/contact.

Several users have reported an issue in which Safari 3.2 crashes whenever a new tab is opened. A sampling of reports:

• "The new Safari release ( 3.2 ) is crashing every time a link opens a new tab. ( for example, in newsfire, I click on a new link, Safari tried to open the new window in a new tab, and poof! No more Safari. )"
• "Just installed Safari 3.2 on a PowerBook with OSX 10.4.11 and now Safari crashes every time I try to open a page in a new tab - either by command-clicking or using a right mouse click."
• "Just installed Safari 3.2, and now nothing loads. All my usual bookmarked websites, including MacFixIt, hang with a blank white page.'
• "I've just upgraded to Safari 3.2 from 3.1. Now I find that if I open more than one tab, the program crashes. I have gone back to 3.0.4 which I found on a previous backup."

The first workaround you should try when encountering this issue is to turn off the "Warn when visiting fraudulent websites" option in Preferences.

Next, you might need to get rid of Input Managers. Look in the following folders:

• /Library/Internet Plug-Ins
• ~/Library/Internet Plug-Ins
• /Library/InputManagers
• ~/Library/InputManagers

and remove any third-party items.

Possible culprits include PithHelmet, SafariStand and Concierge.

Input Managers reach right into an application and alter its code. This puts the behavior of the affected application outside the control and responsibility of its developers: a recipe for troubleshooting problems. That's not to say that issues absolutely will ensue as a result of Input Managers, but you, as a user, must do some cost/benefit analysis. If the functionality of a specific Input Manager or set thereof proves crucial, you may well choose to assume the associated risk.

Feedback? http://www.macfixit.com/contact.

The Finder has the option to view file previews and thumbnails, which can be seen both in the document itself as well as the "get info" window for documents. However, for some users, documents that should display a preview are instead showing a generic document icon.

Apple Discussions poster Vintuitive writes:

"I almost always have my folder view set as thumbnail view so that I can see the images without having to open them in Preview. I just realised that I can no longer do that for some reason. Instead of seeing a thumbnail I see large JPG icons. Even loading them into 'Coverflow' doesn't show them, just shows the icons instead."

While this problem might be most noticeable for pictures, it might also occur for other documents as well, including movie files and PDFs. This problem can be caused by several factors, including the changing of the default application used to view the files as well as some Finder settings for previewing the documents. Users affected by this might try the following to correct it.

Fixes

Ensure Finder "Show preview" options are checked If the problem seems to be with documents in a specific folder or on the Desktop, it may be that the view settings for that folder have been reverted. The default options for folders are to have document previews visible, but corruption in the ".DS_Store" file that contains these settings might prevent the previews from being enabled. For the affected folder, users should ensure it is in the foreground as the active window, and then from the Finder's "View" menu select "Show View Options". Then select the option to "Show icon preview" and close the options window.

Change the default application for the item(s) The Finder uses "Preview" to help render certain documents, including image files and PDFs. If users have switched the primary handling applications for these document types to a third-party program, it is possible that this switch could be interfering with the Finder's handling of the previews. Users can try reverting file types back to using "Preview" by getting information on one, and then changing the application associated with the file in the drop-down menu. Then optionally, clicking "Change All..." will ensure the changes are global instead of pertaining to the selected file only.

Users have periodically reported a problem with iChat where the program functions (menus, buttons, buddy lists, etc) will appear greyed out. The program launches but is otherwise nonfunctional.

Apple Discussions poster hanns writes:

"I got my first mac about a month ago and had not even opened iChat until today. When I click on any of the drop down menus almost all of the options are blanked out, and all of the buttons at the bottom of my bonjour list are also greyed out."

We previously reported on this problem, and at the time, fixes revolved around the iChat's localization settings. As such, and especially since the problem revolved around non-english languages, changing the default languages and limiting application-specific localization options was the primary fix for the issue.

Currently english users have been experiencing the problem, indicating there may be more than language packs contributing to the problem.

Fix: Boot into safe mode and repair permissions While users have tried repairing permissions on the drive as a possible fix, when the computer is booted into safe mode various maintenance scripts will run that may have helped users overcome this problem. To do this, hold the "shift" key down at bootup, and when logged in open Disk Utility and run the permissions fix routine on the boot drive. Restarting the computer after these steps has restored iChat for some affected users.

Yesterday, Apple released Safari 3.2, which addresses a number of bugs including those pertaining to image handling, the processing of XML files, and several security vulnerabilities. In addition the update adds support for anti-phishing technology to help protect users from malicious websites, which has been one of the major criticisms of previous versions of Safari.

NOTE: Before updating the software, which applies changes to some system files, users should ensure they have a full backup of their systems using either Time Machine or a disk cloning program such as SuperDuper or Carbon Copy Cloner.

Crashing caused by various add-ons While the update provides welcomed enhancements and bug fixes, users have reported broken third-party plugins such as "Concierge" bookmarks manager, "PithHelmet" ad-blocking software, and "AcidSearch" search enhancement software. It may be possible a reinstall of affected plugins could get them working again, but if not then users will have to wait for an update from the plugin developer to restore functionality.

Beyond plug-ins not working, users have experienced some problems with the update itself, most of which are random crashes of the application.

Apple Discussions poster PatrickL writes: "I made the big mistake of installing Safari 3.2 on Leopard. What a big friggin' mistake. I can barely use it for 30 seconds without it crashing."

In some cases these problems have been resolved by uninstalling Safari plugins, but for the most part, it seems that this problem has to do with a conflict in the new anti-phishing features, which are enabled by default. Users have found that the crashing seems to go away when these features are disabled.

To disable these features, go to Safari's preferences and in the "Security" section turn off the "Warn when visiting a fraudulent website" option. Alternatively, this problem might be due to a preferences file corruption with the new version of Safari not being able to apply the settings stored in the file. As such, users might try removing the "com.apple.Safari.plist" file from the /username/Library/Preferences/ folder and restart the program. Additionally, users might try removing cache files pertaining to Safari, which are located in the /username/Library/Caches/ folder, as well as removing the contents of the /username/Library/Safari/ folder.

Installation problems Lastly, users have had issues with the Safari update not installing: upon running the installer, users may get an error claiming "You cannot install Safari on this volume. This volume already has a newer version of Safari installed." This error may occur if users have had the Safari 4 preview installed at some point. When the preview is installed, several system files get updated with version information about the program, which will prevent Safari 3.2 from being installed even if users remove the application itself. The Safari 4 preview comes with an uninstaller that should correct this version information. However, if the uninstaller will not run because users have removed part of the Safar 4 installation (ie: the program itself), users should be able to reinstall Safari 4 and then run the uninstall program to properly remove it from the system. However, if this does not work users can manually change the system to accept the update by following these steps:

1. Go to the /System/Library/Frameworks/ folder and back up the "Webkit.framework" file to a safe location.
2. Right-click on the framework and choose "Show package contents"
3. Go to the /Versions/A/Resources/ folder and open the "Info.plist" file in a text editor.
4. Locate the keys labeled "CFBundleShortVersionString" and "CFBundleVersion" (do a search for these text strings)
5. Change the value of these keys to a value less than 5525.26 (the version string for the safari 3.2 program).
6. Save the file and close it, and try installing Safari version 3.2 again.

NOTE: While this will enable users to install Safari, there may still be some residual files from the Safari 4 installation that could be incompatible with the Safari 3.2 update. As such, while users can try this method, the cleaner option is to do an archive and install reinstallation of the operating system to clear out these files.

For users who are experiencing extensive problems with the update and wish to uninstall it, the best way to do this is to revert the system to a backup (Time Machine or otherwise) right before the update was applied.

Several users have reported an issue in which users experimentation with or inavertent modification of permissions on key system resources renders the system unable to boot.

Apple Discussions poster tharrisw writes:

"I was messing around with file permissions and did something very, very stupid. I set the access under 'everyone' of the System Folder to 'no access.' I got the spinning beach ball and no response from any input, so after several minutes I rebooted the machine...On reboot, the machine gets as far as the blue screen with the spinning icon at the bottom, and then it switches back and forth between two shades of blue for eternity."

This type of problem should be relatively easy to fix, and there are several approaches, depending on comfort levels with either the terminal and/or other methods of interacting with the filesystem. At the very worst, users will have to perform an archive and install of the system, but that should only be necessary in a couple of scenarios.

Users should generally be able to locate the improperly modified files. Follow this series of escalating steps:

Fix Permissions Most of the core system resources are listed in the permissions database and, as such, should be fixable by running a permissions fix on the hard drive. Users can do this by booting of the Leopard DVD and running "Disk Utility" from the "Utilities" menu.

Target Disk Mode If users have two Macs available, target disk mode will allow modification of permissions of the affected files through the Finder. To do this, boot the problematic computer into Target Disk mode by holding "T" at bootup. Next, attach it via FireWire to the second computer to mount the hard drive on the second computer. Open it and navigate to the files that were changed, and revert their permissions.

Terminal Users should be able to boot off the Leopard DVD, then open the Terminal application from the "Utilities" menu after choosing their desired language. Using the terminal, users should be able to navigate to and revert the changed files. In the example quoted by the user above, the user needed to change the permissions of the system folder itself to being readable by everyone using the "chmod" command as follows:

• chmod a+rwx /System/

However, the specifics of