#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, TorBrowserTeam201808 | Actual Points: Parent ID: | Points: Reviewer: | Sponsor: --------------------------------------------+--------------------------
Comment (by mcs): Replying to [comment:37 boklm]: > Ah this is a good point, the browser will probably fail to restart on the systems where our version of `libstdc++` is required. Kathy and I agree that this change will cause the browser to fail to start after an update on systems that require our bundled libstdc++. A good catch by gk. > I am wondering if we could update `LD_LIBRARY_PATH` in the same way as the start script, during the update process, before restarting the browser. The problem with this suggestion is that the updater that will be used is already on people's systems, so we cannot make changes to it :) In general, I think we are putting too many important things inside start- tor-browser. Or to put it another way: after an update the browser should be started the same way as when users start the browser. In an ideal world, ./firefox would do everything necessary. We could move all of the start-tor-browser code into a script named firefox and rename the actual binary to something else)... but I don't know what that would break. -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/25485#comment:39> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online
_______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs