OK, then please update the upstream bugtracker info accordingly. It's useful to know that the very latest code still suffers from the same problem. Let's take the workaround temporarily for now until the upstream gets the proper resolution. It's not ideal, but better than sorry.