Anton Vorobyov Sun, 18 Jan 2015 11:25:10 -0800
One of recent (during ~2 last weeks) updates resolved this issue. Bug can be closed now.
