(In reply to Takashi Iwai from comment #35) > OK, I pushed the workaround patch to stable branch, while asking upstream > about a more proper fix (if any). Let's see. Any replies there? This is likely still not fixed upstream. At least not by the proposed patch.