After 10.6.8 Mini Displayport to HDMI PROBLEM

I have filed a bug report two weeks ago for this issue here: https://bugreport.apple.com/ but my bug is still listed as "open" and it doesn't appear as if anyone has looked at it. I think everyone else should file reports to document their experiences there as well.

Hey, thanks so much for that update. That really brings some hope. Fingers crossed that it gets fixed sooner than later. 🙂

I'm truly surprised this bug has been left unfixed for so long. I have a late 2009 27" iMac with this issue. Does it affect 2010 and 2011 27" iMacs?

The bug has been unveiled for more than 2 months but Apple have nothing done yet. For me, I 've rolled back my os verion to 10.6.7 and forget the Lion. I guess it takes 1 day for Apple to fix the bug but appraently they dont care our eyes.

I know exactly how you feel. I tend to wonder how far the information goes when a customer calls in to the Apple tech desk and explains to them a widesread problem? I wonder if it's actually getting transfered to the whole technical department or is it just being memo'd into the system waiting for someone to actually acknowledge this. Seems by now there would've been a software update to address this but I have a feeling it will be addressed but it may be part of a much larger update seeing as Lion needs this fix as well.

There seem to be a bit of a progress as they have updated the bugreport i filed a couple of days ago (with id 9896423). They added "duplicate of bugreport id 9726669". So they seem to be very aware of this problem , question is how important they think it is.

I'm sure there are other critical bugs in Lion that needs to be patched so they will hopefully include it in a forthcoming update of Lion.

WGrose my iMac is from 2010, without thunderbold.

Anyone that can confirm if the 2011 iMac with thunderbolt has this issue too?

Folks, as much as this issue really frustrates me as well, you need to calm down. Writing as someone who works for a software development company that deals with bug reports, and as a former Apple employee, I can guarantee you that flailing about it in the forums and declaring that Apple doesn't care isn't going to solve it. It's only going to increase your own stress. Filing duplicate bug reports isn't going to fix it either. They're obviously aware of the problem. And while it frustrates all of us, this isn't the most pressing issue Apple is dealing with right now. They'll prioritize it and get it fixed.

In the meantime, pour yourself a dram and calm the **** down.

Now just a minute, while I understand what you're trying to say, you're backing up Apple in a way where you're starting to frustrate me. It's not that people are asking for new features and it's not like people are complaining about change in regards to Lion's features, we're talking about functionality that's been screwed with and now our computers are being rendered useless for what we use them for if we do an update past 10.6.7 or decide to upgrade to Lion.

Everything has been working just fine on my iMac and when I did the software update to 10.6.8 the brightness control didn't work when the iMac is used as a display and it's stuck on maximum brightness at that. So how do I deal with that? Doing a Time Machine restore took so long that I ended up doing a reformat as I need my iMac in use ASAP.

I'm inconvenienced, not Apple and since they broke functionality and it's been weeks now, they should make this a priority.

It really frustrates me that you would get this dramatic and use funky language as if the people here have some nerve constantly talking about it. Everyday that we are inconvenienced it should be talked about here. It's not like the problem has gone away. Your post really disturbed me, do you still work for Apple? Sheesh.

I can't tell if you're bring serious or not. Would you be happy if your $4000 TV was locked to maximum brightness after a manufacturer update? Because that's exactly what has happened. The fact that Apple is heavily pushing Lion onto customers makes the situation even worse. We're paying for the privilege of losing core functionality.

My bug report has also now been listed as a duplicate of ID#9726669. Unfortunately I can only view bugs that I have originated, so I have no way of checking the status of that bug. I agree that everyone should submit official feedback here to complain about this issue: http://www.apple.com/feedback/imac.html to make sure that this stays on their radar. In the meantime I have reverted back to OSX 10.6.7 while I wait....patiently....

I think it's sad this hasn't been addressed, yet. I'd imagine it can't be hard to implement a fix, and it's been 6 weeks since this bug was discovered. I know I reported it on June 23... Patience is a virtue.... of the bored. 🙂

Add another one to the list. I've invested a shed load of cash into my dream computer system and now this !

Two 27" imacs and I regularly use target display mode.. Hmm I don't think it's quite full brightness but must be some where near !

I've also upgraded one of them to Lion and I think the only full backup was before the Lion upgrade but after the 10.6.8 went on both at the same time . Hmm not happy about this at all !

I guess I may as well upgrade the other one to Lion too this is a very serious issue for me though.

The first time I've had a problem with an Apple update !

Simon

Having read through the topic in detail, I've just installed shades and it works for me , although obviously it's not going to help if I use the iMac display with my PC. ( which fortunatly I don't do very often !)

I think people should consider donating to the developer of shades !

The 'tint' function might even solve the problem with the white levels looking different between my two iMacs !!!

I also submitted feed back to Apple and will keep an eye on this thread .

Cheers

Simon

This bug is still apparent the latest developer builds of Lion. I wonder if this means a fix won't appear in 10.7.1.

My ticket was closed as a duplicate of #9726669, too. Hopefully the creator of that ticket reads this thread and replies with an update.

Th bug still being present in the latest developer build is somewhat disturbing. However, I can't see Apple not having a fix in 10.7.1 and 10.6.9, or in standalone pathces for 10.6.8 and 10.7

The problem is very disruptive for anyone that uses a 27" iMac as second dispaly for their main machine. While "Shades" works as a temporary fix for the general masses, it does not help for anyone that needs calibrated color, contrast and brightness (ie, photo workflow etc). So again, this problem is quite disruptive for many.

And quite frankly, superkev07 is only partially correct. Ranting in the forums and denouncing Apple as the anti-christ everytime there is a bug is not helpful. However, yes, opening bug reports is. If each person that is having this problem opens a bug report (just one per person), although it will get closed as a duplicate of the original, it gives Apple a watermark of how bad the issue is and can help highten the priority of resolving it.