iMovie and iWeb won't launch on Lion

[greatkemo]

Folks,

I have iLife 11 packaged where all the individual pkg files get copied to a a tmp directory and at reboot, a script runs and install them all. This method has been working for me for a while with Snow Leopard no issues, but now we are upgrading to Lion the issues start.

I deploy with the a Lion configuration in exactly the same way and everything installs ok, but when I test to see if everything is working, I find that only iDVD, iPhoto, and Garageband are working, iWeb and iMovie aren't, they would launch and you see their menus, but there is now window.

Have anyone come across this? I ready somewhere that this may be due to ~/Library being invisible... Any Ideas?
https://discussions.apple.com/thread/3371284?start=0&tstart=0

[mparker]

I know that iphoto, garageband and iMovie come installed now as stand alone installers with new computers (everything that used to be in /Library/Application Support for instance is packaged in the app)

I had some problems when I took a new macbook air with 10.7 on it and tried to install just iWeb and idvd from a dvd the result was that iPhoto tried to install as well and was broken. Once I installed the 10.7.3 combo update that problem fixed itself (although later I removed iPhoto completely and put the original version back on). I can't tell you why, but it was repeatable. I would suggest installing the 10.7.3 combo update if you haven't already and see if it fixes your problem.

[greatkemo]

The computers I am testing it on already are on 10.7.3 the odd thing on my personal mac I have iLife 11 on there and that is running 10.7.3 from an upgrade through the app store from snow leopard and its working fine, but the package I am deploying is not working fine on lion but seems to be working great on snow leopard

Very confused now :-/

[rob_potvin]

I am having the same issue where iMovie won't show up. I haven't even tried iWeb. I found that the combo update would fix this issue, after applying 10.7.2 or 10.7.3, iMovie window would show up.

The problem is now I find that this is happening to my 10.6.8 clients after imaging. iMovie menu shows but the actual window doesn't show up.

I have no idea why this is happening and since the ~/Library is not hidden on 10.6.8

If anyone has some ideas I am all ears.

[stevewood]

If the Lion machines you are deploying to shipped with Lion on them, and you did not re-image with your own baked version of Lion, then you will have to use the iLife apps that are in the Mac App Store. I tried installing iLife '11 on a machine that came with Lion on it, and it did not work.

As for 10.6, I've been using the method that Craig Ernst laid out in this thread:

https://jamfnation.jamfsoftware.com/discussion.html?id=2256

It has worked flawlessly for me. I do not run the script on reboot, I simply copy the PKG files to a temp directory and then run the script as an "after" script in Remote or as a policy.

Steve

[greatkemo]

Today I imaged a my same test machine with Lion again, and installed iLife 11 manually from DVD, and all components worked just fine, iMovie, iWeb, iPhoto, iDVD and GarageBand. No ain't that just about a B**? Anyway, tested my package on Snow Leopard and it worked fine, so I am a bit stomped, next thing I will try is to repackage iLife using the Package manifest from Composer 8.43, fingers crossed.

Kamal

[rob_potvin]

iLife package manifest from composer 8.43 doesn't seem to repair iMovie on any of the laptops that I have a problem with. I created an iLife DMG and PKG from a working iLife 11 installation.

I have a 10.7.2 machine here where iMovie doesn't work and a 10.6.8 machine where iMovie doesn't work. I ran the package that I made with Composer and it doesn't repair the machine. I got the 10.7.2 machine working by updating to 10.7.3. I ran the combo update on the 10.6.8 machine and no luck, still doesn't work.

Cheers

[greatkemo · Accepted solution]

UPDATE:

I went ahead and built the iLife Package using composer's manifest and it actually fixed my problem. Nothing special to it, and it works great now on 10.6.8 and 10.7.3

Thanks everyone, hope this helps