Graphic Glitches on MacBook Still Unacknowledged By Apple

Some have wondered if the increased popularity of Apple products has resulted in a decreased level of quality. Here's yet another case of issues with a new product, as frustrated users have been reporting graphics problems with the Penryn-based 13" MacBooks and 15" MacBook Pros, released in February.

According to several threads in the Apple discussion forums, it appears the issues are most prevalent when playing QuickTime videos, although graphics corruption has also been seen when scrolling through Safari webpages or Mail messages.

Some have said the problems did not exist until they applied the MacOS X 10.5.2 Update.

One such post, related to QuickTime playback, says "When I am watching the Video Tutorials for any of Apple products my QT flickers dark and light, not to the point where I can't see the video, but to the point where it is annoying. Anyone else having this problem? This is on a 4 day old new MacBook. I have the most recent version of QT installed."

While Apple has not officially acknowledged the problem, a user posted the following message he said was received from Apple Technical Support:

"Apple has received reports similar to the behavior you are describing and we are investigating those reports. Further information will come in the form of a Knowledge Base article, Software Update, or Software Release."

The problem is, that message was delivered to him on March 12th! An update from that same user (posted Sunday) says:

Well, despite the notification I received from Apple that the problem has been acknowledged, a solution has obviously still not been provided.

However, to my knowledge the problem has not been "publicly acknowledged", so it is also possible that engineer resources have not been adequately assigned to the defect yet, and they are just hoping/expecting this issue not to get much traction online until they get around to working on it aggressively.

There were some sites that reported that Apple acknowledged the issue, but obviously that's notthe case. Over a month since they said they were looking into the solution and still no fix - and no official acknowledgement? I would expect better from Apple, as would most.

Pictures for this story