This bug is not fixed. Never has been, and not likely going to be fixed in the near future.
The real reason of this bug is that binaries compiled by g++ is exposing weak symbols that it's not supposed to expose. I heard that since the fix requires an ABI change in libstdc++, it won't get fixed until libstdc++7 is released. There are also many bugs reported in LP that is actually a duplicate of this bug, so please don't close it if there is only a workaround, but no real fix. (The GTK_IM_MODULE=xim fix in acroread is just a work around.)
I'll provide links to other distro's BTS on this bug soon, also marking other bugs reported in LP as a duplicate of this.
This bug is not fixed. Never has been, and not likely going to be fixed in the near future.
The real reason of this bug is that binaries compiled by g++ is exposing weak symbols that it's not supposed to expose. I heard that since the fix requires an ABI change in libstdc++, it won't get fixed until libstdc++7 is released. There are also many bugs reported in LP that is actually a duplicate of this bug, so please don't close it if there is only a workaround, but no real fix. (The GTK_IM_MODULE=xim fix in acroread is just a work around.)
I'll provide links to other distro's BTS on this bug soon, also marking other bugs reported in LP as a duplicate of this.