Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

iPhoto crashes when NAS is connected

I have a quite new MacBook Pro with OS X Mountain Lion 10.8.2.


I experienced some problems with iPhoto since I work with a NAS (Synology 112j with one HDD/Western Digital).


Every time the NAS is connected to the network and the WiFi is on, iPhoto crashes when trying to start a slide show or build a new slide show. When the NAS is shutdown or I cut the WiFi, iPhoto works without any problems.


The iPhoto library is NOT exported to the NAS, it's still on my MacBook-HDD. The library is managed!


I tried to build up new libraries several times, but the problems occurs again and again.


I had a discussion in the iPhoto section of the community, but we couldn't get the problem fixed.


Now I try it here in the OS forum.


Maybe somebody experienced the same problem and got it fixed.


I would appreciate any help.

MacBook Pro with Retina display, OS X Mountain Lion (10.8.2)

Posted on Mar 15, 2013 1:48 PM

Reply
20 replies

Mar 15, 2013 6:49 PM in response to mjkrueger

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


Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left. If you don't see that menu, select

View Show Log List

from the menu bar.

Enter the name of the crashed application or process in the Filter text field. Select the messages from the time of the last crash, if any. Copy them to the Clipboard (command-C). Paste into a reply to this message (command-V).


When posting a log extract, be selective. In most cases, a few dozen lines are more than enough.

Please do not indiscriminately dump thousands of lines from the log into this discussion.


Important: Some private information, such as your name, may appear in the log. Anonymize before posting.


Step 2


Still in the Console window, look under User Diagnostic Reports for crash reports related to the process. The report name starts with the name of the crashed process, and ends with ".crash". Select the most recent report and post the entire contents — again, the text, not a screenshot. 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 shutdownStall, spin, or hang logs — they're very long and not helpful.

Mar 16, 2013 1:07 PM in response to Linc Davis

So, thats the lines from the Console when I started iphoto and tried to start a slide show then...


16.03.13 20:46:53,905 iPhoto[3576]: ImageIO: CGImageReadSessionGetCachedImageBlockData *** CGImageReadSessionGetCachedImageBlockData: bad readSession [0x80336280]

16.03.13 20:46:53,905 iPhoto[3576]: ImageIO: CGImageReadSessionGetCachedImageBlockData *** CGImageReadSessionGetCachedImageBlockData: bad readSession [0x7bb62990]

16.03.13 20:47:03,920 iPhoto[3576]: *** WARNING: -[NSImage compositeToPoint:operation:] is deprecated in MacOSX 10.8 and later. Please use -[NSImage drawAtPoint:fromRect:operation:fraction:] instead.

16.03.13 20:47:03,921 iPhoto[3576]: *** WARNING: -[NSImage compositeToPoint:fromRect:operation:] is deprecated in MacOSX 10.8 and later. Please use -[NSImage drawAtPoint:fromRect:operation:fraction:] instead.


There are no listings in the user Diagnostics Reports...!!!???

Mar 17, 2013 1:05 AM in response to Linc Davis

I start iPhoto and then it is no problem to open different pictures or import new ones.


When I try to start a slide show or try to create a new slide show, the programm freezes (there is this little rolling coloured ball). This happens also when I click on a already created slide show. Then the program is not responding anymore. I figured that after a very long time (20 minutes and more) the slide show starts!?!


Sometimes it helps when I create a new library. Then it works for three or four times.

Yesterday iPhoto let me start slide shows!!! Then I tried to integrate music from iTunes into a slide show (my music and also the iTunes library are on the NAS), the program freezes again (the rolling ball!). After that I couldn't open or start a slide show again.


Important: Under a different user account (my wife's) iPhoto works fine. At least you can start a slide show there without any problems.

Mar 17, 2013 6:51 AM in response to mjkrueger

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

First, empty the Trash.

Triple-click the line below to select it, then copy the selected text to the Clipboard (command-C):

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

Launch the Terminal application in any of the following ways:

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

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

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

Paste into the Terminal window (command-V). The command may take a noticeable amount of time to run. Wait for a new line ending in a dollar sign (“$”) to appear.

The output of this command, on a line directly below what you entered, will be a number such as "41." Please post it in a reply.

Mar 17, 2013 7:55 AM in response to mjkrueger

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

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


Step 1

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

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

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

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


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

Step 2 (optional)


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

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

When the OS X Utilities screen appears, select

Utilities Terminal

from the menu bar. A Terminal window will open.

In the Terminal window, type this:

res


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

resetpassword


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

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

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

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

Select

Restart

from the menu bar.

Mar 19, 2013 11:01 AM in response to Linc Davis

I followed Step 1. Actually it took NOT a noticeable amount of time for the Terminal application to run the command.


And also nothing changed, iPhoto still crashes when trying to start or open a slide show.


But I found out that after a while - sometimes after 5 minutes, sometimes after 15 minutes - iPhoto starts the slide show!!!


I also follwed Step 2.


Nothing's changing, iPhoto still does the same like before. 😐

Mar 19, 2013 3:40 PM in response to mjkrueger

Please read this whole message before doing anything.

This procedure is a diagnostic test. It’s unlikely to solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.
The purpose of the test is to determine whether the problem is caused by third-party software that loads automatically at startup or login.


Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards. Boot in safe mode* and log in to the account with the problem. The instructions provided by Apple are as follows:

  • Shut down your computer, wait 30 seconds, and then hold down the shift key while pressing the power button.
  • When you see the gray Apple logo, release the shift key.
  • If you are prompted to log in, type your password, and then hold down the shift key again as you click Log in.
*Note: If FileVault is enabled under OS X 10.7 or later, or if a firmware password is set, or if the boot volume is a software RAID, you can’t boot in safe mode.


Safe mode is much slower to boot and run than normal, and some things won’t work at all, including wireless networking on certain Macs. The next normal boot may also be somewhat slow.
The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.


Test while in safe mode. Same problem?


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

Mar 20, 2013 3:08 PM in response to mjkrueger

Please read this whole message before doing anything.

This procedure is a diagnostic test. It won’t solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.

Third-party system modifications are a common cause of usability problems. By a “system modification,” I mean software that affects the operation of other software — potentially for the worse. The following procedure will help identify which such modifications you've installed. Don’t be alarmed by the complexity of these instructions — they’re easy to carry out and won’t change anything on your Mac.


These steps are to be taken while booted in “normal” mode, not in safe mode. If you’re now running in safe mode, reboot as usual before continuing.


Below are instructions to enter some UNIX shell commands. The commands are harmless, but they must be entered exactly as given in order to work. If you have doubts about the safety of the procedure suggested here, search this site for other discussions in which it’s been followed without any report of ill effects.


Some of the commands will line-wrap or scroll in your browser, but each one is really just a single line, all of which must be selected. You can accomplish this easily by triple-clicking anywhere in the line. The whole line will highlight, and you can then copy it. The headings “Step 1” and so on are not part of the commands.


Note: If you have more than one user account, Step 2 must be taken as an administrator. Ordinarily that would be the user created automatically when you booted the system for the first time. The other steps should be taken as the user who has the problem, if different. Most personal Macs have only one user, and in that case this paragraph doesn’t apply.


Launch the Terminal application in any of the following ways:


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


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


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


When you launch Terminal, a text window will open with a line already in it, ending either in a dollar sign (“$”) or a percent sign (“%”). If you get the percent sign, enter “sh” and press return. You should then get a new line ending in a dollar sign.


Step 1


Triple-click the line of text below to select it:

kextstat -kl | awk '!/com\.apple/{printf "%s %s\n", $6, $7}'

Copy the selected text to the Clipboard by pressing the key combination command-C. Then click anywhere in the Terminal window and paste (command-V). Post the lines of output (if any) that appear below what you just entered. You can do that by copying and pasting as well. Omit the final line ending in “$”. No typing is involved in this step.

Step 2


Repeat with this line:

sudo launchctl list | sed 1d | awk '!/0x|com\.(apple|openssh|vix)|edu\.mit|org\.(amavis|apache|cups|isc|ntp|postfix|x)/{print $3}'

This time you'll be prompted for your login password, which you do have to type. It won't be displayed when you type it. Type it carefully and then press return. You may get a one-time warning to be careful. Heed that warning, but don't post it. If you see a message that your username "is not in the sudoers file," then you're not logged in as an administrator.


Note: If you don’t have a login password, you’ll need to set one before taking this step. If that’s not possible, skip to the next step.


Step 3

launchctl list | sed 1d | awk '!/0x|com\.apple|edu\.mit|org\.(x|openbsd)/{print $3}'

Step 4

ls -1A /e*/mach* {,/}L*/{Ad,Compon,Ex,Fram,In,Keyb,La,Mail/Bu,P*P,Priv,Qu,Scripti,Servi,Spo,Sta}* L*/Fonts 2> /dev/null

Important: If you formerly synchronized with a MobileMe account, your me.com email address may appear in the output of the above command. If so, anonymize it before posting.


Step 5

osascript -e 'tell application "System Events" to get name of every login item' 2> /dev/null

Remember, steps 1-5 are all copy-and-paste — no typing, except your password. Also remember to post the output.


You can then quit Terminal.

iPhoto crashes when NAS is connected

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.