• On BNET: Job suck? Here's the key to happiness
advertisement
April 23, 2007 9:00 AM PDT

Security Update 2007-004 (#3): Problems logging in, QuickTime components may be to blame

by CNET staff

Problems logging in (cont.) We continue to report on an issue where after installation of Security Update 2007-004, users experience 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.

More fixes

Delete QuickTime components It appears that certain third-party QuickTime components may be interfering with login on systems that have received Security Update 2007-2004. If you have installed EyeTV or another application that places DivX QuickTime components on your system, you may want to try removing the files via one of the following routines:

1. 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), then navigate to the /Library/QuickTime on the problematic volume, and drag the following files to the trash:

  • DivX 6 Decoder.component
  • DivX Decoder.component
  • DivX Encoder.component
  • EyeTV MPEG Support.component
  • 3ivx D4 4.5.1 for OSX

2. If you are forced into single-user mode (a text-based interface) after applying Security Update 2007-004, and don't have access to a separate startup volume, you can use the following commands at the single-user prompt to delete these files:

  • rm -rf "/Library/QuickTime/DivX 6 Decoder.component"
  • rm -rf "/Library/QuickTime/DivX Decoder.component"
  • rm -rf "/Library/QuickTime/DivX Encoder.component"
  • rm -rf "/Library/QuickTime/EyeTV MPEG Support.component"
  • rm -rf "/Library/QuickTime/3ivx D4 4.5.1 for OSX"

Try restarting and check for normal login after removing these files.

You may also want to temporarily other third-party QuickTime components you find in the /Library/QuickTime/ directory.

Re-install update from a separate volume Some users have been able to resolve an inability to boot by re-applying Security Update 2007-004 for an alternate startup drive, via these steps:

  1. Download and save the appropriate copy of Security Update 2007-004 from Apple's download page but do not run the installer
  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. Run the Security Update 2007-004 installer, selecting the original, problematic startup volume as the destination.
  5. Re-attempt booting from the problematic volume (hold down the option key at startup to select the desired drive)

One MacFixIt reader who had success with this workaround writes:

"After installing the Security Update 2007-004 (#2) all I got was the Darwin login and password interface. Running disk utility or the latest DiskWarrior did not help. My solution (after some 3 days of trouble shooting, since I did not want to reinstall a clean system!) was to run and reinstall the updater as a downloaded file from another computer (G4 in this case) while my 'problematic' Powermac G5 quad was booted with Command-T and connected with firewire."

Feedback? Late-breakers@macfixit.com.

Previous coverage:

Resources

  • Apple's download page
  • Late-breakers@macfixit.com
  • Security Update 2007-004 (...
  • Security Update 2007-004 r...
  • More from Late-Breakers
  • Recent posts from MacFixIt
    iTunes 10 user interface sees some minor changes
    Apple seeds iOS 4.1 Gold Master to developers
    Possible fix for Harman Kardon iSub problems with PowerPC Macs
    Precautions to take before installing iTunes 10
    A reminder on how to reset your Mac's system password
    Mail messages appearing blank
    Adobe Lightroom update brings direct Facebook publishing; Camera Raw 6.2 released
    Weekly troubleshooting utilities update
    Add a Comment (Log in or register) (4 Comments)
    • prev
    • next
    by Rosyna--2008 April 23, 2007 9:45 AM PDT
    <tt>rm -rf /Library/QuickTime/DivX 6 Decoder.component</tt>

    That's a very dangerous command to use... especially when the spaces aren't escaped and quotes aren't used.
    Reply to this comment
    by kucharsk April 23, 2007 12:29 PM PDT
    Elgato now has a <A HREF="http://faq.elgato.com/index.php/faq/more/517/">note on their support page</A> stating:

    <i>The current download of EyeTV 2.4 should have an adjusted MPEG component that can avoid this problem. Thus, affected users are encouraged to re-download and re-install EyeTV 2.4. Feel free to use the 3ivX or DivX plugins after installing the latest build of EyeTV.</i>
    Reply to this comment
    by Ilgaz April 23, 2007 12:29 PM PDT
    <class="merchant"><span>&#62;</span><div class="datestamp"><i>This is a reply to a previous comment by kucharsk</i></div></class><br />
    I suspected the EyeTV right away because both EyeTV 2.4 and security update shipped around same time (check versiontracker)

    I am glad we don't have to give up a great,free codec as 3ivx. Thanks to El Gato too.
    Reply to this comment
    by DavidM April 23, 2007 8:55 PM PDT
    I had the same problem on my Intel Mac with 10.4.8. Once a month or so, the login window would not accept any credentials.

    This is a family mac, shared with my wife and son, so we often leave it at the login window for convenience.

    On those occasions, I have been able to ssh into the machine and kill the loginwindow process and login again. The downside is that it forcibly kills every logged in user's session. But it is better than a power cycle, I suppose.

    Oddly, I have not seen it yet with this security update. But then, I've only had it for a week and the problem is only occasional.
    Reply to this comment
    (4 Comments)
    • prev
    • next