Comment 18 for bug 327428

OK, now it's getting absurd. It *still* hasn't been fixed in Maverick. Fortunately, the same patch works in the Maverick version as it does in the Lucid one, but come on - this problem has an identified cause, a known temporary solution (which does correct the problem, it's not just a workaround)... how has it not been addressed in the official version yet?

If the problem is in identifying when the correction needs to work, can't a simple file be introduced that allows users to set the appropriate values, should they find that the defaults not be acceptable? Just a config file that, if absent, leaves everything at defaults?