Attempt to delete photo results in 'spinning beach ball'.

We try to delete some photos, and we get a 'spinning beach ball'. All we can do is force quit. The photo we want to delete never is placed in the iPhoto trash. We need to be able to delete photos to gain some hard drive space to produce more albums and videos.
Is this related to the post "Deleting photos doesn't move them to IPhoto Trash "?

Yes, space is very tight on that machine now.
Yes you can move your Library to another drive: Make sure the drive is formatted Mac OS Extended (Journaled)
1. Quit iPhoto
2. Copy the iPhoto Library from your Pictures Folder to the External Disk.
3. Hold down the option (or alt) key while launching iPhoto. From the resulting menu select 'Choose Library' and navigate to the new location. From that point on this will be the default location of your library.
4. Test the library and when you're sure all is well, trash the one on your internal HD to free up space.
Then to rebuild:
Option 1
Back Up and try rebuild the library: hold down the command and option (or alt) keys while launching iPhoto. Use the resulting dialogue to rebuild. Choose to Rebuild iPhoto Library Database from automatic backup.
If that fails:
Option 2
Download iPhoto Library Manager and use its rebuild function. This will create a new library based on data in the albumdata.xml file. Not everything will be brought over - no slideshows, books or calendars, for instance - but it should get all your albums and keywords, faces and places back.
Because this process creates an entirely new library and leaves your old one untouched, it is non-destructive, and if you're not happy with the results you can simply return to your old one.
Regards
TD

Similar Messages

Is Spotlight making those grinding noises and spinning beach balls?

Since newly installing Snow Leopard I am finding myself getting delays and if I persist in trying to do work it results in spinning beach balls. All the while I hear grinding noises.
I am guessing it is Spotlight trying to do its work. But I'd like to know for sure.
I am trying to use Activity Monitor but, as usual, am having little success as I have never figured out the best way to use it that gives me any useful info. For instance, I'd like to see what is most active (and likely causing the grinding and spinning). With %CPU selected everything moves so fast, and names of things are too arcane for me to understand. If spotlight is in there it's not clear to me.
For now, I am using the Spotlight privacy settings to stop it from touching any of my internal drives - so I can get some work done.
Is there a manual on-off control for Spotlight?

Allan. Grinding noises aside, did you write anything else in your reply? I see two horizontal lines with nothing on them.
*Installing SL was an indirect result of my having to trash two internal drives and install two new ones; reinstall an OS; then rebuilt my working computer and making Time Machine back ups. Along the way I opted to purchase and upgrade one to SL. I don't think the noises I described as grinding are bad drive. Somaybe they're not exactly "grinding." Perhaps "ticking."

Solution to iPhoto spinning beach ball for Book projects with too many unplaced photos

A few days ago I discovered the solution to this problem for a client using iPhoto 9.5.1 in OS X Mavericks 10.9.4.
=====
TRIED ALL KNOWN SUGGESTIONS BUT NONE HELPED
My client had already tried repairing, rebuilding etc. the iPhoto Library, and I tried OS X's Disk Verify and Repair Permissions plus emptied the cache folder in system Library and in the hidden user Library folder (option-key "Go" menu, Library). None of this helped.
CLUE TO PROBLEM
I noticed several of her iPhoto Book projects each had thousands of "unplaced" photos. In each of those cases, each Book project only had 10-50 "placed" photos used to order the book but thousands of "unplaced" photos. In a Book project, clicking on the bottom-right corner's "Photo" icon-button caused an extremely long lasting spinning beach ball making iPhoto unusable for long periods.
I discovered the problem by clicking once on an existing Book project's name in the left column of iPhoto, then letting go of the mouse with its arrow cursor hovering over the selected Book project name. Within 1-7 seconds, a little pop-up appears listing the total number of photos (placed + unplaced) in that Book project. For many Book projects, the total number was just several more photos than the number of "placed" photos, e.g., a Book with 25 photos showed "(37)" in the pop-up info by the hovering stationary mouse, meaning 37 total photos (placed + unplaced) are associated with that Book project.
BUT...
...some projects listed over 5,000 (five thousand) photos associated with a single Book project that had only placed 20-40 photos in the final printed book. One Book project had 6,070 and several other small book projects showed over 1,000 photos. In each Book project with a mass of unplaced photos, clicking the bottom-right "Photo" icon-button caused a very long-lasting spinning beach ball, almost certainly because iPhoto struggled to build a huge list of thumbnails for the mass of unplaced photos.
My client didn't understand how to efficiently add photos to a new Book project and was clicking on the pull-down menu in the right column that appears after clicking the Photo icon-button within the Book project. From the menu she chose "Last import..." or other menu choice that added a mass of "unplaced" photos to the Book project.
She didn't realize that after creating a new Book project, she could simply drag an individual photo or multi-selected group of photos or an event or "faces" group from its respective library section and drop it onto the Book project's name in the left column, thereby adding only a small group of "unplaced" photos.
USER SOLUTIONS
=====Delete mass of "unplaced photos" within a Book project
This works best for cleaning up smaller number of unplaced photos from completed Book projects.
Problems with solution:
- if the number of unplaced photos is huge, e.g., 6,070, the list of unplaced photos won't appear for a long, long time if ever.
- even if the list of unplaced photos finally appears, there's no way to select more than one thumbnail at a time, i.e., command-a for Select All doesn't work, nor do shift-clicks and command-clicks for multi-item selecting. You must click one photo then tap the "delete" key on your keyboard repeatedly and fast for this to be practical (note: delete key presses are cached here (meaning accumulated until it catches up processing them later); tapping the delete key like mad then waiting for iPhoto to catch up takes lots of patience.
====Delete an entire existing Book project containing a mass association of unplaced photos
This is practical if you've already printed your Book project and no longer need it. My client chose this method for Book projects with a mega mass of unplaced photos.
Problem with solution:
- for incomplete Book projects in progress with a mass of unplaced photos, you'd have to start over after deleting the whole thing.
NEED FOR IMPROVED IPHOTO FEATURE(S)
(1) The existing "Clear Placed Photos" button within a Book project might be useful, but it'd be even better to also have a button to "Clear Unplaced Photos,” and this button should be available outside of the section that struggles to display thumbnails of large numbers of unplaced photos. Clicking "Clear Unplaced Photos" would do the trick.
(2) An additional iPhoto behavior might help: iPhoto should warn with an option to cancel when adding a mass of photos to the "unplaced photo" section if the number of photos exceeds ??? (400??).
(3) Add another choice to iPhoto’s special startup Administrative window (Repair, Rebuild, etc.): "Remove unplaced photos from existing projects. (Doesn't destroy any photos in Library)"
Whew!

Like I mentioned in the post, corruption was probably ruled out by running all the Admin features at iPhoto startup (e.g., Rebuild, etc.). I also stated in my post that I also ran a Disk Verify and Repaired Permissions in OSX (via Disk Utility). I also emptied system Library cache files as I stated in my post.
I was paid to figure out the solution and am not getting paid to troubleshoot for Apple. The more unplaced photos there are in a Book project, the longer it takes to build thumbnails. It's an old general problem in computing when building lists on the fly.
The delay happened for all Book projects with lots of unplaced photos (almost*** certainly more than Apple imagined a user would use), and the beach ball delay was proportional to the number unplaced photos, which super large numbers of photos.
I very much doubt photos are corrupt. But Apple will probably figure it out. It was EASILY reproducible. Try it with different number of unplaced photos known not be corrupt (they display fine elsewhere and iPhoto's and Disk Utlity's admin Verify, Repair etc features show no problems).
I'm done with this.
My client's iPhoto works well now and she knows how avoid placing exorbitant numbers of unplaced photos into her project. I'm not getting paid to answer all this, so good night.
=======
***"Science is the outcome of being prepared to live without certainty and therefore a mark of maturity. It embraces doubt and loose ends."
— A. C. Grayling

Why do I get the spinning beach ball when I try to change from Events to Photos. How do I fix it?

Why do I get the spinning beach ball when I try to change from Events to Photos. How do I fix it?

Option 1
Back Up and try rebuild the library: hold down the command and option (or alt) keys while launching iPhoto. Use the resulting dialogue to rebuild. Choose to Repair Database. If that doesn't help, then try again, this time using Rebuild Database.
If that fails:
Option 2
Download iPhoto Library Manager and use its rebuild function. (In early versions of Library Manager it's the File -> Rebuild command. In later versions it's under the Library menu.)
This will create an entirely new library. It will then copy (or try to) your photos and all the associated metadata and versions to this new Library, and arrange it as close as it can to what you had in the damaged Library. It does this based on information it finds in the iPhoto sharing mechanism - but that means that things not shared won't be there, so no slideshows, books or calendars, for instance - but it should get all your events, albums and keywords, faces and places back.
Because this process creates an entirely new library and leaves your old one untouched, it is non-destructive, and if you're not happy with the results you can simply return to your old one.
Regards
TD

Attempting to Delete Song Results in iTunes Crash

Whenever I try to delete a song from my iTunes Library (no matter what song it is) iTunes pauses for a second then immediately crashes. I have never experienced this before and it's beginning to become very frustrating. I have just recently upgraded to OSX Leopard (10.5) and I'm not sure if it has anything to do with my recent upgrade but, any possible help is very much appreciated. I have already searched though numerous threads of various topics of discussion and have not had any luck finding anything to help me. I am currently running iTunes version 7.4.2.
Thank you.

This is not a problem specific to iTunes. For some reason, even a clean install left no alert sound selected in the audio control panel on my dual G5. ANY action that called an alert sound, in ANY application, would freeze the app, give a spinning beach ball for a few seconds, and end in an unexpected quit of the application. Deleting a song in iTunes triggers an alert sound and BAM, iTunes quits.
More often, I was encountering application departures with accidental clicks outside of modal dialog boxes, failed Safari text searches, etc. I was so disgusted I created a new install of Tiger and was ready to hunker down there and wait for Apple to recognize this problem and solve it.
However, in my new Tiger install I found that my screen was flashing when I should have been hearing an alert. This continued whether or not that option was selected in Universal Access, and toggling it there made no difference. Clicking on the alert volume slider in the audio control panel also resulted in a flash rather than sound. I selected another sound in Tiger and the alert began functioning correctly and the flash was gone.
This lead to me correctly wonder if this was not related to my Leopard problems and to the the above discovery. I booted back into leopard and found that clicking on the alert volume slider there resulted in a beach ball and crash of the preferences panel. Selecting a new sound solved ALL of these problems.

HT1338 I cant upload photos to send as email i keep geeting the spinning beach ball that freezes

I cant upload photos to send as email i keep geeting the spinning beach ball that freezes the whole system can anybody tel me how to get ovet this problem please (explain for a dummy please)

Hi,
I have a Folder called "Pictures" (My Pictures seems a bit "Windowsy" to me)
I don't have a Media folder inside there.
It would help to know if this is actually within the iTunes Library
Having said that I tend to use Eric's Method.
Pic of My own Card in the Contacts list
It shows where I have used Faces (from iPhoto) and Defaults (Login pic choices for the Account pic).
My iChat/Messages pic is the same Signature pic as used here and is in the Recents Tab on show.
You can even use the Camera if one is attached (Mac Minis and Mac Pro require External Cameras).
Drag and Drop is my preferred method.
9:47 PM Saturday; December 22, 2012
Please, if posting Logs, do not post any Log info after the line "Binary Images for iChat"
 iMac 2.5Ghz 5i 2011 (Mountain Lion 10.8.2)
 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

Photo Booth Spinning Beach Balls

Within a few minutes of use using the background animations, Photo Booth gives a spinning beach ball and eventually closes.
Any suggestions on how to prevent this?
Thank you in advance,
Steve

Hi,
IF this is a Core 2 Duo Processor you could try setting Photo Booth to Open in 32 Bit Mode.
(Do a "Get Info" on the Photo Booth Application in the application folder).
2:37 PM Sunday; October 25, 2009
Please, if posting Logs, do not post any Log info after the line "Binary Images for iChat"

Transferring photos from camera or memory card causes iPhoto to hang up with the spinning beach ball - why

Transferring photos from camera or memory card causes iPhoto to hang up with the spinning beach ball - why? This happens only on a 5 year old iMac running 10.6.8. It is a recent developmemt. All other machines have no problen with the same card.

I click on the send feedback everytime it pops up with the force quit, so they'er getting it.
That sends a crash report. Its doubtful that these are ever seen by a human being, but more likely datamined. Sending feedback reaches an actual person.
My guess from yourdescription is that the portion of the OS (note, OS, not iPhoto) that manages the importing process is what's crashing.
Regards
TD

Spinning Beach Ball Delay with "Look for Shared Photos" Checked

We installed iLife '06 on our school computers - all 500 of them - this fall. It is version 6.0.4. However, upon launch, there is a long delay of about 2-4 minutes with a spinning beach ball that we've determined takes place because iphoto is looking for shared libraries. We have one shared library on the network at this time, but sometimes teachers turn on sharing, or have in the past.
Last year, we were using iPhoto '04 and had no problems like this at all -shared libraries appeared immediately, just as quickly as shared libraries in itunes still do.
Has anyone experienced this - is there a known issue? Or should I look for a network problem.

Solved this problem myself. It was a dns issue. For some reason, when iphoto looks for shared photo's, it does a reverse lookup on the ip of any machine it finds that has sharing turned on. If there is no reverse lookup zone on your dns server running OS X then it locks up as it repeatedly sends the request. Simply creating a reverse zone for the ip address range of your clients makes the bug go away. Why it needs to do a reverse lookup is beyond me.

Spinning Beach Ball on Start Up of iPhoto 09'

I have suddenly started having problems with iPhoto '09. I have about 4500 photos in my library. I have a late 2009 i7 iMac running mountain lion with 12 gb of RAM.
When I start iPhoto, it opens quickly enough, but as soon as I move my cursor I get a spinning beach ball for about 20-30 seconds. Then everything seems to work OK. I have deleted my cache and plist files and rebuilt the thumbnails, etc. to no avail. I also turned off sharing and unclicked look for shared photos. I have "check for new published photos" set to manually.
Does anyone have any idea what the issue is or how to fix it?
Many thanks.

I went into the Console and when I open iPhoto I get the following messages. Does this mean anything to you?
Many thanks.
5/25/13 12:26:37.927 PM iPhoto[407]: This process is attempting to exclude an item from Time Machine by path without administrator privileges. This is not supported.
5/25/13 12:26:37.927 PM iPhoto[407]: This process is attempting to exclude an item from Time Machine by path without administrator privileges. This is not supported.
5/25/13 12:26:37.928 PM iPhoto[407]: This process is attempting to exclude an item from Time Machine by path without administrator privileges. This is not supported.
5/25/13 12:26:37.928 PM iPhoto[407]: This process is attempting to exclude an item from Time Machine by path without administrator privileges. This is not supported.
5/25/13 12:26:38.161 PM iPhoto[407]: CFURLGetFSRef was passed this URL which has no scheme (the URL may not work with other CFURL routines): /Applications/iPhoto.app
5/25/13 12:26:38.179 PM iPhoto[407]: CFURLGetFSRef was passed this URL which has no scheme (the URL may not work with other CFURL routines): /Applications/iPhoto.app
5/25/13 12:26:38.181 PM iPhoto[407]: CFURLGetFSRef was passed this URL which has no scheme (the URL may not work with other CFURL routines): /Applications/iPhoto.app
5/25/13 12:26:38.184 PM iPhoto[407]: CFURLGetFSRef was passed this URL which has no scheme (the URL may not work with other CFURL routines): /Applications/iPhoto.app

Mavericks Screen Capture causes spinning beach ball

Trained by experience never to install a brand new operating system on top of a perfectly functioning one (unless I want to risk many wasting times and losing productivity), to test out the new Mac OS, I installed Mavericks on an external FireWire drive by upgrading a fresh install of Snow Leopard, updated to its maximum version. Nothing else was on the volume, for I had used Disk Utility to securely erase and content and overwrite the volume with zeros.
Immediately after the Mavericks, I looked at the System Profile, taking some screen captures of selected windows. While Mavericks successfully captured the screens, it failed to display them when I selected one and hit the space bar. Instead, mavericks presented a perpetually spinning beach ball that prevented me from doing anything else on the Mac. I was forced to shut down.
Upon restart back into Mavericks, I encountered the same problem. I had to force power off again.
After rebooting into Mountain Lion on my internal hard drive, I ran a complete series of hard drive maintenance utilities involving all the tools I have, including Disk Utility, Drive Genius, Disk Warrior, and Tech Tool Pro. All ran successfully and reported no problems. I then capped things by running iDefrag to eliminate file fragmentation and to optimize the volume. With several hours of labor invested in preparing the external hard disk, downloading Mavericks' installer, running the Mavericks installer, performing all the pertinent maintenance routines I could think of, and finally optimizing the volume, which has no other software on it besides the new Apple operating system, I restarted the Mavericks volume. I then took a fresh screen capture, selected it, pressed the space bar, and I still got that infernal spinning beach ball.
I let it run for at least half an hour as I returned to watching a football game, hoping things would finally get cleared up. They did not. The ball still spun. I could not even get to the Finder to peek into the Force Quit command under the Apple icon. So, as originally condemned, I was compelled to hold down the power button to regain control of my computer, which this new, appropriately named operating system had wrested from me.
Anyone having a similar problem? Anyone aware of a sure-fire solution, other than to avoid relying on this new operating system, which must be my policy until such glitches get fixed?
At least you know now why I consider it unwise to install a brand new OS atop of one that has served you well.

OK, it’s Wednesday now, late afternoon, following a long yesterday, spent exclusively on getting Mavericks installed, a day which continued well into night, approaching the sun rise, until I collapsed. No one can tell me that the Mavericks installation is without errors! Your mileage may differ, if you’re lucky. But if you had to go through what I just did, you’ll long for the days of System 7, when all you had to do was shove a half-dozen floppy disks into a floppy drive to get your Mac up and running without such angst.
SHORT ANSWER:
After many twists and turns that Apple should have foreseen and not inflicted upon customers, I finally managed to get Mavericks installed on my external Firewire hard drive.
I did follow your lead, Baltwo, that the nature of the problem might lay in corrupt preferences files on the primary Account, but, as I attempted a couple of days, I modified your suggestion that I cherry-pick which plist files might be good vs. which might be corrupt, by deleting the whole **** account. A couple of days ago, my intuition told me that doing that was the wiser way to proceed; today I felt compelled to do exactly that, because I had no other choice.
The reasons I had to do that is elaborated upon below.
LONGER EXPLANATION and DETAILS:
As I explained in the message I composed on Tuesday morning, I felt so insecure that I did not obtain a well-functioning operating system that I had decided to start the installation all over from scratch.
It took all day Monday to again use Disk Utility to securely erase the volume and prepare it for the new installation. When I tried to short-cut the process by doing a Quick Erase, the volume refused to accept the installation of Snow Leopard 10.6.3 from the DVD. On top of that, I again encountered difficulties in installing Snow Leopard from the DVD, because the installer just could not close the deal. The gauge runs up to the 99% mark, and it hangs there saying that it is “Moving items into place.” Sure, it is!
I’m a patient guy, so I let the installer do its thing for about four hours while I watched the World Series game. (Yeah, Red Sox!) But by the time the game was over, so was my patience. I had to Force Power Off the Mac and restart it.
Since I have no confidence in an operating system whose installer failed to do its job properly, I felt that I had to do more. Before I did that, though, I did a Google search to find out if my experience was unique. It is not! The forums are full of people who have complained about this very same hanging problem ever since the Snow Leopard DVD was released. Great, I thought. Now what do I do?
I decided to the Apple support site and download the 1.x GB combo updater to Snow Leopard 10.6.8 in the hopes that the upgrade process would cure whatever issues cropped up during the incomplete installation by the DVD. After downloading that combo disk image, installing 10.6.8, restarting the Mac under 10.6.8, and getting all the software updates applicable to that version, a few tests, supplemented by a running a whole barrage of maintenance utilizes to fix permissions, repair the disk, rebuilt the directory, seemed to indicate that I did finally achieve a solid installation of Snow Leopard 10.6.8 and all its trimming.
To save myself any future agony of having to go through this kind of winding road installation again, I used SuperDuper to create a disk image of the entire volume. That disk image is stored on another Firewire volume, ready to burned at some future date onto a BluRay disc for safe-keeping and backup.
With Snow Leopard safely installed on the volume and sporting one user Account, I was ready to use the Mavericks installer package that I had downloaded last Saturday, when I first began this process, to upgrade to Apple’s latest and greatest OS. Unfortunately, the installation process failed in the same way that the Snow Leopard installer failed. The installer just could not get over the hump of closing the deal. Once I got the installer started, I went to bed.
Four hours later, the installer still had not completed its job, again getting to the 99% mark, and just hanging there. Again, I had to Power Off the Mac. Upon restarting with the Option held down, I elected to start up using the built-in Recovery feature.
That seemed to work, but only sort of. I was able to get a Mavericks desktop, but the User account had absolutely no privileges to do a **** thing. It could not open its own Home folder to see what was in it. It could not complete the screen capture process, because I had no permission to save the picture anywhere, like on the Desktop.
In System Preferences, I tried to increase the size of the cursor, but that failed. In Finder preferences, I tried to make the hard drives show up on the desktop, but that failed, too. I ran permissions in Disk Utility; that did no good. Nothing worked! I could not even change anything related to my User account, because I had no permission to do so. Imagine that: my only account was an Administer account to which I had no access. I would not have thought such a thing could be possible.
I was caught in a loop, stranded on a Mobius Strip, walking on the wild side, surfing the waves of a brand new operating system corrupted by its own installation process.
Not a good thing at all.
Since the first installment had also resulted in a bizarre set of user accounts ending up with QuickLooks being declared the winner of a new account the system decided to create for me, I think it is reasonably safe to conclude that there is some kind of a bug, or flaw, in the Apple upgrade / installation procedure that needs some attention by Apple system engineers. None of this kind of stuff I have delineated at some length should be happening to anyone who owns a Mac.
And, Baltwo, even though I had kept uppermost in my mind your suggestion about creating a new account merely to ferret out which preference files might be corrupt and which might be OK, I decided that I did not want to take any chances at all with this extremely messed User account, which had worked fine in Snow Leopard, but had somehow got corrupted during the upgrade. So, as before, I decided to (1) create a brand new Administrator account; (2) log out from the useless User account in which I had no privileges whatsoever; (3) log in with the brand new Adminstrator; and (4) delete that useless User account entirely, completely, and forever.
At first, I was a little hesitant about deleting the first Administrator account that existed in my Users and Groups pane. I did not even know if such a thing could be done. So, I referred to my David Pogue reference books, and I did a Google search for “Delete Home User Mac” to see what others knew about this. Everyone described the standard way to delete an account; no one even mentioned any prohibition about deleting the original User account. So, I went ahead and deleted it, without encountering the slightest problem in doing so. I even followed up with before and after Terminal commands to see if that useless User account was truly gone, and it definitely went poof. Since I lacked permissions to create any documents at all within that former Home folder, getting rid of it was easy. I think that the System was just as glad to trash it as I was.
Hopefully, whatever corruption occurred during the Mavericks installation and upgrade process was restricted to the preference files associated with that messed-up, original Administrator account so that I can begin exploring Mavericks with a perfectly pristine operating system. Before I start tweaking it or adding stuff to it, my next step will be to use SuperDuper to create a disk image of the entire volume, so that, in the future, I will have a clean set of system of file to install on this external Firewire volume, or on any other internal hard drive I choose to install Mavericks later on. A Bluray disc will contain that disc image for safekeeping when it’s time to remove it from the destination volume where it gets created.
As to the tardiness of my reply, it is caused by the exorbitant amount of time—four days!—it took me to trek along this twisting, winding path of installing Mavericks, as well as a glitch in the mismatch of similarly looking User Names associated with similarly looking Apple ID accounts and similarly looking User Names associated with nearly identical Email Addresses that do not convert from one to the other, as, for example, mac.com does to me.com.
As I learned from Apple Staff who responded to my report that I was being locked out of the Apple Discussions community, there are four pieces of information that must match up for each Apple ID account, and my data had slipped out of sync. Now I know why, during Apple’s changeover in the formatting of the Apple Discussions section, I lost all those “points” I had accumulated in helping others, not that I track such things, and I could not find where my previous discussions were.
That’s also why I may be able to award anyone points for helping me in this thread, but I’m dialing in under the “other” Apple ID, not the one I used to create this topic. Close readers will observe the slight difference.
Thanks a lot, Baltwo. You get the credit for pointing me in the right direction.

Aperture will not open. Just an endless spinning beach ball. Will not force quick., Aperture will not open. Just an endless spinning beach ball. Will not force quit

Every attempt to open Aperture results in a spinning beach ball. When attempting to force quit, every program freezes. I am running a MacBook Pro, OS X 10.9.3, 8 GB Ram. Have deleted and reinstalled the program from the App store with the same results. Purchased Aperture a few months ago and began without difficulties. However, recently, the program simply stopped working. Suggestions?

Try a few of these:
-Hold option while opening. This will ask you to create a new library/choose a different one. Create the new library, see if it opens
->If it opens, it's a library issue. Swap the library back to the original one.
->Try running Library First Aid (cmd + opt while opening)
->Make a backup first, run each of these until it opens.
-If it does not open, test in Safe Mode (shift while booting)
->If it works there, it's user login items or startup items that can be removed from /Library/LaunchAgents, /Library/LaunchDaemons, /Library/StartupItems and ~/Library/LaunchAgents.
->Show no mercy in these folders, but don't trash everything just yet. Move it to a safe location on the desktop where you can easily put these files back. Reboot, test.
->Put some files back from harmless/well-known developers. Reboot, test.
->Rinse and repeat until Aperture doesn't open.
-Test in a new user account
->If it opens here, it's part of your user preferences
->Log back in to your main user
->Open ~/Library/Preferences, pull com.Aperture.xxxxxx.plist
->Logout, log back in, test.
If it keeps up, contact Apple or try verifying/repairing the disk through Disk Utility.

IPHOTO 11 causing spinning beach ball and freezing. help

I have a mid 2009 macbook with 2.3 dual core and 2 gb ram. i installed iPhoto 11 after a very successful 10.7.3 install. all was well then i began to import my photos from a thumb drive that i downloaded from a macbook pro onto a thumb drive. after few hiccups i realized i had a file that was stopping the import as it cam eup with the error message. so i deleted that and then about 3/4 of the way through the laptop just choked up and the spinning beach ball started and wouldnt stop. couldnt get it to force quit etc..
so after several days of attempts i gave up ended up having to do a safe reboot too many times and have now deleted iphoto and all its contents. my mac is working alebit is a bit sluggishly.
any help? is this due to just 2 gig of ram do i need more ram? i am at a loss and i really need to upload these photos but it just doesnt seems worth the hassle

That shoots that theory down. Try this: launch iPhoto with the Option key held down and create a new, test library. Import some photos and check to see if the same problem persists. If that library works without a problem your current library is suspect.
In that case if you have the space available on your hard drive and don't aready have a backup copy of the library make a temporary, backup copy (select the library and type Command+D) and apply the two fixes below in order as needed:
Fix #1
Launch iPhoto with the Command+Option keys held down and rebuild the library.
Select the options identified in the screenshot.
Fix #2
Using iPhoto Library Manager to Rebuild Your iPhoto Library
Download iPhoto Library Manager and launch.
Click on the Add Library button, navigate to your Home/Pictures folder and select your iPhoto Library folder.
Now that the library is listed in the left hand pane of iPLM, click on your library and go to the File ➙ Rebuild Library menu option
In the next window name the new library and select the location you want it to be placed.
Click on the Create button.
Note: This creates a new library based on the LIbraryData.xml file in the library and will recover Events, Albums, keywords, titles and comments but not books, calendars or slideshows. The original library will be left untouched for further attempts at fixing the problem or in case the rebuilt library is not satisfactory.

Spinning Beach Ball - Network Issue?

Hi Folks,
I know there have been posts on this over time but my particular question does not appear to have been answered. My apologies if I missed a response somewhere else in the forums. I'll try to keep it short.
Basically, a month or so ago I started getting the spinning beach ball in any application at various points of time. There was no rhyme or reason it seemed. It could happen when I have one application open, 5 applications open, it could happen in 5 five minutes or 2 hours later. Once the beachball started spinning, it wouldn't go away and it prevented me from using other apps as well, compelling me to do a manual shut down. I typically use only iPhoto, Safari, iDvd, Numbers and Mail. It could happen in any of them.
I've tried everything. Apple tech support had me do an archive and install - didn't work. I got Disk Warrior 4.2. Nope. I deleted plug-ins and did some other maintenance tasks etc., etc. but nothing worked.
Activity Monitor didn't seem to show anything alarming. Same with Console. Apple suggested I bring it into a tech at the local Apple Store. I did that and after 4 days of running their diagnostics, they could not replicate the 'hang' on the applications. That is, they found no problems with the Macbook - hardware or software.
Now I'm wondering (not being a computer savvy person I don't know if this is possible) if this is a wireless internet issue. Could my home network be a source of the application 'hang' (spinning beach ball) that I've experienced? It's the only thing I can think of that is different from my home computer set-up to the store. My router/modem is a SMC Gateway.
Any thoughts are really appreciated. Thanks so much for your brains on this!
Andyman

Ok folks,
I've got the one from yesterday and another one today below it. This was running while I was trying to burn a DVD in iDVD. Nothing else was running as far as I know and Airport was turned 'off':
10-09-19 7:08:45 PM com.apple.launchd[1] * launchd[1] has started up. *
10-09-19 7:09:16 PM com.apple.launchd.peruser.501[84] (com.apple.ReportCrash) Falling back to default Mach exception handler. Could not find: com.apple.ReportCrash.Self
10-09-19 7:09:26 PM com.apple.launchd.peruser.501[84]
(com.apple.Kerberos.renew.plist[102]) Exited with exit code: 1
10-09-19 7:09:50 PM com.apple.WindowServer[62] Sun Sep 19 19:09:50 andrew-maneras-macbook.local WindowServer[62] <Error>: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
10-09-19 7:33:47 PM com.apple.launchd.peruser.501[84] ([0x0-0x11011].org.m0k.handbrake[131]) Exited: Terminated
10-09-19 8:09:29 PM com.apple.backupd-auto[229] Not starting scheduled Time Machine backup - time machine destination not resolvable.
10-09-19 8:17:32 PM SystemUIServer[89] It does not make sense to draw an image when [NSGraphicsContext currentContext] is nil. This is a programming error. Break on _NSWarnForDrawingImageWithNoCurrentContext to debug. This will be logged only once. This may break in the future.
10-09-19 8:22:02 PM [0x0-0x2c02c].backupd-helper[236] Not starting Time Machine backup after wake - failed to resolve alias to backup volume
10-09-19 9:47:00 PM com.apple.launchd[1] * launchd[1] has started up. *
10-09-19 9:48:48 PM com.apple.launchd[1] * launchd[1] has started up. *
10-09-19 9:49:39 PM com.apple.launchd.peruser.501[82] (com.apple.ReportCrash) Falling back to default Mach exception handler. Could not find: com.apple.ReportCrash.Self
10-09-19 9:49:48 PM com.apple.launchd.peruser.501[82] (com.apple.Kerberos.renew.plist[105]) Exited with exit code: 1
Here's another one today that occurred during a print attempt:
10-09-20 12:01:17 PM com.apple.launchd.peruser.501[84] (com.apple.Kerberos.renew.plist[104]) Exited with exit code: 1
10-09-20 12:35:06 PM com.apple.launchd[1] * launchd[1] has started up. *
10-09-20 12:35:55 PM com.apple.launchd.peruser.501[84] (com.apple.ReportCrash) Falling back to default Mach exception handler. Could not find: com.apple.ReportCrash.Self
10-09-20 12:35:57 PM com.apple.launchd.peruser.501[84] (com.apple.Kerberos.renew.plist[103]) Exited with exit code: 1
10-09-20 5:14:12 PM [0x0-0x18018].backupd-helper[143] Not starting Time Machine backup after wake - failed to resolve alias to backup volume
10-09-20 5:17:02 PM [0x0-0x1c01c].com.apple.iWork.Keynote[165] objc[165]: Class SFXMeshAnimation is implemented in both /Applications/iWork '08/Keynote.app/Contents/Resources/Animations/Bolt.sfxplugin/Contents/MacOS/Bol t and /Applications/iWork '08/Keynote.app/Contents/Resources/Animations/Kiln.sfxplugin/Contents/MacOS/Kil n. One of the two will be used. Which one is undefined.
10-09-20 5:17:02 PM com.apple.WindowServer[63] Mon Sep 20 17:17:02 andrew-maneras-macbook.local WindowServer[63] <Error>: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
10-09-20 5:17:14 PM Keynote[165] * WARNING: Method setDrawsGrid: in class BGOutlineView is deprecated. It will be removed in a future release and should no longer be used.

Spinning Beach Ball

Recently my early 2011 MacBook Pro would start freezing up, usually with a Spinning Beach Ball. This can happen a few times an hour that requires rebooting. Sometimes the cursor would just freeze. Mr. Linc Davis, on June 2, 2013, suggested copying some information from the Console, that just preceeded the line with BOOT_TIME. I have done so below. Can anyone detect what my problem is from the Console information? Thanks
5/1/14 1:31:39.889 PM mds[40]: (Normal) Volume: volume:0x7fa78c914000 ********** Bootstrapped Creating a default store:0 SpotLoc:(null) SpotVerLoc:(null) occlude:0 /Volumes/firmwaresyncd.NYPs0d
5/1/14 1:34:24.825 PM WindowServer[94]: _CGXSetWindowBackgroundBlurRadius: Invalid window 0xffffffff
5/1/14 1:34:24.886 PM loginwindow[44]: find_shared_window: WID -1
5/1/14 1:34:24.886 PM loginwindow[44]: CGSGetWindowTags: Invalid window 0xffffffff
5/1/14 1:34:24.886 PM loginwindow[44]: find_shared_window: WID -1
5/1/14 1:34:24.887 PM loginwindow[44]: CGSSetWindowTags: Invalid window 0xffffffff
5/1/14 1:34:25.066 PM Chronicle[251]: Selected Index Loaded: 0
5/1/14 1:34:25.081 PM Chronicle[251]: All Bills Loaded
5/1/14 1:34:25.126 PM WindowServer[94]: device_generate_desktop_screenshot: authw 0x7fc710768a50(2000), shield 0x7fc71061d960(2001)
5/1/14 1:34:25.143 PM WindowServer[94]: device_generate_lock_screen_screenshot: authw 0x7fc710768a50(2000), shield 0x7fc71061d960(2001)
5/1/14 1:34:25.236 PM Chronicle[251]: EXPECTED BALANCE
5/1/14 1:34:26.323 PM sandboxd[100]: ([232]) coreaudiod(232) deny file-read-data /Library/Audio/Plug-Ins/Components/Flip4Mac WMA Import.component
5/1/14 1:34:26.396 PM sandboxd[100]: ([232]) coreaudiod(232) deny file-read-metadata /Library/Audio/Plug-Ins/Components/Flip4Mac WMA Import.component/Contents
5/1/14 1:34:26.469 PM sandboxd[100]: ([232]) coreaudiod(232) deny file-read-metadata /Library/Audio/Plug-Ins/Components/Flip4Mac WMA Import.component
5/1/14 1:34:45.013 PM loginwindow[44]: CoreAnimation: warning, deleted thread with uncommitted CATransaction; set CA_DEBUG_TRANSACTIONS=1 in environment to log backtraces.
5/1/14 1:35:55.229 PM com.apple.backupd[382]: Starting automatic backup
5/1/14 1:35:56.000 PM kernel[0]: nspace-handler-set-snapshot-time: 1398976558
5/1/14 1:35:56.801 PM com.apple.mtmd[39]: Set snapshot time: 2014-05-01 13:35:58 -0700 (current time: 2014-05-01 13:35:56 -0700)
5/1/14 1:35:57.092 PM com.apple.backupd[382]: Attempting to mount network destination URL: afp://Steve%20MYLAST NAME;[email protected]/Data
5/1/14 1:35:57.000 PM kernel[0]: AppleSRP started.
5/1/14 1:35:57.988 PM NetAuthSysAgent[384]: TUAMHandler::SetUAMType setting UAMType to 13
5/1/14 1:36:13.762 PM mds[40]: (Normal) Volume: volume:0x7fa78c823000 ********** Bootstrapped Creating a default store:0 SpotLoc:(null) SpotVerLoc:(null) occlude:0 /Volumes/Data
5/1/14 1:36:13.791 PM com.apple.backupd[382]: Mounted network destination at mount point: /Volumes/Data using URL: afp://Steve%20Mylastname;[email protected]/Data
5/1/14 1:36:34.000 PM kernel[0]: hfs: mounted Time Machine Backups on device disk2s2
5/1/14 1:36:35.728 PM com.apple.backupd[382]: Disk image /Volumes/Data/Steve’s MacBook Pro.sparsebundle mounted at: /Volumes/Time Machine Backups
5/1/14 1:36:36.373 PM com.apple.backupd[382]: Backing up to /dev/disk2s2: /Volumes/Time Machine Backups/Backups.backupdb
5/1/14 1:36:48.728 PM com.apple.backupd[382]: Event store UUIDs don't match for volume: Macintosh HD
5/1/14 1:36:49.579 PM com.apple.backupd[382]: Deep event scan at path:/ reason:must scan subdirs|new event db|
5/1/14 1:36:55.082 PM parentalcontrolsd[417]: StartObservingFSEvents [849:] -- *** StartObservingFSEvents started event stream
5/1/14 1:37:08.851 PM pacemaker[191]: error reading drift value from file /var/db/ntp.drift
5/1/14 1:38:23.737 PM pacemaker[191]: no drift value available, exiting
5/1/14 1:40:36.497 PM Check Off[242]: CGSGetWindowTransformAtPlacement
5/1/14 1:40:36.498 PM Check Off[242]: CGSTranslatePointForWindow
5/1/14 1:40:36.498 PM Check Off[242]: CGSGetWindowBounds
5/1/14 1:40:36.567 PM loginwindow[44]: ERROR | -[LWBuiltInScreenLockAuthLion closeAuthAndReset:] | Attempted to remove an observer when not observing
5/1/14 1:40:36.795 PM WindowServer[94]: CGXDisplayDidWakeNotification [823063370429]: posting kCGSDisplayDidWake
5/1/14 1:40:36.797 PM WindowServer[94]: handle_will_sleep_auth_and_shield_windows: Deferring.
5/1/14 1:40:40.402 PM Check Off[242]: CGSGetWindowTransformAtPlacement
5/1/14 1:40:40.402 PM Check Off[242]: CGSTranslatePointForWindow
5/1/14 1:40:40.402 PM Check Off[242]: CGSGetWindowBounds
5/1/14 1:40:42.331 PM Check Off[242]: CGSGetWindowTransformAtPlacement
5/1/14 1:40:42.331 PM Check Off[242]: CGSTranslatePointForWindow
5/1/14 1:40:42.331 PM Check Off[242]: CGSGetWindowBounds
5/1/14 1:40:43.812 PM Check Off[242]: CGSGetWindowTransformAtPlacement
5/1/14 1:40:43.813 PM Check Off[242]: CGSTranslatePointForWindow
5/1/14 1:40:43.813 PM Check Off[242]: CGSGetWindowBounds
5/1/14 1:40:48.082 PM Check Off[242]: CGSGetWindowTransformAtPlacement
5/1/14 1:40:48.082 PM Check Off[242]: CGSTranslatePointForWindow
5/1/14 1:40:48.083 PM Check Off[242]: CGSGetWindowBounds
5/1/14 1:40:53.830 PM Check Off[242]: CGSGetWindowTransformAtPlacement
5/1/14 1:40:53.831 PM Check Off[242]: CGSTranslatePointForWindow
5/1/14 1:40:53.831 PM Check Off[242]: CGSGetWindowBounds
5/1/14 1:40:53.897 PM com.apple.SecurityServer[15]: Session 100017 created
5/1/14 1:40:58.472 PM Check Off[242]: CGSGetWindowTransformAtPlacement
5/1/14 1:40:58.472 PM Check Off[242]: CGSTranslatePointForWindow
5/1/14 1:40:58.473 PM Check Off[242]: CGSGetWindowBounds
5/1/14 1:41:06.127 PM Check Off[242]: CGSGetWindowTransformAtPlacement
5/1/14 1:41:06.127 PM Check Off[242]: CGSTranslatePointForWindow
5/1/14 1:41:06.127 PM Check Off[242]: CGSGetWindowBounds
5/1/14 1:41:12.888 PM Check Off[242]: CGSGetWindowTransformAtPlacement
5/1/14 1:41:12.888 PM Check Off[242]: CGSTranslatePointForWindow
5/1/14 1:41:12.888 PM Check Off[242]: CGSGetWindowBounds
5/1/14 1:48:35.000 PM bootlog[0]: BOOT_TIME 1398977315 0

Make a "Genius" appointment at an Apple Store, or go to another authorized service provider.
Back up all data on the internal drive(s) before you hand over your computer to anyone. There are ways to back up a computer that isn't fully functional—ask if you need guidance.
If privacy is a concern, erase the data partition(s) with the option to write zeros* (do this only if you have at least two complete, independent backups, and you know how to restore to an empty drive from any of them.) Don’t erase the recovery partition, if present.
Keeping your confidential data secure during hardware repair
Apple also recommends that you deauthorize a device in the iTunes Store before having it serviced.
*An SSD doesn't need to be zeroed.

Attempt to delete photo results in 'spinning beach ball'.

Similar Messages

Maybe you are looking for