[tor-bugs] #25485 [Applications/Tor Browser]: Browser/TorBrowser/Tor/libstdc++.so.6: version `CXXABI_1.3.11' not found (required by /usr/lib/x86_64-linux-gnu/libmirclient.so.9)

[Tor Bug Tracker & Wiki]

#25485: Browser/TorBrowser/Tor/libstdc++.so.6: version `CXXABI_1.3.11' not found
(required by /usr/lib/x86_64-linux-gnu/libmirclient.so.9)
--------------------------------------------+--------------------------
 Reporter:  cypherpunks                     |          Owner:  tbb-team
     Type:  defect                          |         Status:  reopened
 Priority:  Very High                       |      Milestone:
Component:  Applications/Tor Browser        |        Version:
 Severity:  Normal                          |     Resolution:
 Keywords:  ff60-esr, TorBrowserTeam201806  |  Actual Points:
Parent ID:                                  |         Points:
 Reviewer:                                  |        Sponsor:
--------------------------------------------+--------------------------

Comment (by boklm):

 It seems that the issue is that `libgdk-3.so.0` on Ubuntu is linked to
 `libmirclient.so.9`, which is linked to a newer version of
 `libstdc++.so.6` than the one we ship.

 Some (probably not good) solutions could be:
 - building and shipping a `libgdk-3.so.0` (and maybe libgtk3?) that is not
 linked to `libmirclient.so.9`. However this will increase the complexity,
 build time, and size of our bundles.
 - building and shipping a `libmirclient.so.9` that is linked to our
 version of `libstdc++.so.6`.

 I think a better option might be to avoid having our version of
 `libstdc++.so.6` in `LD_LIBRARY_PATH` when the version installed on the
 system is newer. Maybe the `start-tor-browser` script could detect which
 version of `libstdc++.so.6` is available and only add our version to
 `LD_LIBRARY_PATH` when needed.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/25485#comment:9>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online