Closed nickguletskii closed 8 years ago
The workaround is to compile using an old compiler to link against an old libstdc++. The problem is that some applications ship old libstdc++ with them, so GLXOSD crashes because it needs a newer libstdc++.
Please see the according FAQ entry.
There is a useful workaround for many games - very often they have libstdc++.so
library somewhere in their game directory (usually in lib/
or similarly named subdirectory). By moving/renaming/deleting that file, the game will no longer be able to its own (old) libstdc++ library and will instead use the system one (newer). In 99% of cases, the game will run just fine without any issues, and glxosd will start working with it as well. I have just tested this myself with an affected game.
So the workaround would be:
libstdc++.so*
in the game directory, including subdirectories (if you find libgcc*.so*
, you can try the same approach with it as well)_disabled
suffix)Could you please add this to the FAQ entry? I believe it would help quite a few people. (I wanted to send you a pull request for that FAQ, but it seems your gh-pages
branch is out of date, older than what you have on your web).
This issue should be fixed in GLXOSD v3.
Due to the stupid ABI, GLXOSD does not work in some applications on some distributions.
The only real workaround I see is rewriting the whole project from scratch without using libstdc++.
There is no ETA.