iTunes 8 - No interface on Leopard. STRANGE

Dr.Wong

Registered
Hey guys,

After updating to iTunes 8 on 10.5.4 my Mac is resembling windows.

Have a look at the attached pic, anyone else getting this?

Is there a fix?
 

Attachments

  • screen.png
    screen.png
    886.9 KB · Views: 14
Yeah, it's a recurring problem.

It's been happening for the past few days. Done many shutdowns, restarts etc
 
Have you tried with a fresh user account, just to test whether it's a settings-related problem?
 
What do you see in Console when you run iTunes?
Were there any installation errors or did you have any applications running when you installed the update?
Do you have any QuickTime related plugins or other applications using QuickTime? Did you also update QuickTime when you installed iTunes?

That's way more lucky than I am.. the MB keeps only wanting to restart, and it never even downloads iTunes 8.
 
There is nothing funny in the console.

iTunes starts up fine and I can be using it with no problem, then all of a sudden it goes white like in the screenshot above.

When it does this, music still plays and my iPod carries on syncing until it's done.

Sometimes the interface returns to normal, but usually I have to quite and start the app again.

I think it's a problem with iTunes 8, not a settings issue.

Giaguara :

I did install the newest quicktime update that came out around the same time as iTunes 8. When I installed the app I may have been running Dreamweaver CS3 and Photoshop CS3.

I have perian installed.
 
All of those things pose no problem for me with iTunes 8, so I guess it's not those things.
 
You probably don't have the exact same configuration and exact same everything as he does.
Or since iTunes was QAd with every combination of everything and the problem was not detected, the problem does not exist :)


Keep Console open, with All messages, and when the GUI is lost, there will have to be something showing in there.

Reinstalling the program sounds a bit Windows solution, but could you reinstall iTunes 8 and see if that solves it?
 
What I meant was: If you _really_ want to test whether it's a settings issue, you kinda _have_ to test against a clean user account. Just saying you don't *think* it's a settings issue and rather it's the app's fault doesn't make it so.
 
Back
Top