Comment 17 for bug 1483276

I know it's strange, but I'm almost certain that the version of Ubuntu where I first had the issue, it only came after doing a fresh install, previously it had worked on a fresh install as well. But this update definitely fixes it for me. Seems it doesn't affect all though, but if you can test that the updated version in -proposed doesn't break the functionality for you then I don't see a problem in releasing it if it fixes the problem for those who have it.