Comment 140 for bug 842566

Is there anything we can do to help identify what the outstanding problem is and get this bug fixed? Perhaps it's just that some of us are running the 'wrong' package or haven't got the update yet (although I'm running a standard 12.04 installation with no PPAs, all updates installed etc.).