IPhoto '08 Oddity

When I try to do a batch date change in iPhoto, I change the month, tab to the day and change it, tab to the year and change it and for some reason it automatically changes the time. For instance, if I'm changing the date from 1/1/2001 to 1/1/2000, as soon as I tab to the year and change the date, the time is changed from 12:00:00 PM to 11:59:59 AM.
I've done a fresh install of Mac OSX and of iLife and the problem still exists. I also created a new account and a new iPhoto Library and it still happens. I have another MacBook Pro and I don't have this problem with iPhoto on it.

OK I'll try that but FYI if I move that library to a different MBP I don't have this problem.
I posted here because I thought it might be a iPhoto problem but it might be something else now.

Similar Messages

IPhoto to Aperture Library Transfer Oddity

Or maybe I should have just said iPhoto Library oddity, since Aperture seems fine, and in the end, seems to have done what it should have.
Let me explain:
A few weekends ago, I started to transfer my entire iPhoto library from iPhoto v7.x (current version) to my Aperture v2 library. I started my iPhoto library over three years ago, using iPhoto v5 and OS X 10.4, later upgrading to iPhoto v6 via iLife ’06 in mid 2006, and finally iPhoto v7 via iLife ’08 last Fall. I then upgraded to Leopard and Aperture v2 this past Spring.
After transferring some 46,000 photos (with most being RAW + Jpeg pairs) from iPhoto to Aperture, I noticed that a there were a large number (approximately 1,800) of stacked photos were one photo was an iPhoto Original RAW photo, and the other was an iPhoto Edited RAW photo. The curious thing is, I didn't edit all of those RAW files in iPhoto, I only edited a select few dozen of them. It should be noted that all of the edited and original Jpegs pairs were also stacked, and the orientation of all of them looked fine.
As it turned out, all of these mysteriously edited photos were shot as verticals, none were horizontals. And when looking at the unstacked pair, the edited photo was properly rotated, but the Original iPhoto RAW photo was not, despite having its orientation listed as portrait. When I rotated an Original iPhoto RAW photo to correct it, the orientation was changed to landscape, even though the photo was displayed in portrait mode.
Upon further digging, it seems that all of the vertical photos that were imported into iPhoto v5 were affected, as were some of the vertical photos that were imported by iPhoto 6, but none of the photos imported be iPhoto v7. I don't remember the exact dates that I imported them and when I upgraded iPhoto, but the timeline seems close.
I also noticed recently when using iPhoto that the info display panel listed some of the RAW photos as “Jpeg (From Nikon RAW)”. I have not spot checked these files yet, but I suspect that these are the photos that resulted the creation of the Original & Edited iPhoto stacked pair in Aperture.
I do realize that iPhoto converts RAW files to Jpegs if you edit them, and I would expect that it does not when you don’t edit them. However, it would appear that iPhoto v5 always did when it rotated them, iPhoto v6 did some times, and iPhoto v7 doesn't.
I’m puzzled as to how these RAW files got edited in the first place.
I can only guess that it happened as either:
1) The result rebuilding the cache at some point, or
2) Possible as a result of a conversion process for the iPhoto updates, or
3) How iPhoto handled RAW files, particularity with iPhoto v5.
But as to why these particular files were affected, and most of the vertical shots were OK, I don't know. Any Ideas?
As for the iPhoto edited RAW photos, I plan to delete them since there doesn't seem to be a point in keeping them, because I have the original RAW file, and the original and edited Jpeg versions. They were easy to find using keyword and Aperture excellent filtering tool.
Incidently, I've also had some problems with the "Black Frames" problem and also the "Unsupported File Format" error with photos that were directly imported into Aperture. I hope that my photos are not corrupted.
Other than that, I'm really liking Aperture2 a lot!

My iPhoto library shrunk drastically when I switched to Aperture, from around 13.8GB it dropped to 9GB. I was worried at first but everything appears to have showed up.
The only things that I can attribute it to is the fact that when an image is imported into iPhoto with auto rotate data, the image is duplicated before it is rotated in Aperture it is not.
iPhoto duplicates the image on virtually every modification.
My iPod photo cache was quite large as well, but Aperture does not import this.
Videos you may have in iPhoto will not be imported into Aperture.
I also get the feeling that preview and tumbnail data is more optimized in Aperture.
If you are unsure backup your iPhoto library to an external drive as a read-only disk image, then if you find any problems with your photos in Aperture you can go to the disk image and get them.

Iphoto '11 cannot show slideshow for files on NFS (Faces fails, too)

Hello, please help me see my pictures in slideshow! I get black pictures, but I have a unique error (google has zero hits on '"NULL CGImageSource" iphoto'). See details below. Thanks!
I'm using iPhoto '11 (9.1.5 (615)).
My preferences have UNCHECKED "copy items into the iPhoto Library". I want my pictures to remain on my linux (NFS) server so that other PCs can view them in their existing directory tree organization.
I import the files into iPhoto. I see them all. yay!
I also import files from my iPhone. These most likely reside on my local Mac drive rather than on the server. yay.
Signs that things are strange:
- I can use Faces to identify faces for those pictures which originated on my iPhone(now on local drive), but not those stored on the NFS location.
- When I use the slideshow, pictures which originated on my iPhone (now on local drive) appear, but not those stored on the NFS location. These are black screen. If I use a Theme such as Snapshots, then I see the white borders, and blackness inside. No, I didn't shoot *every* picture with the lens cap on.
- (THIS IS THE KEY ERROR MESSAGE FOR APPLE SOFTWARE ENGINEERS TO INVESTIGATE!) Console is spewing errors such as:
7/27/11 11:49:50 PM    iPhoto[1541]    NULL CGImageSource for Path - /Volumes/network/yoda/yoda/rbrown/misc/pics/gretchen/2001/IMG_0046.JPG!!!
I find this odd, because IT'S THE WRONG PATH! The correct path only contains one "yoda" in the tree hierarchy, i.e.
/Volumes/network/yoda/rbrown/misc/pics/gretchen/2001/IMG_0046.JPG rather than
/Volumes/network/yoda/yoda/rbrown/misc/pics/gretchen/2001/IMG_0046.JPG
I should note that from iPhoto, if I click "File->Reveal in Finder", the Finder launches to the correct location (one "yoda" in hierarchy). It opens on /Volumes/network/yoda/rbrown/misc/pics/gretchen/2001/IMG_0046.JPG and I see the file.
The mount itself looks like:
[hansolo:pics/in/VivaVienna2010] rbrown% mount
/dev/disk0s2 on / (hfs, local, journaled)
devfs on /dev (devfs, local, nobrowse)
map -hosts on /net (autofs, nosuid, automounted, nobrowse)
map auto_home on /home (autofs, automounted, nobrowse)
yoda:/home on /Volumes/network/yoda (nfs, nosuid)
And I'm not confused about the directory tree:
[hansolo:pics/in/VivaVienna2010] rbrown% ls -la /Volumes/network/yoda/yoda
ls: /Volumes/network/yoda/yoda: No such file or directory
[hansolo:pics/in/VivaVienna2010] rbrown% ls -lad /Volumes/network/yoda/rbrown
drwxr-xr-x 122 rbrown messagebus 12288 Jul 26 00:42 /Volumes/network/yoda/rbrown
[hansolo:~] rbrown% ls -la /Volumes/network/yoda/rbrown/misc/pics/gretchen/2001/IMG_0046.JPG
-rw-r--r-- 1 rbrown messagebus 789848 Nov 10 2001 /Volumes/network/yoda/rbrown/misc/pics/gretchen/2001/IMG_0046.JPG
Once I discovered this oddity, I thought maybe there was something about the way I browsed in iPhoto to find the pictures to import. I had gone through the "yoda" share on the left-side of the file selection box. So I deleted the pictures from iPhoto, and decided to use a symbolic link, which I had created in my home area on the Mac:
[hansolo:~] rbrown% ls -la /Users/rbrown/yoda
lrwxr-xr-x 1 rbrown staff 21 Feb 2 23:07 /Users/rbrown/yoda -> /Volumes/network/yoda
When I import photos into iPhoto using the "rbrown" item with the house icon (my Mac home directory) on the left-side of the file selection box, and then click through "yoda" and then through "rbrown" and "misc" etc. etc., to find the same files via the non-canonical path of /Users/rbrown/yoda/rbrown/misc/pics/gretchen/2001/, here's what happens:
- I have to highlight files, not the directory.
- If I hightlight the files, then they import okay into iPhoto, and appear on the main window
- The slideshow still doesn't work (black images)
- The Console error message changes(!) to:
7/27/11 11:54:03 PM    iPhoto[1541]    NULL CGImageSource for Path - /Masters/IMG_0022.JPG!!!
I have no idea where "/Masters" originated. I have no such directory anywhere, to my knowledge.
Help! okthxbye.
          -rb

In iPhoto 11 the Originals folder is renamed Masters.
IPhoto menu -> Provide iPhoto Feedback and report the bug.
Regards
TD

IPhoto album "not found" / Communication error...

Having a really weird problem with Front Row... it likes everything but iPhoto! It pulls my iTunes across my network with no problem, it plays movies, trailer and video clips locally and across the network with no problems, but when it comes to iPhoto, it throws a snit.
Seriously, when I select the "Photos" section, it sees the shared iPhoto library across my network, so it tries to go load it. About three seconds after it starts trying to pull the shared library across, it throws up an error: "The album you selected could not be found," then it suggests that there was either a communications error or that the server went offline, although neither is true. Note that it never gets to the point where I can choose an album - it doesn't show any albums, only the error message.
Has anyone else seen this?
First, it should be noted that the Front Row computer is attached to a projector that can only display up to 800x600. iPhoto on this computer launches, but first throws up an error that the display is not optimal for that application. The machine is otherwise quite strong: Mini dual-core, 1GB RAM, 45+GB free HD.
Here's what I've done in the meantime...
1) Reinstalled iPhoto 6 from the beginning. Tested - no dice. Applied 6.0.1 and 6.0.2. No dice.
2) Repaired perms on the server. No dice.
3) Checked iPhoto on the Front Row machine - it does see the shared library and has no problem bringing the library across.
4) Changed libraries - I use three different libraries regularly - no dice. #3, above, recognized each library just fine, incidentally.
5) Created a generic user account on the iPhoto "server," ran iPhoto (which creates a new, blank library), put four pictures in it. iPhoto on the Front Row mac saw the new library with no problem. Front Row, however, gaves the same error.
6) Rebooted everything (of course). No luck.
7) I've "googled" the error messages, with no applicable results.
8) I've put aliases to the libraries in the Front Row machine's user account's "Pictures" folder. The Front Row machine's iPhoto didn't like it, nor did Front Row. Oh well... besides, this would be a workaround - not what I want.
9) The iPhoto "server" has a pretty straightforward name with no spaces or odd characters. The "share name" assigned in iPhoto has no odd characters or spaces. The Front Row machine, too, has a straightforward, short alphanumeric name.
10) Networking between the two is a reliable gigabit connection through a five-port gigabit switch. Communication is steady and very fast - as evidenced by iTunes working, video streaming, iPhoto recognizing libraries, etc.
11) Name resolution between the machines works just fine. There are no odd routing tables or other infrastructure hiccups that might bog it down.
12) I've pared down the share from "full library" to sharing only a single, tiny album. The album has a straightforward name with no spaces or odd characters and only a handful of pictures. No dice.

iPhoto on the Front Row computer does launch and, after I "OK" the warning about a suboptimal display resolution (an error I'd really like to eradicate), I do see the local iPhoto library.
I've tried several combinations to see what happens - I'll call the main "serving" computer "server," even 'tho it's not a "server," technically speaking - it's running regular ol' Tiger, same version as the Front Row machine ("FR").
1. Neither machine running iPhoto: Front Row doesn't see the server's collection, nor does it offer the local library, either.
2. Server running iPhoto, FR not: Front Row gives the error described above. When I quit Front Row, the iPhoto icon is bouncing, alerting me (again) to the fact that the display is suboptimal, so apparently Front Row is launching iPhoto in the background in order to connect (presumably) to the server's iPhoto library.
3. Server running iPhoto, FR running iPhoto: If I "OK" the suboptimal display error on the FR machine so that both FR and server are running iPhoto, I get the error described above when attempting to view the server's iPhoto collection. iPhoto on the FR machine, however, does see the server's iPhoto collection - I can browse it, view it, etc. just fine.
4. Server not running iPhoto, FR running iPhoto (again, clicking "OK" to get through that suboptimal display warning): FR iPhoto only displays local library; FR doesn't see server libraries and gives appropriate error.
Through all of this, I just noticed an oddity: at no point does Front Row attempt to let me browse the local iPhoto library... it only gives me the "shared albums" option. I need to check something but this could be an oddity: I don't believe there are any actual pictures or albums in the local library, only the server's library. Again, iPhoto does launch properly and will let me browse shared albums - I'm just not certain I populated the local library with anything. I'll check that tonight to see if it makes a whit of difference.

Calendar Crashes, iPhoto 6.0.3, and Missing Photos, Books, etc.

Last week I was creating a calender in iPhoto 6.0.2. It crashed twice while I was working on it. I submitted the crash logs to Apple and went on working with the calendar. Everything seemed fine.
Last night I upgraded to iPhoto 6.0.3 via Software Update. I checked permissions afterwards, then launched iPhoto 6.0.3 to work on my calendar. ALL of my photos since December 2004 were missing and I also had no books, albums, or calendars in the left side pane. I tried rebuilding the library and nothing changed. I have not yet tried to "recover" lost images.
I'm not sure if the iPhoto 6.0.2 calendar crash did this or the iPhoto 6.0.3 update, or the combination of the two. Does anyone have any ideas on how to get back all of this information? From what I've gathered, it looks like I should try iPhoto Library Manager. That seems to help some people. At the very least I hope to get all my Film Rolls back, but I would like all the other stuff as well.
Yes, I should have a more recent backup than I do, but Apple also needs to make the iPhoto Library data files more robust so it's easier to rebuild this information!

That did indeed recover all my "missing" photos. I guess there just isn't anyway to recover albums, calendards, greeting cards, slideshows, etc. Is that true?
I think I will revert back to my last backup and manually add the 10 or so rolls that I have taken since then. At least that way the only thing I lose is the calendar I was working on during the crash in iPhoto 6.0.2. I also plan on filing a bug on iPhoto with the crash log and the information about it corrupting my iPhoto Library. If iPhoto Library Manager can recover all my photos, then iPhoto itself should definitely be able to!
One other oddity I noticed was the iPhoto Library Manager would say it was importing Film Roll "Joss's Birthday", but then it would NOT actually use that as the name of the Film Roll in the rebuilt library. I figured since it obviously saw the name, it should use it. Maybe I had the preferences configured wrong.
Power Mac G5 Dual 2 GHz Mac OS X (10.4.6)

IPhoto 11 is so slow when opening

Very recently my iPhoto has become so slow when opening, it can take anywhere between 3 and 7 minutes, during this time my Macbook just hangs, I can't use any other programs.
I have attempted running the iPhoto first aid, I have picked all of the options on the first aid list and nothing has helped. I have tried quitting everything before opening iPhoto and this makes no difference. I have also deleted some of the photos from my library, but I don't have an exceptionally large library anyway, 1900 jpegs.
I am running iPhoto 11 version 9.4.2 with mountain lion 10.8.2, I have no issues with any other programs being slow.
Once it opens it is generally fine, but it's just turning a 20 second task into a 10 minute task.
Any help is greatly appreciated.

I have (had?) the identical problem, with just slightly different details (I'm on Lion, not Mountain Lion, and I haven't tried repairing anything yet in iPhoto). iPhoto used to start up in a reasonable amount of time, but it seems since updated to 9.4.2, the startup time is incredibly long (I'll guess 5-10x longer). Admittedly, I have one of the largest iPhoto libraries I've heard of, but I'm just really trying to see why the update changed startup time so much.
Note that I have 500GB of free space on my boot drive, and that creating a new iPhoto library results in a speedy startup.
An oddity I just now see after creating a new library is, when I go back to select my old library at iPhoto launch, there are two libraries listed, with identical names, and identical paths ("iPhoto Library" - /Users/UserName/Pictures/iPhoto Library). Looking in the finder, I only see one Library with that name. After playing around with opening either one, now the first one says "(default)" after it every time.
Note that I just added "(had?)" to the beginning of my post, as it seems like my library has started opening in the normal amount of time since I played around with the libraries (creating a new one, etc.). So maybe just creating a new library and then going back to the default library with help thatgurlwho too?

IPhoto 9.2.2 Crashing

Since updating to iPhoto v9.2.2 yesterday, iPhoto has begun crashing on a regular basis. I can't ever recall iPhoto crashing and I've been using it for years.
It almost always happens after I've used the "Enhance" editing feature.
I have a Lumix camera and shoot RAW as well as an iPhone 4. iPhoto has crashed during or after editing photos from both sources. Again, this never happened until this latest update.
I've tried repairing disk permissions and rebooted, but iPhoto continues to crash periodically.
Another oddity I experienced this a.m. - I tried dragging a couple of photos out of iPhoto to my desktop and received an error message (8003 I believe). I ended up rebooting my iMac and was successful at dragging the photos to my desktop after that, but I did experience another iPhoto crash after editing an image later. ???
Is anyone else experiencing this? Welcome any advice and TIA.
I only know enough to be dangerous when it comes to crash logs. Here's the most recent crash log if it helps...
Process:         iPhoto [585]
Path:            /Applications/iPhoto.app/Contents/MacOS/iPhoto
Identifier:      com.apple.iPhoto
Version:         9.2.2 (9.2.2)
Build Info:      iPhotoProject-629040000000000~2
App Item ID:     408981381
App External ID: 6836991
Code Type:       X86 (Native)
Parent Process: launchd [119]
Date/Time:       2012-03-09 11:28:36.330 -0800
OS Version:      Mac OS X 10.7.3 (11D50)
Report Version: 9
Crashed Thread: 0 Dispatch queue: com.apple.coreimage.tiles_lists_isolation
Exception Type: EXC_BAD_INSTRUCTION (SIGILL)
Exception Codes: 0x0000000000000001, 0x0000000000000000
Application Specific Information:
objc[585]: garbage collection is OFF
Thread 0 Crashed:: Dispatch queue: com.apple.coreimage.tiles_lists_isolation
0   com.apple.GeForceGLDriver     0x8f00548c 0x8effe000 + 29836
1   com.apple.GeForceGLDriver     0x8f0b673c 0x8effe000 + 755516
2   com.apple.GeForceGLDriver     0x8f098567 0x8effe000 + 632167
3   com.apple.GeForceGLDriver     0x8f0b6faf 0x8effe000 + 757679
4   com.apple.GeForceGLDriver     0x8f0056ae 0x8effe000 + 30382
5   com.apple.GeForceGLDriver     0x8f00573b gldTestObject + 92
6   GLEngine                       0x0eb9334c gleTestObject + 340
7   GLEngine                       0x0eb931ee glTestObjectAPPLE_Exec + 206
8   com.apple.CoreImage           0x93d280ec __collectTiles_block_invoke_048 + 238
9   com.apple.CoreImage           0x93d28aeb __CFDictionary::enumerateUsingBlock(void ( block_pointer)(void const*, void const*)) + 165
10 com.apple.CoreImage           0x93d27f59 __collectTiles_block_invoke_0 + 261
11 libdispatch.dylib             0x95f96126 _dispatch_barrier_sync_f_invoke + 30
12 libdispatch.dylib             0x95f965b6 dispatch_barrier_sync_f + 87
13 libdispatch.dylib             0x95f9670c dispatch_sync + 45
14 com.apple.CoreImage           0x93d27e4c FEOpenGLBitmapTile::collectTiles(FEOpenGLContext const*, signed char) + 192
15 com.apple.CoreImage           0x93be38ba -[FEOpenGLContext(Texture) collectBitmapsForAllTiles:] + 31
16 com.apple.CoreImage           0x93bdb0c0 -[FEOpenGLContext collect] + 43
17 com.apple.CoreImage           0x93cebefe fe_context_collect_(FEContext*, bool, bool) + 159
18 com.apple.CoreImage           0x93bdeafd -[FEContext collectAndFlushCache:] + 39
19 com.apple.CoreImage           0x93b9ffea -[CIContextImpl collect:] + 67
20 com.apple.CoreImage           0x93b9ea3f -[CIContext clearCaches] + 44
21 com.apple.iPhoto               0x000eeac5 0x1000 + 973509
22 com.apple.QuartzCore           0x9ae00e17 _ZL20CAOpenGLLayerDestroyP13CAOpenGLLayerb + 71
23 com.apple.QuartzCore           0x9ae00da8 -[CAOpenGLLayer dealloc] + 29
24 com.apple.iPhoto               0x0014e430 0x1000 + 1365040
25 com.apple.QuartzCore           0x9addf9e4 -[CALayer _dealloc] + 33
26 com.apple.QuartzCore           0x9adc9c50 CALayerRelease + 135
27 com.apple.CoreFoundation       0x954d62d9 CFRelease + 169
28 com.apple.QuartzCore           0x9add9880 CA::release_objects(X::List<void const*>*) + 27
29 com.apple.QuartzCore           0x9adc884b CA::Transaction::unlock() + 55
30 com.apple.QuartzCore           0x9addfb1f CA::Layer::~Layer() + 173
31 com.apple.QuartzCore           0x9add0e9f CA::release_root_if_unused(CA::Layer*, CA::Layer*, void*) + 57
32 com.apple.QuartzCore           0x9ad9892b x_hash_table_remove_if + 79
33 com.apple.QuartzCore           0x9adc7563 CA::Transaction::commit() + 213
34 com.apple.QuartzCore           0x9adeee4c +[CATransaction flush] + 32
35 com.apple.AppKit               0x92d7b4f4 -[NSView(NSLayerKitGlue) _drawRectAsLayerTree:] + 764
36 com.apple.AppKit               0x92c394e2 -[NSView _drawRect:clip:] + 4306
37 com.apple.AppKit               0x92c68c32 -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 1958
38 com.apple.AppKit               0x92c68fd3 -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 2887
39 com.apple.AppKit               0x92c36bf2 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 708
40 com.apple.AppKit               0x92d8bb70 -[NSNextStepFrame _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 286
41 com.apple.AppKit               0x92c3187c -[NSView _displayRectIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:] + 4817
42 com.apple.AppKit               0x92c2a79f -[NSView displayIfNeeded] + 1365
43 com.apple.AppKit               0x92d8ba3f -[NSNextStepFrame displayIfNeeded] + 91
44 com.apple.AppKit               0x92c2756d -[NSWindow displayIfNeeded] + 316
45 com.apple.AppKit               0x92c2a070 _handleWindowNeedsDisplayOrLayoutOrUpdateConstraints + 804
46 com.apple.CoreFoundation       0x95569f8d _runLoopObserverWithBlockContext + 29
47 com.apple.CoreFoundation       0x9553647e __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 30
48 com.apple.CoreFoundation       0x955363bd __CFRunLoopDoObservers + 413
49 com.apple.CoreFoundation       0x95508c24 __CFRunLoopRun + 1044
50 com.apple.CoreFoundation       0x9550847c CFRunLoopRunSpecific + 332
51 com.apple.CoreFoundation       0x95508328 CFRunLoopRunInMode + 120
52 com.apple.HIToolbox           0x9385217f RunCurrentEventLoopInMode + 318
53 com.apple.HIToolbox           0x93859412 ReceiveNextEventCommon + 168
54 com.apple.HIToolbox           0x93859356 BlockUntilNextEventMatchingListInMode + 88
55 com.apple.AppKit               0x92be9a9c _DPSNextEvent + 678
56 com.apple.AppKit               0x92be9306 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 113
57 com.apple.AppKit               0x92be5675 -[NSApplication run] + 911
58 com.apple.AppKit               0x92e79261 NSApplicationMain + 1054
59 com.apple.iPhoto               0x00010dda 0x1000 + 64986
60 com.apple.iPhoto               0x00010269 0x1000 + 6205

This crash is referencing Core Image which is at the heart of the OS.
I would start by trying to re-install iPhoto. If that doesn't work then you'll need to re-install the OS.
To re-install iPhoto
1. Put the iPhoto.app in the trash (Drag it from your Applications Folder to the trash)
2a: On 10.5: Go to HD/Library/Receipts and remove any pkg file there with iPhoto in the name.
2b: On 10.6: Those receipts may be found as follows: In the Finder use the Go menu and select Go To Folder. In the resulting window type
/var/db/receipts/
2c: on 10.7 they're at
/private/var/db/receipts
A Finder Window will open at that location and you can remove the iPhoto pkg files.
3. Re-install.
If you purchased an iLife Disk, then iPhoto is on it.
If iPhoto was installed on your Mac when you go it then it’s on the System Restore disks that came with your Mac. Insert the first one and opt to ‘Install Bundled Applications Only.
If you purchased it on the App Store or have a Recent Mac you can find it in your Purchases List.

Error enabling photo stream "iphoto was unable to connect to Photo Stream"

Whenever I try to enable Photo Stream, it times out after awhile, and I get the following error: "iPhoto was unable to connect to Photo Stream." (see below [1]). I "tcpdump" shows that the computer is trying to open connections to akamai (unrelated?) but not apple. I am using iPhoto 9.2 build 626.
There is one oddity in this scenario : I have one iCloud account that I am trying to use between three computers. I was able to register iPhoto on my mac book pro, but it is failing on my second.
thanks in advance,
-tom
08:26:35.984082 STP 802.1d, Config, Flags [none], bridge-id 8000.98:fc:11:54:7a:9e.8002, length 35
08:26:37.417858 ARP, Request who-has dd-wrt (Broadcast) tell 192.168.6.122, length 46
08:26:38.032082 STP 802.1d, Config, Flags [none], bridge-id 8000.98:fc:11:54:7a:9e.8002, length 35
08:26:39.977873 STP 802.1d, Config, Flags [none], bridge-id 8000.98:fc:11:54:7a:9e.8002, length 35
08:26:42.025748 STP 802.1d, Config, Flags [none], bridge-id 8000.98:fc:11:54:7a:9e.8002, length 35
08:26:42.435600 ARP, Request who-has dd-wrt (Broadcast) tell 192.168.6.122, length 46
08:26:43.971461 STP 802.1d, Config, Flags [none], bridge-id 8000.98:fc:11:54:7a:9e.8002, length 35
08:26:46.019515 STP 802.1d, Config, Flags [none], bridge-id 8000.98:fc:11:54:7a:9e.8002, length 35
08:26:47.453197 ARP, Request who-has dd-wrt (Broadcast) tell 192.168.6.122, length 46
08:26:47.965198 STP 802.1d, Config, Flags [none], bridge-id 8000.98:fc:11:54:7a:9e.8002, length 35
08:26:49.606268 IP 192.168.6.122.filenet-rmi > 239.255.255.250.ssdp: UDP, length 339
08:26:49.708805 IP 192.168.6.122.filenet-rmi > 239.255.255.250.ssdp: UDP, length 348
08:26:49.811498 IP 192.168.6.122.filenet-rmi > 239.255.255.250.ssdp: UDP, length 379
08:26:49.914098 IP 192.168.6.122.filenet-rmi > 239.255.255.250.ssdp: UDP, length 405
08:26:50.016310 IP 192.168.6.122.filenet-rmi > 239.255.255.250.ssdp: UDP, length 401
08:26:50.017171 STP 802.1d, Config, Flags [none], bridge-id 8000.98:fc:11:54:7a:9e.8002, length 35
08:26:50.118847 IP 192.168.6.122.filenet-rmi > 239.255.255.250.ssdp: UDP, length 401
08:26:50.221214 IP 192.168.6.122.filenet-rmi > 239.255.255.250.ssdp: UDP, length 393
08:26:51.958833 STP 802.1d, Config, Flags [none], bridge-id 8000.98:fc:11:54:7a:9e.8002, length 35
08:26:52.368490 ARP, Request who-has dd-wrt (Broadcast) tell 192.168.6.122, length 46
08:26:54.006909 STP 802.1d, Config, Flags [none], bridge-id 8000.98:fc:11:54:7a:9e.8002, length 35
08:26:55.004001 IP susans-pc.52389 > a173-223-237-54.deploy.akamaitechnologies.com.https: Flags [.], seq 187854:189302, ack 103254, win 65535, options [nop,nop,TS val 1073825952 ecr 2280611493], length 1448
08:26:55.004213 IP susans-pc.52389 > a173-223-237-54.deploy.akamaitechnologies.com.https: Flags [.], seq 189302:190750, ack 103254, win 65535, options [nop,nop,TS val 1073825952 ecr 2280611493], length 1448
08:26:55.004264 IP susans-pc.52389 > a173-223-237-54.deploy.akamaitechnologies.com.https: Flags [P.], seq 190750:191283, ack 103254, win 65535, options [nop,nop,TS val 1073825952 ecr 2280611493], length 533
08:26:55.004415 IP susans-pc.52389 > a173-223-237-54.deploy.akamaitechnologies.com.https: Flags [P.], seq 191283:191688, ack 103254, win 65535, options [nop,nop,TS val 1073825952 ecr 2280611493], length 405
08:26:55.035678 IP a173-223-237-54.deploy.akamaitechnologies.com.https > susans-pc.52389: Flags [.], ack 189302, win 4116, options [nop,nop,TS val 2280641050 ecr 1073825952], length 0
08:26:55.053470 IP a173-223-237-54.deploy.akamaitechnologies.com.https > susans-pc.52389: Flags [.], ack 190750, win 4116, options [nop,nop,TS val 2280641068 ecr 1073825952], length 0
08:26:55.060158 IP a173-223-237-54.deploy.akamaitechnologies.com.https > susans-pc.52389: Flags [.], ack 191283, win 4116, options [nop,nop,TS val 2280641074 ecr 1073825952], length 0
08:26:55.066460 IP a173-223-237-54.deploy.akamaitechnologies.com.https > susans-pc.52389: Flags [.], ack 191688, win 4116, options [nop,nop,TS val 2280641081 ecr 1073825952], length 0
08:26:55.209380 IP a173-223-237-54.deploy.akamaitechnologies.com.https > susans-pc.52389: Flags [P.], seq 103254:103691, ack 191688, win 4116, options [nop,nop,TS val 2280641223 ecr 1073825952], length 437
08:26:55.209522 IP susans-pc.52389 > a173-223-237-54.deploy.akamaitechnologies.com.https: Flags [.], ack 103691, win 65535, options [nop,nop,TS val 1073826154 ecr 2280641223], length 0
08:26:55.952463 STP 802.1d, Config, Flags [none], bridge-id 8000.98:fc:11:54:7a:9e.8002, length 35
08:26:57.386190 ARP, Request who-has dd-wrt (Broadcast) tell 192.168.6.122, length 46

Good catch, nifmus. I'm kicking myself for not checking system.log earlier! I have very similar messages in mine.
By any chance is your Library folder (or part of it) relocated to a separate disk? Or your entire home folder? I have part of my Library folder on a SSD for speed, but my home folder and some of the larger Library subdirectories are on a regular disk because they wouldn't fit on the small SSD. It's all tied together with symbolic links, and without problems... until Photo Stream came along and didn't like it.
I knew that sandboxd was involved somehow, but your post prompted me to focus on it. It's definitely the problem here. I found the following sandbox profile file inside the iPhoto application bundle:
/Applications/iPhoto.app/Contents/Library/LoginItems/PhotoStreamAgent.app/Conten ts/Resources/PhotoStreamAgent.sb
Inside this file are a bunch of definitions to control what PhotoStreamAgent is allowed to do. There are a bunch of lines under an allow-file-write* declaration which should allow PhotoStreamAgent to write to the above files listed in your log. Lines such as:
(home-regex #"/Library/Application Support/iLifeAssetManagement")
(home-regex #"/Library/Preferences/com\.apple\.iLifeAssetManagement\.crash\.plist(\.[^/]+)? $")
And many others. In my case, I suspect that the problem may be related to the fact that the final absolute path of those files may differ from what you'd get if you just substituted my home directory in for "home-regex" since I have stuff relocated around. Although since I was able to get it working with a blank home directory, also put in place via a symbolic link (so the final path differs), I'm not 100% sure of this.
What I do know right now is that there is a quick "hack" that fixed it for me. I don't like the hack and would strongly recommend against it, because it's likely to break the next time there's a software update for iPhoto. But it works until I can find a permanent solution.
To make it work, I edited the above file and changed the second line from "(deny default)" to "(allow default)". This, of course, defeats the whole purpose of the sandbox by allowing PhotoStreamAgent to do anything it wants, but it also allows stuff that is really supposed to be allowed but fails anyway for us.
If you want to try this, it helps to be familiar with the unix underpinnings of OS X. There's probably a way to do it in the normal graphical user interface, but as a longtime unix guy, I just jumped to the command line and did a "sudo vi (that long filename)". To do it via the gui method, you'll have to navigate to that folder in Finder (quickest way is to hit Cmd-Shift-G and copy/paste the path, or right-click iPhoto and "Show Package Contents", then drill down to the file), edit the file, save a copy (because you don't have permission to modify it), then copy the new version over the old (it will ask for an admin password).
Again, I don't recommend this because it's likely to break in the future and defeats the security that Apple intended with the sandbox, but it's a quick fix. I'll continue to investigate as I have time, trying to find out precisely what's causing the failure with the default sandbox profile.

IPhoto has changed its organization

Three days ago iphotos decided not to operate the way it had been since I bought it.
Used to be, create my Events.and when I wanted to go through them to edit.I w ould click on the particular event photo, and the entire folder would open so I could see all the photos.
Now, when I click on Events, the middle photo comes up, and I cannot get the upper scroll or the others to show unless I use the scroll on the right hand side, which is a PITA....it's slower as well.
Another oddity is when I go onto a Windows site..if I reply to a post on a forum, I have a large( or small) boxed outline that follows my scroll.it doesn't leave.. It also shows up on Desktop.
Thanks for you time.
Gail

Thanks Td.
I am most likely not being very specific..will attempt it again...
I have about 12,000 photos in iPhoto now, all of them are i the Events. They are all named and I had them sorted by date taken.
Four days ago, I would be able to go to iPhoto, click on Events, and all of the headers and photos would show up . Al I would need to do if I wanted to edit of re look at the photos was double click on the folder; ;e" Flowers", and the entire folder would open so I could see each photo individually..while all still on the same page.
Now, when I go to Events, and go to open an individual named folder, it opens, but not entirely. It automatically goes to the middle photo instead of opening the entire thing.And then, to scan over each photo, now I have to use the slider, which I didn't have to before.
Lol.does this make sense.? I do alot of editing and then copy and paste for a photo forum, and it does slow things down..I use PhotoBucket as my photo share site and it works fine with Mac, or at least seems to?
The browser is Google, without all the bells and whistles.
Thanks again.

Iphoto crashing after using mini-dvi to video adapter

Hi, IPhoto on my Macbook is crashing. I can open it, then as soon as I scroll down it locks up and I have to force quit.
This started happening right after I used a Mini-DVI to Video Adapter cable to hook my macbook up to my TV. The adapter/s-video connection worked and I was able to see the video on the tv. But iphoto immediately locked up the computer when I went to slide show and now it locks every time I open it.
Any ideas?
Thank you:)
Dorothy

It means that the issue resides in your existing Library.
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

Cannot open and update IPhoto after upgrading to OXYosemite

From the App store, I downloaded and installed OXYosemite. There are 2 more updates available: iPhoto and iMovie. When I try to upload them, the notice I get is "Update Unavailable with This Apple ID This update is not available for this Apple ID either because it was bought by a different user or the item was refunded or cancelled."
I have 2 apple IDs when I inquire about my ids. Signing in App Store with either of them, doesn't resolve the problem. I get the same notice. iTunes, Mac, mobile downloads, all use the same apple IP, only for the computer downloads from App Store isn't working.
What should I do?
Thanks, Sev

I have the same problem and can't find out how to correct it. Unable to update iPhoto or iMovie .. I get the same message as above user. Help!

I am having macbook air recently my iphotos did not open and was showing report apple and reopen but i came to know that by pressing alt and iphotos i open an new photo library and stored the pics but now how can i get the pics which i had in the earlier

i am having macbook air recently my iphotos did not open and was showing report apple and reopen but i came to know that by pressing alt and iphotos i open an new photo library and stored the pics but now how can i get the pics which i had in the earlier photo please help me to recover my photos

Well I'll guess you're using iPhoto 11:
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

IPhoto slideshow using mini-dvi to video adapter

When using the mini-dvi to video adapter to connect to my widescreen tv (via composite), to show iPhoto slideshows, the transistions between slides dont apear and there are no ken burns effects. The slideshow runs fine on my MacBook display (ie when not conected to the tv), and the is no other distortion or flickering (as reported in other threads), this seems odd to me or is it just a limitation of analogue output.
2Ghz MacBook, White Mac OS X (10.4.7)

It means that the issue resides in your existing Library.
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

I create a birthday calendar in iCal and then click on it in iphoto at the begining of the calendar project each year. Some how the birthday did not populate the photo calendar. Is there a way to add the birthday iCal calendar into the calendar project?

I created a birthday calendar to use in iphoto for calendar. When a new calendar project is started each year, I click on it in. Some how the birthday did not populate the photo calendar this year. The photo calendar is almost complete. Is there a way to add the birthday iCal calendar into the calendar project? I would prefer not to start over.

Hi,
If you first select the calendar on the left, so that its background is highlighted blue/grey, when you make a new events they should be added to that calendar.
Best wishes
John M

Cannot send email from within iPhoto

Using OX X 10.7.5 cannot send email from within iPhoto. I get this error message: "Your email did not go through because the server did not reply."
If I change the preference to use email, everything goes fine but I lose the formatting feature.

iPhoto Menu ->
Preferences ->
Accounts ->
Delete and recreate your email settings.
Alternatively, use Apple's Mail for the job. It has Templates too - and more of them. Check out the Stationery...

IPhoto '08 Oddity

Similar Messages

Maybe you are looking for