Even after the bug fix is released, the question may be useful to someone who has not applied the fix (so they know they should apply the fix). It may also be useful to someone who experienced the problem in the past and assumed there was no solution. Furthermore, the workarounds people have posted may also be useful again for people who are (1) running the software from a live CD that was mastered before the update was released or otherwise doesn't incorporate the update, or (2) experiencing a later, similar bug.
Therefore, I think the best thing to do for the community is to post an answer explaining that this is due to such-and-such bug and that the bug was fixed and explaining briefly how to update to get the fix. Assuming you promptly (i.e., shortly after two days time) accept this answer to your question, I think having that clearly answered question more than makes up, in value to the community, for the clutter the question introduces. Furthermore, with this as the accepted answer, people will not be fooled into thinking that any outdated information is still applicable.
Clearly, once the fix is released, updating will be the best solution, so there's nothing wrong with accepting your answer even in the face of others that offered worthy workarounds. Those other answers may deserve upvotes; but yours, explaining how to get rid of the problem entirely, should be the accepted answer.
I think it's acceptable, though less ideal, to simply delete the whole question. However, I feel that you should be very reluctant to do this, unless you know that all the workarounds posted are readily accessible somewhere else that's likely to stay online. In particular, if all the workarounds are also posted as comments on the Launchpad bug page, then I think it may make sense to decide your question has come to be of minimal value to the community. (I do not think you should post the workarounds on Launchpad, so that you can feel better about then deleting your question.)