Glad to know that this fixed it.
In addition, you probably should know that Linux systems use a “loader cache,” which is re-populated by the sudo ldconfig command. Installer packages normally run this command for you, but, should you be mucking-around with libraries yourself, you might need to run it. Linux has a very flexible system by which applications (and libraries) can identify the libraries that they need, and the loader cache pre-calculates these answers so that a file-search does not have to ... and, indeed, does not ... occur. When you “re-installed,” this undoubtedly caused this command to be run, possibly fixing the problem. Anytime you see the loader saying that a library cannot be found when you know that it is there, rebuild the loader cache.