3 Replies Latest reply: May 11, 2013 8:51 AM by Wascally Wabbit
jaruzek Level 1 Level 1 (0 points)

Today, I woke my Mac from sleep and went to open my Mailplane app to check my email. The app, which I've had installed for years, suddenly told me that my license has expired. Although my account were still stored, the windows size and toolbars also reset.

 

Whenever I open iTunes now, it asks me to agree to the license agreement, and show me the tour. All my display preferences have reset as well, ugh. I noticed my Finder's toolbar buttons reverted to default. Same thing is happening some other apps. This happened a couple of times before, so I repaired permissions, etc., using Onyx, but the problem keeps re-occurring.

 

Presently, I am OS X10.8.3, iTunes 11.0.2 and Mailplane 2.5.10.

 

Anyone know what's up with this?

  • Eric Root Level 7 Level 7 (31,200 points)

    Try setting up another admin user account to see if the same problem continues. If Back-to-My Mac is selected in System Preferences, the Guest account will not work. The intent is to see if it is specific to one account or a system wide problem. This account can be deleted later.

     

    Isolating an issue by using another user account

     

    If the problem is still there, try booting into the Safe Mode.  Shut down the computer and then power it back up. Immediately after hearing the startup chime, hold down the shift key and continue to hold it until the gray Apple icon and a progress bar appear. The boot up is significantly slower than normal. This will reset some caches, forces a directory check, and disables all startup and login items, among other things. If the system operates normally, there may be 3rd party applications which are causing a problem. Try deleting/disabling the third party applications after a restart. For each disable/delete, you will need to restart if you don't do them all at once.

                   

    Safe Mode

     

    Safe Mode - About

     

    General information.

     

    Isolating issues in Mac OS X

     

    Troubleshooting Permission Issues

     

     

    Step by Step to Fix Your Mac

  • Linc Davis Level 10 Level 10 (155,650 points)

    Back up all data. Don't continue unless you're sure you can restore from a backup, even if you're unable to log in.

    This procedure will unlock all your user files (not system files) and reset their ownership and access-control lists to the default. If you've set special values for those attributes on any of your files, they will be reverted. In that case, either stop here, or be prepared to recreate the settings if necessary. Do so only after verifying that those settings didn't cause the problem. If none of this is meaningful to you, you don't need to worry about it.

     

    Step 1

    If you have more than one user account, and the one in question is not an administrator account, then temporarily promote it to administrator status in the Users & Groups preference pane. To do that, unlock the preference pane using the credentials of an administrator, check the box marked Allow user to administer this computer, then reboot. You can demote the problem account back to standard status when this step has been completed.

    Triple-click the following line to select it. Copy the selected text to the Clipboard (command-C):

    { sudo chflags -R nouchg,nouappnd ~ $TMPDIR.. ; sudo chown -R $UID:staff ~ $_ ; sudo chmod -R u+rwX ~ $_ ; chmod -R -N ~ $_ ; } 2> /dev/null

    Launch the Terminal application in any of the following ways:

    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)

    ☞ In the Finder, select Go Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.

    ☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.

    Paste into the Terminal window (command-V). You'll be prompted for your login password, which won't be displayed when you type it. You may get a one-time warning to be careful. If you don’t have a login password, you’ll need to set one before you can run the command. If you see a message that your username "is not in the sudoers file," then you're not logged in as an administrator.

     

    The command will take a noticeable amount of time to run. Wait for a new line ending in a dollar sign (“$”) to appear, then quit Terminal.

    Step 2 (optional)

     

    Step 1 should give you usable permissions in your home folder. This step will restore special attributes set by OS X on some user folders to protect them from unintended deletion or renaming. You can skip this step if you don't consider that protection to be necessary, and if everything is working as expected after step 1.

    Boot into Recovery by holding down the key combination command-R at startup. Release the keys when you see a gray screen with a spinning dial.

    When the OS X Utilities screen appears, select

    Utilities Terminal

    from the menu bar. A Terminal window will open.

    In the Terminal window, type this:

    res

     

    Press the tab key. The partial command you typed will automatically be completed to this:

    resetpassword

     

    Press return. A Reset Password window will open. You’re not  going to reset a password.

    Select your boot volume ("Macintosh HD," unless you gave it a different name) if not already selected.

    Select your username from the menu labeled Select the user account if not already selected.

    Under Reset Home Directory Permissions and ACLs, click the Reset button.

    Select

    Restart

    from the menu bar.

  • Wascally Wabbit Level 1 Level 1 (0 points)

    This worked for me. 

     

    A caution for people like me who are unaccustomed to using Terminal: Linc is correct that when you type in your password, it won't show. In fact, nothing shows - I thought Terminal was just not responding. There was no acknowledgement that anything had even been typed. I had interpreted Linc's words as meaning that the password characters would not show - not that NOTHING would show.  I'm not blaming Linc - he was literally correct, and it was my interpretation of his words that caused my confusion.  But I suspect others will make the same wrong assumption I did, so pay attention.

     

    There was also no sign that terminal was churning away on the command.  It sat there unchanging and mute until it finally spat out the line with the "$" at the end.  When I returned to the system the problem appeared to be fixed. Apps that displayed the first-use intro screen upon every start up now stopped doing so.  I'm hoping this will eliminate several other problems related to password and permissions that DIDN'T show up when doing a check of permissions using the keychain app.

     

    Thanks, Linc.