[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [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)



#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 sukhbir):

 Replying to [comment:39 mcs]:

 > 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.

 I am not sure but doesn't that break the updater as well? Or would it
 simply replace the Firefox executable with the script and add the new
 binary?

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/25485#comment:41>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs