Comment # 30 on bug 1193599 from
Are you still experiencing this problem or is it solved in upstream?


You are receiving this mail because: