PSE9 on iMac shows pinwheel of death for 10 to 15 seconds when mousing!

Help! My PSE9 on my iMac (10.8.3) has become nearly completely unresponsive. When I mouse over any menu or tool, I get a 10 to 15 second pinwheel of death. I can't select tools from the toolbar. I think this all started when I attempted to update the Inspiration Browser (that ended in failure). I have tried removing the program and reinstalling, but that hasn't helped. I'm relatively new to the Mac world, so I'm not sure whether I removed the program properly.
I trusted that this Adobe software would be a good program for my photo editing needs, but now it's useless. How can I resolve this issue?
I don't know if it makes a difference, but I bought Photoshop Elements & Premier Elements as a boxed set.
Any suggestions?

I would try repairing and optimizing your catalog while you're in there (if you use the organizer), but that won't affect the editor's performance.
To repair permissions, go to applications>utilites>disk utility and click your computer in the list on the left side of the window, then click Repair Permissions. This can take quite a while, so don't fret, and don't get upset about all the messages you'll see passing by in the window while it's working (SUID has been changed and will not be repaired, for example). Those don't matter. The only thing that matters is if you see Repair Failed in red at the end of the process.

Similar Messages

I have a wireless router for my house, and my I-phone can find the network and sign in but it won't show up in airport for my i -mac even when right beside the router. What can I do?

I have a wireless router for my house, and my I-phone can find the network and sign in but it won't show up in airport for my i -mac even when right beside the router. What can I do?

Do you have any videos/movies in the video app?
In iTunes if you right click on the video and select Get Info and go to the Option tap what Media Type is shown?

Firefox freezes for at least 5 seconds when opening context menus

Well I've been looking for a reason to switch to Chrome... I guess now i have one.
Problem: Firefox freezes for 5 seconds when opening context menus (screen goes gray for @3s)
Firefox 32
Ubuntu 12.04
I first noticed it this morning when I tried to open up a Bookmark menu. Continued testing and found that right-clicking(anywhere) caused the same behavior. There are tons of posts going back years of similar behavior (although I doubt they're all related), so I ran therough the standard troubleshooting steps (restarting firefox after each step):
* cleared the caches
* Lowered cache memory allocation
* Created a new profile (did not carry-over any previous bookmarks or add-ons)
* Restarted firefox in safe-mode.
* Reset firefox (from safe-mode command)
Restarting firefox with all add-ons disabled is not included here because that is assumed in 'created a new profile' (correct?).
Furthermore, when I went to reinstall I got the error: "E: I wasn't able to locate a file for the firefox package. This might mean you need to manually fix this package."
I don't know what happened over the weekend, but I guess I'll try a full manual reinstall, when I have more time to mess with it. FF has been a primary tool for development, but for now it's dead to me.
P.S. On an unrelated issue. Maybe I'm old-school, but I miss the original drop-down menus up top. I don't think there's anything wrong with improving on the existing model, but why would you replace something that's worked well for DECADES.

Thanks for your response and sorry for the delay in my rep[ly.
Today I tested the Linux-64 version (Firefox 33) from the link you suggested. There weren't any install instructions or a README, but based on the file-system layout I guess it just needs to be extracted. I downloaded and extracted to my Downloads directory and ran the executable via command-line as my user (not root).
Firefox popped up right away, but it was not usable for at least 30s. It asked to import from Chrome which I did (no errors). Every click on the top bar (address bar search, buttons to the right of search, bookmarks toolbar) resulted in a dimming un-dimming sequence of @7s, after which nothing (couldn't focus in the address bar, occasionally the bookmark menu would appear, but was not functional). Basically, it's un-usable.
As I mentioned in an earlier reply, I am having similar problems with Komodo which is apparently also Mozilla based.
Are there any logs I could tail and post that might help track this down?
Not sure what to do at this point.

Safari 5.1 and Lion pinwheel of death

After the install of Lion my Safari 5.1 is running very slow. It either crashes or I get the pinwheel of death for around a minute or so. You can't reinstall Safari 5.1 because the download site is set up for Snow Leopard. Any sugestions? I've cleared my cache. I'm on a 2007 iMac intel duo core.

I've been having the SPOD as well, since the upgrade to Lion. It only seems to be in Safari. It will spin for around 30 seconds, then work fine. There doesn't seem to be any rhyme or reason to when it happens, it happens on low graphics pages as well as those with embeded animations etc...

Pinwheel of death

Hi, My macbook has been pretty speedy and has little issues except getting a little hot. Lately I have started using imovie. I have made a few small movies and it is a good editing tool. Well today whenever I try to use Imovie every few seconds when I go to click on something or change where I want to play the clip from, the pinwheel comes up for 3 or 4 seconds. I have gone into activity monitor and I barely have anything running or using up my cpu so I don't see the problem. Please help it really effects the speed I can do things.

Care to share which OS and iMovie versions you are using?

Can I use my new iMac 20" as a monitor for for Power Mac G5?

Actually I want to buy the new iMac 20" computer with the intel and then randomly use the iMac as a monitor display for my Power Mac G5 when I am editing video and then unhook it and use the Imac as a stand alone when I'm not editing video with my Power Mac. Will this work please. Thank You

Hello,
It's not possible to use either the iMac (Flat Panel) (G4) or the new Intel iMacs as displays. The only options would be:
VNC set-up. It's fairly low speed of refresh would probably make this undesirable for your situation: Screen Recycler (link)
A video-in device. A device like Elgato's EyeTV Hybrid (link) would not be of sufficiently high resolution to be any use for video editing.
regards
mrtotes

I just replaced the hard drive for my Mac Pro, and I am trying to restore what is on my Time Capsule, but it wont connect, and only is giving me the pinwheel of death. What do i do?

I just replaced the hard drive for my Mac Pro, and I am trying to restore what is on my Time Capsule, but it wont connect, and only is giving me the pinwheel of death. What do i do?

You will need to boot from some alternate boot device to accomplish this, if you did not initialize the drive before installing it.
If you have another Mac, you may be able to use FireWire target disk mode.
If your MacBook has a DVD reader and you have a Mac OS X Installer/Utilities DVD, such as the one that shipped with it, you can boot from that DVD, answer only the "what Language" question, and wait a quarter minute for the MenuBar to be drawn. Then examine the Utilities menu or the Installer menu and Find Disk Utility.

When I go to Preview to view a photo it shows up for less than a second then disappears and just leaves a gray box where the photo should be. iMac (Retina 5K, 27-inch, Late 2014). I need Preview for work.

After the OS X Yosemite 10.10.3 update When I go to use Preview to view a photo it shows up for less than a second then disappears and just leaves a gray box where the photo should be. iMac (Retina 5K, 27-inch, Late 2014). I need Preview for work.

1. This procedure is a diagnostic test. It changes nothing, for better or worse, and therefore will not, in itself, solve the problem. But with the aid of the test results, the solution may take a few minutes, instead of hours or days.
The test works on OS X 10.7 ("Lion") and later. I don't recommend running it on older versions of OS X. It will do no harm, but it won't do much good either.
Don't be put off by the complexity of these instructions. The process is much less complicated than the description. You do harder tasks with the computer all the time.
2. If you don't already have a current backup, back up all data before doing anything else. The backup is necessary on general principle, not because of anything in the test procedure. Backup is always a must, and when you're having any kind of trouble with the computer, you may be at higher than usual risk of losing data, whether you follow these instructions or not.
There are ways to back up a computer that isn't fully functional. Ask if you need guidance.
3. Below are instructions to run a UNIX shell script, a type of program. As I wrote above, it changes nothing. It doesn't send or receive any data on the network. All it does is to generate a human-readable report on the state of the computer. That report goes nowhere unless you choose to share it. If you prefer, you can act on it yourself without disclosing the contents to me or anyone else.
You should be wondering whether you can believe me, and whether it's safe to run a program at the behest of a stranger. In general, no, it's not safe and I don't encourage it.
In this case, however, there are a couple of ways for you to decide whether the program is safe without having to trust me. First, you can read it. Unlike an application that you download and click to run, it's transparent, so anyone with the necessary skill can verify what it does.
You may not be able to understand the script yourself. But variations of it have been posted on this website thousands of times over a period of years. The site is hosted by Apple, which does not allow it to be used to distribute harmful software. Any one of the millions of registered users could have read the script and raised the alarm if it was harmful. Then I would not be here now and you would not be reading this message. See, for example, this discussion.
Nevertheless, if you can't satisfy yourself that these instructions are safe, don't follow them. Ask for other options.
4. Here's a general summary of what you need to do, if you choose to proceed:
☞ Copy a particular line of text to the Clipboard.
☞ Paste into the window of another application.
☞ Wait for the test to run. It usually takes a few minutes.
☞ Paste the results, which will have been copied automatically, back into a reply on this page.
These are not specific instructions; just an overview. The details are in parts 7 and 8 of this comment. The sequence is: copy, paste, wait, paste again. You don't need to copy a second time.
5. Try to test under conditions that reproduce the problem, as far as possible. For example, if the computer is sometimes, but not always, slow, run the test during a slowdown.
You may have started up in "safe" mode. If the system is now in safe mode and works well enough in normal mode to run the test, restart as usual. If you can only test in safe mode, do that.
6. If you have more than one user, and the one affected by the problem is not an administrator, then please run the test twice: once while logged in as the affected user, and once as an administrator. The results may be different. The user that is created automatically on a new computer when you start it for the first time is an administrator. If you can't log in as an administrator, test as the affected user. Most personal Macs have only one user, and in that case this section doesn’t apply. Don't log in as root.
7. Load this linked web page (on the website "Pastebin.") The title of the page is "Diagnostic Test." Below the title is a text box headed by three small icons. The one on the right represents a clipboard. Click that icon to select the text, then copy it to the Clipboard on your computer by pressing the key combination command-C.
If the text doesn't highlight when you click the icon, select it by triple-clicking anywhere inside the box. Don't select the whole page, just the text in the box.
8. 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 and start typing the name.
Click anywhere in the Terminal window to activate it. Paste from the Clipboard into the window by pressing command-V, then press return. The text you pasted should vanish immediately.
9. If you see an error message in the Terminal window such as "Syntax error" or "Event not found," enter
exec bash
and press return. Then paste the script again.
10. If you're logged in as an administrator, you'll be prompted for your login password. Nothing will be displayed when you type it. You will not see the usual dots in place of typed characters. Make sure caps lock is off. Type carefully and then press return. You may get a one-time warning to be careful. If you make three failed attempts to enter the password, the test will run anyway, but it will produce less information. If you don't know the password, or if you prefer not to enter it, just press return three times at the password prompt. Again, the script will still run.
If you're not logged in as an administrator, you won't be prompted for a password. The test will still run. It just won't do anything that requires administrator privileges.
11. The test may take a few minutes to run, depending on how many files you have and the speed of the computer. A computer that's abnormally slow may take longer to run the test. While it's running, a series of lines will appear in the Terminal window like this:
[Process started]
        Part 1 of 8 done at … sec
        Part 8 of 8 done at … sec
        The test results are on the Clipboard.
        Please close this window.
[Process completed]
The intervals between parts won't be exactly equal, but they give a rough indication of progress. The total number of parts may be different from what's shown here.
Wait for the final message "Process completed" to appear. If you don't see it within about ten minutes, the test probably won't complete in a reasonable time. In that case, press the key combination control-C or command-period to stop it and go to the next step. You'll have incomplete results, but still something.
12. When the test is complete, or if you stopped it because it was taking too long, quit Terminal. The results will have been copied to the Clipboard automatically. They are not shown in the Terminal window. Please don't copy anything from there. All you have to do is start a reply to this comment and then paste by pressing command-V again.
At the top of the results, there will be a line that begins with the words "Start time." If you don't see that, but instead see a mass of gibberish, you didn't wait for the "Process completed" message to appear in the Terminal window. Please wait for it and try again.
If any private information, such as your name or email address, appears in the results, anonymize it before posting. Usually that won't be necessary.
13. When you post the results, you might see an error message on the web page: "You have included content in your post that is not permitted," or "You are not authorized to post." That's a bug in the forum software. Please post the test results on Pastebin, then post a link here to the page you created.
14. This is a public forum, and others may give you advice based on the results of the test. They speak for themselves, not for me. The test itself is harmless, but whatever else you're told to do may not be. For others who choose to run it, I don't recommend that you post the test results on this website unless I asked you to.
Copyright © 2014, 2015 by Linc Davis. As the sole author of this work (including the referenced "Diagnostic Test"), I reserve all rights to it except as provided in the Use Agreement for the Apple Support Communities website ("ASC"). Readers of ASC may copy it for their own personal use. Neither the whole nor any part may be redistributed.

The pinwheel is spinning for longer and longer periods of time. Have to manually shut off iMac sometimes to get it to restart.

The pinwheel is spinning for longer and longer periods of time. Why and what do I need to do about that?

You have 10.6 on that machine, I suggest you stick with it for performance, third party hardware and software reasons as long as possible.
Consider 10.8 (not 10.7) when it's released, because 10.7 and 10.8 will require a new investment in software and newer third party hardware as it requires newer drivers the old machines won't have. (forced upgrade because of software, really nice of them)
http://roaringapps.com/apps:table
Far as your Safari problem do these things until it's resolved:
1: Software Update fully under the Apple menu.
2: Check the status of your plug-ins and update (works for all browsers) also install Firefox and see if your problems continue. You should always have at least two browsers on the machine just in case one fails.
https://www.mozilla.org/en-US/plugincheck/
Flash install instructions/problem resolution here if you need it.
How to install Flash, fix problems
3: Install Safari again from Apple's web site
https://www.apple.com/safari/
4: Run through this list of fixes, stopping with #16 and report back before doing #17
Step by Step to fix your Mac

Nvidia drivers crashing in Adobe Bridge, spinning pinwheel of death

Twice so far in Adobe Bridge my system will randomly lock up with the spinning pinwheel of death. The console shows these lines at the time of the freeze:
8/12/12 9:47:44.000 PM kernel[0]: NVDA(OpenGL): Channel timeout!
8/12/12 9:47:45.000 PM kernel[0]: NVDA(OpenGL): Channel exception! exception type = 0x20 = PBDMA Error
8/12/12 9:48:05.000 PM kernel[0]: NVDA(OpenGL): Channel timeout!
8/12/12 9:48:05.000 PM kernel[0]: IOVendorGLContext::ReportGPURestart
8/12/12 9:48:05.000 PM kernel[0]: 0000006e
8/12/12 9:48:05.000 PM kernel[0]: 00000001 0000902d 00000000 00000000
8/12/12 9:48:05.000 PM kernel[0]: 00000000 00000100 00000000 00000009
8/12/12 9:48:05.000 PM kernel[0]: 00000000 00000000 00000000
8/12/12 9:48:05.000 PM kernel[0]: 00000000 00000000
8/12/12 9:48:05.000 PM kernel[0]: 0000006e
8/12/12 9:48:05.000 PM kernel[0]: 00000001 0000902d 00000000 00000000
8/12/12 9:48:05.000 PM kernel[0]: 00000000 00000100 00000000 00000009
8/12/12 9:48:05.000 PM kernel[0]: 00000000 00000000 03000821
8/12/12 9:48:05.000 PM kernel[0]: 00000000 00000000
8/12/12 9:48:05.000 PM kernel[0]: 0000006e
8/12/12 9:48:05.000 PM kernel[0]: 00000001 0000902d 00000000 00000000
8/12/12 9:48:05.000 PM kernel[0]: 00000000 00000100 00000000 00000009
8/12/12 9:48:05.000 PM kernel[0]: 00000000 00000000 00000000
8/12/12 9:48:05.000 PM kernel[0]: 00000000 00000000
8/12/12 9:48:05.000 PM kernel[0]: NVDA(OpenGL): Channel exception! exception type = 0x20 = PBDMA Error
This obviously points to the Nvidia drivers crashing, but why? I'm currently using an Nvidia GTX 460 768MB in my Mac Pro, and I've never had this problem with any other applications. It seems to only be Bridge.

And you are assuming that the 460 will be supported of course which is not a given. The 570 and 670 seems to be okay and some use GTX 4xx but they also realized it can be iffy for support.

Safari crashed and the mac keeps getting the pinwheel of death, especially when streaming. whats going on???

I was streaming a baseball game and safari crashed on me, i have a macbook air osx7.1. it said it sent a message to apple about the situation. been having problems with then pinwheel of death! especially when I'm streaming the pinwheel will pop up for no reason. does anyone have any idea what the problem could be??

Launch the Console 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 Console in the icon grid.
Step 1
For this step, the title of the Console window should be All Messages. If it isn't, select
          SYSTEM LOG QUERIES ▹ All Messages
from the log list on the left. If you don't see that list, select
          View ▹ Show Log List
from the menu bar at the top of the screen.
In the top right corner of the Console window, there's a search box labeled Filter. Initially the words "String Matching" are shown in that box. Enter the name of the crashed application or process. For example, if iTunes crashed, you would enter "iTunes" (without the quotes.)
Each message in the log begins with the date and time when it was entered. Select the messages from the time of the last crash, if any. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.
☞ The log contains a vast amount of information, almost all of which is irrelevant to solving any particular problem. When posting a log extract, be selective. A few dozen lines are almost always more than enough.
Please don't indiscriminately dump thousands of lines from the log into this discussion.
Please don't post screenshots of log messages—post the text.
☞ Some private information, such as your name, may appear in the log. Anonymize before posting.
Step 2
In the Console window, select
          DIAGNOSTIC AND USAGE INFORMATION ▹ User Diagnostic Reports
(not Diagnostic and Usage Messages) from the log list on the left. There is a disclosure triangle to the left of the list item. If the triangle is pointing to the right, click it so that it points down. You'll see a list of crash reports. The name of each report starts with the name of the process, and ends with ".crash". Select the most recent report related to the process in question. The contents of the report will appear on the right. Use copy and paste to post the entire contents—the text, not a screenshot.
I know the report is long, maybe several hundred lines. Please post all of it anyway.
If you don't see any reports listed, but you know there was a crash, you may have chosen Diagnostic and Usage Messages from the log list. Choose DIAGNOSTIC AND USAGE INFORMATION instead.
In the interest of privacy, I suggest that, before posting, you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if it’s present (it may not be.)
Please don’t post other kinds of diagnostic report—they're very long and rarely helpful.

Mail and never ending spinning pinwheel of death! Help!

I'm running 10.5.6 on my 24'' aluminum/glass iMac, and when I open mail, I instantly get a spinning pinwheel of death that doesn't go away. I then have to force quit Mail, and if I open it again, the same thing happens.
This definitely *****, how would I go about re-installing mail? Is that the solution?

You don't need to reinstall mail, however, I do thing you need to reset it.
This is how you do it:
Quit mail (force quit it if necessary)
Delete the following files:
~\library\Preferences\com.apple.mail.plist
~\library\Preferences\com.apple.mail.RSS.plist
Move the folder Mail from ~\Library to your Desktop
Launch mail. It will ask you to configure a new account, if it doesn't click on the Mail menu\Preferences\Accounts\(+) to add a new account and follow the on screen instructions to add an account. if you don't know how to add an account follow this tutorial:
http://grumpynet.ath.cx/tutorials/configuremailforleopard/configuremail.php
If you need help finding the settings for your ISP check out this link or call your ISP:
http://grumpynet.ath.cx/Articles/Mailservers/mailservers1.php
After doing this you should have your mail working normally again.
NOTE: if you have folders created in your computer you can recover them by copying the Mail folder you moved to the desktop earlier into ~\Library and replace what's there. The folder ~\Library\Mail contains all your email messages and attachments, you can browse it and take a look at its structure if you want, is actually pretty cool and can help you understand how you can recover messages in the future or from another computer
NOTE 2: the term ~\ means your Home Folder (the folder with the icon of a house and your user name under Places in Finder)
I hope this help you fix your problem. Please post back to let us know if this fixed your problem or if you need more help

I can't adjust any settings in iPhoto preferences because it always freezes and i get the spinning pinwheel of death! HELP!!!

i can't adjust any settings in iPhoto preferences because it always freezes and i get the spinning pinwheel of death! HELP!!!

Try the following:
1 - delete the iPhoto preference file, com.apple.iPhoto.plist, that resides in your
User/Home/Library/ Preferences folder.
2 - delete the contents the following folder: User/Library/Containers/com.apple.iPhoto
3 - reboot, launch iPhoto and try again.
NOTE: For Mavericks and Yosemite, go to your Home folder and use the View ➙ Show View Options menu to bring the this window:
where you can check the Show Library Folder checkbox.

Directory Utility Won't Launch, Pinwheel of Death...

So, just today, two Leopard Macs (10.5.7) on my network lost connection to our Active Directory. A switch was rebooted, and the Macs lost DNS for only a couple minutes. When I went to reboot them to get the authentication back, as I've done many times in the past, neither of them could see the directory server. None of the AD accounts could log in. So I went to log in as a local admin, and went to launch Directory Utility to unbind and rebind, and I just get the pinwheel of death. This is happening on a G5 tower and an Intel iMac. Both were 10.5.7, and I was hoping an OS update might fix it, so I upgraded them to 10.5.8 and that didn't help.
Just out of curiosity, I tried to run DU on another Mac Laptop that has never been part of any directory, and it is doing the same thing. The G5 is a pretty fresh OS install with no third party software installed other than VLC. So I'm not really sure what's going on.
I tried using dsconfigad from the command line to Unbind the machines from the directory, and it just hangs after it asks for the network password... I'm confused, and unable to log into my macs...

Post to the Server Products forums where those mavens hang out.

How can I get Messages to show the correct time for read receipts?

Messages in Mountain Lion shows the wrong time for read receipts. For example, my iPad will show a message was read at 3:37 pm but if I open Messages on my MacBook, the read receipt shows the time that I opened the Messages app as opposed to the time the message was actually read. This is not too much of an issue if my iPad is handy, but really, shouldn't Messages on my MacBook be able to show the correct time the message was read? It syncs all the other infromation with Messages on iOs.
I should mention that if Messages is running on my MacBook when the recipient reads the message, then it does show the correct time the message was read. It's if Messages was not running and I re-launch it that the read receipt time gets mixed up.

HI,
As far as I am aware Messages marks or time stamps an iMessage at the time of receipt rather then the time you got around to reading it.
I will admit that in most cases reading and receiving as the app opens will be near enough the same time in some conversations.
Adding Time Stamps to Chat is what iChat has always done particularly with AIM based Chats.
The "Sync" in Messages is "display on all devices" and after that each iMessages is dealth with separately on each device.
There is no syncing of deleting/dimssing an iMessages or having read it on another device.
8:58 PM Tuesday; April 16, 2013
 iMac 2.5Ghz 5i 2011 (Mountain Lion 10.8.3)
 G4/1GhzDual MDD (Leopard 10.5.8)
 MacBookPro 2Gb (Snow Leopard 10.6.8)
 Mac OS X (10.6.8),
 Couple of iPhones and an iPad
"Limit the Logs to the Bits above Binary Images."  No, Seriously
Message was edited by: Ralph Johns (UK)

PSE9 on iMac shows pinwheel of death for 10 to 15 seconds when mousing!

Similar Messages

Maybe you are looking for