Security Update 2007-004 (#2): Problems logging in; login items broken; fixes

Problems logging in One of the most widely reported problems occurring for some users after installation of Security Update 2007-004 is an inability login to certain, or all user accounts.

The problem may be typified by a "looping" situation where the user enters a login name and password then presses return, only to be presented with the same login window over and over.

The problem may also manifest as a display of the single user mode login prompt ("Welcome to Darwin") with the error message username:/dev/console: Operation not supported by device.

Potential fixes

Try booting in safe mode Restart your Mac and hold down the Shift key while the system is booting. If the system boots properly, check the /Library/StartupItems and /System/Library/StartupItems directories for potentially problematic files, then use try some of the workarounds listed below in the "Common fixes" section. Also, try deleting the appropriate .plist files as listed below in "Delete .plist files." After attempting repeairs, restart your Mac and check for normal login behaviour.

Run fsck If you are presented with the single user mode screen aforementioned, try running the fsck command by typing the following, then pressing return:

• /sbin/fsck -fy

If the message ***** FILE SYSTEM WAS MODIFIED ***** appears, keep typing the above command and pressing return until the message ** The volume (name of volume) appears to be OK

Delete .plist files If you have an alternate means of booting the Mac in question -- e.g. a separate startup drive, or another Mac connected via FireWire target disk mode -- you can try deleting the following files from the problematic Mac's primary startup drive [the tilde (~) represents the home user directory]:

• ~/Library/Preferences/com.apple.loginwindow.plist
• ~/Library/Preferences/loginwindow.plist

We've received an increasing number of reports from readers who, for unexplained reasons, are suddenly unable to log in to previously working accounts. When attempting to enter their login and password information, users are told that the password is incorrect (when it is verified as correct), or that login simply failed.

In many cases, even creating a new user account with new login/password information then attempting to gain entry is problematic.

While we are still tracking down reliable solutions for this issue, we have identified a few workarounds that prove successful for some readers.

Change password If you can login with one administrator account but not other accounts, the first thing to try is a password change as follows:

1. Launch the Terminal (located in /Applications/Utilities)
2. Type the command sudo username passwd
3. Enter the administrator password when prompted, and subsequently the desired username password.
4. Re-enter the new username password to verify.

Feedback? Late-breakers@macfixit.com.

Reader reports

Matthew Norcross adds:

"After installing Security Update 2007-004, one of my computers (Quad G5/OS X 10.4.9) is stuck in a log in loop. It starts up and goes to GUI log in screen. I enter password, screen goes light blue and then goes to console mode log in screen. I enter name/password and am taken back to GUI log in screen. The loop goes on and on and on."

Biger Munthe writes:

"I got a 'Welcome to Darwin' black screen, after downloading and then manually installing the new updates: When it comes to the LogInScreen: Then a name and then a password - well and the next is??  I can write 'exit', but then it happens  all-over again."

MacFixIt reader Peter Burgess writes:

"I was working as one user while the update was being installed. Now the second user cannot login. It seems to want a password even though none has been set up. Really bad because now they can't get at their work."

Jean-Marie writes:

"The installation failed, the administrator password window vanishing before I was able to type in anything. Upon restart the Mac refuses to start, showing briefly the login window but this one vanishes and is replaced by the console giving the message: 'operation not supported by device'"

Finally, MacFixIt reader Lee writes:

"After I installed the Security Update for my PPC, the login screen displays for a few seconds and then goes to the Darwin Command prompt to login. I enter my user id and password and stay in Unix mode."

If you are experiencing similar issues, please let us know.

Login items broken Meanwhile, a number os users are reporting an issue where login items are disabled after the update.

MacFixIt reader Lawrence Hargett writes:

"After installing this update none of my login items launch (although they are still present in Preferences / Users) and my mouse speed setting reverted to a very slow speed. I can launch my login items (such as iCal) without event and I can reset the mouse setting, but if I restart I'm back to square one."

Feedback? Late-breakers@macfixit.com.

Possibly the worst thing that can happen after applying Security Update is an inability to startup your Mac. The first step in this case is to attempt startup in safe mode (hold the "shift" key while your Mac is booting), then follow the procedures outline in our tutorial "Startup fails (particularly after a system or security update); solving"

Delete kernel extension caches, other caches for some issues A number of common issues that crop up after incremental Mac OS X updates can be resolved by deleting specific cache files -- specifically kernel extension caches -- and restarting.

This can most easily be accomplished with a shareware utility like Tiger Cache Cleaner, but also bears a manual process which involves dragging the following files to the trash:

• com.apple.kernelcaches (a folder in /System/Library/Caches)
• Extensions.kextcache (a file in /System/Library)
• Extensions.mkext (a file in /System/Library/)
• com.apple.ATS (a folder in /Library/Caches/)
• Files that start with com.apple.LaunchServices (in /Library/Caches)

You will be prompted to enter your administrator password when dragging these files to the trash. You may need to restart after moving them to the trash.

Re-apply the Mac OS X 10.4.9 combo updater A workaround that has proved successful for various problems caused by Security updates Mac OS X updaters is re-application of the current combination updater:

• Mac OS X 10.4.9 Update Intel, Combo [310 MB]
• Mac OS X 10.4.9 Update PowerPC, Combo [163MB]
• Mac OS X Server Update 10.4.9 Intel, Combo [350 MB]
• Mac OS X Server Update 10.4.9 PowerPC, Combo [216MB]

Doing so overwrites potentially problem-causing files that were not replaced by the "Delta" (adjacent version-to-version) update.

Re-apply the Mac OS X 10.4.9 combo updater from an alternate startup volume

1. Download and save the appropriate Mac OS X 10.4.9 combo updater (links above)).
2. Startup from an alternate boot volume, such as an external FireWire drive, or use another Mac to boot the problematic system in FireWire target disk mode (connect the two machines via a FireWire cable, and boot the target [problematic] system while holding down the "T" key)
3. Once booted from an alternate drive, select the problematic volume in the Finder, and "Get Info" -- either by pressing the Command-I keyboard combination or accessing the "Get Info" option in the File menu. Check the box marked "Ignore ownership permissions on this volume."
4. If you have a third-party disk repair utility like DiskWarrior, use it to re-build the directory on the problematic volume (this step may not be necessary)
5. Re-install the Mac OS X 10.4.9 combo updater on the problematic drive.
6. Re-attempt booting from the problematic volume (hold down the option key at startup to select the desired drive)

Getting the update off your Mac If you are unable to properly startup or experiencing other dire issues after applying Security Update 2007-004 that cannot be resolved by already posted workarounds, you may need to uninstall the update.

This can be accomplished via the following process, adapted from our tutorial on reverting to a previous iteration of Mac OS X. Note, however, that reverting your system will remove any refinements brought by the update and leave your system open to potential vulnerabilities.

First, make a backup of your current Mac OS X installation with the Security Update applied, problematic as it may be. If there is an issue along the way, your valuable data will be safely intact in its current form.

Next, you'll need to perform an Archive and Install process to remove all of the Security Update's (and potentially problem-causing) components, and replace them with the components of a fresh copy provided by the Mac OS X disc that shipped with your system, or a retail Mac OS X disc. Unfortunately, this means you will lose some system settings and some or all third-party system add-ons.

To begin the process, insert your Mac OS X CD or DVD, as indicated above. Restart your machine and hold down the "C" key to boot from the newly inserted disc. Follow the on-screen instructions, and after accepting the license agreement, click "Options." Select "Archive and Install," and check the "Preserve User and Network Settings" option if you'd like to do so.

After the installation process is complete, you will be left with an earlier Mac OS X system that (hopefully) does not suffer from the problems generated by the Security Update. Use Software Update or Apple's download page to download the update that brings your system to a state directly prior to the Security Update

Previous coverage:

• Security Update 2007-004 released: Vulnerabilities in AFP, AirPort, Help Viewer, SMB, WebDAV and more plugged

Resources