3 Replies Latest reply: Aug 17, 2010 1:10 AM by Jason Harder
Jason Harder Level 1 Level 1
I am currently sitting on a MBP that has lost its wireless connection and system date after a power failure. Since especially the latter shouldn't happen, I got suspicious.

Now, when trying to set the system time manually, everything seems to work fine – but it doesn't. Dropping down the menu clock shows, the system thinks its sunday, not monday.

I have tried all the usual stuff; PRAM, SMC, single user boot, ... way up to deleting systemui prefs. Nope, doesn't work.

When I create a new user, there seems to be no problem. System time is correct and the dropdown shows the same time.

So it must have something to do with the first user. Any hints?

I currently wait for updates to install ...


MBP 17" SSD, Mac OS X (10.6.2)
  • Jason Harder Level 1 Level 1
    System is now on 10.6.4 including all other updates. Problem persists: Menu clock shows correct day (monday), when dropping down it says "Sunday".

    When I open SystemPrefs, it says that the last check for updates ran on sunday.

    This is freaky ...

  • Jason Harder Level 1 Level 1
    ... the time zone file (/etc/localtime) doesn't exist, something went wrong ...

    Whenever I try to change the timezone setting I get errors like this on console:

    09.08.10 19:58:26 [0x0-0x14014].com.apple.systempreferences[150] System Preferences(150,0x11b1fb000) malloc: reference count underflow for 0x2005c77e0, break on autorefcount_underflowerror to debug.

    And after that:

    09.08.10 19:58:27 [0x0-0x14014].com.apple.systempreferences[150] 2010-08-09 19:58:27.245 writeconfig[153:903] ** warning, the time zone file (/etc/localtime) doesn't exist, something went wrong

    I haven't removed timezone information from the system. What is going wrong here? Can I reinstall that info without needing to dump the entire system?

  • Jason Harder Level 1 Level 1
    Problem solved by deleting this file: