This bug still exists in Maverick. Just retested with 2.6.35-22-server. Is anyone out there even tracking this bug or should I just give up?
This bug still exists in Maverick. Just retested with 2.6.35-22-server.
Is anyone out there even tracking this bug or should I just give up?