jdkjoller

Q: desktop folders slow to open

Hello All-

I recently upgraded my iMac to Mavericks. Everything is working fine except the time it takes to open a folder on my desktop and the time it takes to open my harddrive from the desktop. When I click on the HD icon or a folder it takes around 15-20 seconds for it to display the contents. Once inside the foler or hard drive, the subsequent files and folders open quickly. So it seems to be something associated with my desktop.

 

I've"

- repaired permissions

- reset teh PRAM

- Checked the Activity Monitor. Shows nothing eating up CPU

- Went to delete the com.apple.finder.plist But could not find it! Followed this path: HD>Library>Preferences. Also did a search and this file is not found.

Is this casuing the problem?

 

Thoughts? Also running 16GB RAM.

 

Thanks.

iMac, OS X Mavericks (10.9.1), 3.2 GHz Intel Core i3

Posted on Jan 13, 2014 2:38 PM

Close

Q: desktop folders slow to open

  • All replies
  • Helpful answers

Page 1 of 3 last Next
  • by jdkjoller,

    jdkjoller jdkjoller Jan 14, 2014 11:21 AM in response to jdkjoller
    Level 1 (0 points)
    Jan 14, 2014 11:21 AM in response to jdkjoller

    Anyone out there have an idea?

  • by Linc Davis,

    Linc Davis Linc Davis Jan 14, 2014 2:28 PM in response to jdkjoller
    Level 10 (208,037 points)
    Applications
    Jan 14, 2014 2:28 PM in response to jdkjoller

    Please read this whole message before doing anything.

     

    This procedure is a test, not a solution. Don’t be disappointed when you find that nothing has changed after you complete it.

     

    Step 1

     

    The purpose of this step is to determine whether the problem is localized to your user account.

     

    Enable guest logins* and log in as Guest. Don't use the Safari-only “Guest User” login created by “Find My Mac.”

     

    While logged in as Guest, you won’t have access to any of your personal files or settings. Applications will behave as if you were running them for the first time. Don’t be alarmed by this; it’s normal. If you need any passwords or other personal data in order to complete the test, memorize, print, or write them down before you begin.

     

    Test while logged in as Guest. Same problem?

     

    After testing, log out of the guest account and, in your own account, disable it if you wish. Any files you created in the guest account will be deleted automatically when you log out of it.

     

    *Note: If you’ve activated “Find My Mac” or FileVault, then you can’t enable the Guest account. The “Guest User” login created by “Find My Mac” is not the same. Create a new account in which to test, and delete it, including its home folder, after testing.

     

    Step 2

     

    The purpose of this step is to determine whether the problem is caused by third-party system modifications that load automatically at startup or login, by a peripheral device, by a font conflict, or by corruption of the file system or of certain system caches.

     

    Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards, if applicable. Start up in safe mode and log in to the account with the problem. You must hold down the shift key twice: once when you boot, and again when you log in.

       

    Note: If FileVault is enabled, or if a firmware password is set, or if the boot volume is a software RAID, you can’t do this. Ask for further instructions.

     

    Safe mode is much slower to boot and run than normal, with limited graphics performance, and some things won’t work at all, including sound output and Wi-Fi on certain models. The next normal boot may also be somewhat slow.

     

    The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.

     

    Test while in safe mode. Same problem?

     

    After testing, reboot as usual (not in safe mode) and verify that you still have the problem. Post the results of steps 1 and 2.

  • by dianeoforegon,

    dianeoforegon dianeoforegon Jan 14, 2014 3:19 PM in response to jdkjoller
    Level 5 (5,758 points)
    Mac OS X
    Jan 14, 2014 3:19 PM in response to jdkjoller

    Try changing to Google Public DNS (8.8.8.8 and 8.8.4.4).  I realize that makes

    no sense to you, but others have found this to work. 

     

    Open System Preferences > Network

    Click on Advanced tab > DNS

     

    You should see your DNS servers listed. Make a note of what is entered.

    Click on the + and add 8.8.8.8 and 8.8.4.4. It shouldn't delete but if it does after you add the Google servers, you can add the original back at the bottom.

     

    This fix was posted here on another discussion post but I failed to save the link.

     

    Download and run Name Bench. It hunts down the fastest DNS servers available for your computer to use.

     

     

    http://code.google.com/p/namebench/

  • by jdkjoller,

    jdkjoller jdkjoller Jan 14, 2014 3:23 PM in response to Linc Davis
    Level 1 (0 points)
    Jan 14, 2014 3:23 PM in response to Linc Davis

    Thanks for your reply!

    Here are the results:

     

    Step 1: Logged out and logged back in to a guest user account (I'm set up as the admin fo rmy imac). Did not have any problems! Everything opened correctly with no delays. Shut down and proceeded to step 2.

     

    Step 2: Started up in Safe Mode with all peripherals disconnected. Do not have any aftermarket expansion cards. Filevault was not enabled, no firmware password and boot volume is not a software RAID.

    Problem was still there. Any folder (as well as "Macintosh HD") I tried to open from desktop took a minimum of 15 seconds to open. Any folder within a folder opens immediately.

     

    Stpe 3: reconnected all peripherals, restarted. problem still occuring.

  • by Linc Davis,

    Linc Davis Linc Davis Jan 14, 2014 3:30 PM in response to jdkjoller
    Level 10 (208,037 points)
    Applications
    Jan 14, 2014 3:30 PM in response to jdkjoller

    Problems such as yours are sometimes caused by files that should belong to you but are locked or have wrong permissions. This procedure will check for such files. It makes no changes and therefore will not, in itself, solve your problem.

    First, empty the Trash, if possible.

    Triple-click anywhere in the line below on this page to select it, then copy the selected text to the Clipboard by pressing the key combination command-C:

    find ~ $TMPDIR.. \( -flags +sappnd,schg,uappnd,uchg -o ! -user $UID -o ! -perm -600 \) 2>&- | wc -l | pbcopy

    Launch the built-in 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). The command may take a noticeable amount of time to run. Wait for a new line ending in a dollar sign ($) to appear.

    The output of the command will be a number. It's automatically copied to the Clipboard. Please paste it into a reply.

  • by jdkjoller,

    jdkjoller jdkjoller Jan 14, 2014 3:33 PM in response to dianeoforegon
    Level 1 (0 points)
    Jan 14, 2014 3:33 PM in response to dianeoforegon

    FYI changing DNS per dianeoforegone's post did not do anything.

  • by jdkjoller,

    jdkjoller jdkjoller Jan 14, 2014 3:40 PM in response to jdkjoller
    Level 1 (0 points)
    Jan 14, 2014 3:40 PM in response to jdkjoller

    How long is a "noticeable amount of time to run"?

    Going on almost 7 minutes now.

  • by Linc Davis,

    Linc Davis Linc Davis Jan 14, 2014 3:44 PM in response to jdkjoller
    Level 10 (208,037 points)
    Applications
    Jan 14, 2014 3:44 PM in response to jdkjoller

    You may not have started the command. Press the return key.

  • by jdkjoller,

    jdkjoller jdkjoller Jan 14, 2014 3:47 PM in response to Linc Davis
    Level 1 (0 points)
    Jan 14, 2014 3:47 PM in response to Linc Davis

    No, I did. I went ahead and tried to close it and it said "closing this window will terminate the running processes: wc, find, pbcopy".

  • by jdkjoller,

    jdkjoller jdkjoller Jan 14, 2014 3:48 PM in response to jdkjoller
    Level 1 (0 points)
    Jan 14, 2014 3:48 PM in response to jdkjoller

    It just popped up but not with a number. Instead it states my computer and user name (like it does when you first launch terminal).

  • by Linc Davis,

    Linc Davis Linc Davis Jan 14, 2014 4:16 PM in response to jdkjoller
    Level 10 (208,037 points)
    Applications
    Jan 14, 2014 4:16 PM in response to jdkjoller

    The output is on the Clipboard, not in the Terminal window. Paste it into a reply.

  • by jdkjoller,

    jdkjoller jdkjoller Jan 15, 2014 7:02 AM in response to Linc Davis
    Level 1 (0 points)
    Jan 15, 2014 7:02 AM in response to Linc Davis
    200
  • by Linc Davis,

    Linc Davis Linc Davis Jan 15, 2014 7:16 AM in response to jdkjoller
    Level 10 (208,037 points)
    Applications
    Jan 15, 2014 7:16 AM in response to jdkjoller

    Some of your user files (not system files) have incorrect permissions or are locked. This procedure will unlock all your user files, reset their ownership, and remove their access-control lists. If you've set special values for those attributes, 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.

      

    Back up all data.

       

    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.

        

    Enter the following command in the Terminal window in the same way as before (triple-click, copy, and paste):

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

       

    This time 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 may take several minutes to run, depending on how many files you have. Wait for a new line ending in a dollar sign (“$”) to appear, then quit Terminal.

        

    Step 2 (optional)

        

    Take this step only if you have trouble with Step 1 or if it doesn't solve the problem.

       

    Boot into Recovery. When the OS X Utilities screen appears, select

       

    Utilities Terminal

      

    from the menu bar. A Terminal window will open. In that 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 startup 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.

  • by jdkjoller,

    jdkjoller jdkjoller Jan 15, 2014 4:21 PM in response to Linc Davis
    Level 1 (0 points)
    Jan 15, 2014 4:21 PM in response to Linc Davis

    Linc Davis-

    I did step 1 (above) but the terminal has been running for over an hour now. I went to quit and it states "Closing this window will terminate the running process: sudo". I have about 500 GB on this computer. Should I go ahead and quit or does it usually take this long?

Page 1 of 3 last Next