./tor-browser-linux-x86_64-14.0.2/tor-browser/Browser/start-tor-browser --verboseXPCOMGlueLoad error for file /home/poncho/Downloads/tor-browser-linux-x86_64-14.0.2/tor-browser/Browser/libmozgtk.so:./TorBrowser/Tor/libcrypto.so.3: version `OPENSSL_3.2.0' not found (required by /usr/lib64/libcryptsetup.so.12)Couldn't load XPCOM.
./tor-browser-linux-x86_64-14.0.4/tor-browser/Browser/start-tor-browser --verboseXPCOMGlueLoad error for file /home/poncho/Downloads/Firefox/tor-browser-linux-x86_64-14.0.4/tor-browser/Browser/libmozgtk.so:./TorBrowser/Tor/libcrypto.so.3: version `OPENSSL_3.2.0' not found (required by /usr/lib64/libcryptsetup.so.12)Couldn't load XPCOM.
This has Backport but I closed it for some reason I don't really remember.
Maybe because we discussed about switching to static linking for the tor daemon (see the logs)
So, it was merged to the nightly and alpha channels (will be shipped in 14.5a2) but not backported to 14.0.x stable, yet.
I don't have any problems with it with nightlies on my machine (Debian testing).
I could probably test a couple of other distros as well, but I'm not too worried of this change.
TBH, I think we could backport this to 14.0.x as well, and then re-backport the patch to switch to static deps.
this is a concern (not blaming anyone) - edit: also I am not an expert on TB/BB/MB builds are cherry picking and backporting and channels etc - PS this is not the first time and won't be the last
can we have some sort of script to check things, or after each stable release, verify fixes? @morgan