Description of problem: Thunderbird reports error ``` Error: couldn't find function symbol in library enableRNPLibJS chrome://openpgp/content/modules/RNPLib.jsm:1606 init chrome://openpgp/content/modules/RNPLib.jsm:91 once chrome://openpgp/content/modules/RNP.jsm:37 init chrome://openpgp/content/modules/RNP.jsm:54 init chrome://openpgp/content/BondOpenPGP.jsm:90 initOpenPGPIfEnabled chrome://messenger/content/msgMail3PaneWindow.js:536 _delayedStartup chrome://messenger/content/msgMail3PaneWindow.js:752 RNP.jsm:46:15 ``` Manually compiling version 1.2.1 of https://crates.io/crates/sequoia-octopus-librnp/1.2.1 fixed the issue. Version-Release number of selected component (if applicable): ``` Name : thunderbird Version : 91.3.0 Release : 1.fc34 Architecture : x86_64 ``` with ``` Name : sequoia-octopus-librnp Version : 1.1.0 Release : 1.fc34 Architecture : x86_64 ``` Steps to Reproduce: Already installed thunderbird using stock rnp. 1. sudo dnf swap thunderbird-librnp-rnp sequoia-octopus-librnp 2. start thunderbird (error in debug tools log - openpgp empty) Actual results: Error above, no keys in openpgp directory. Expected results: Additional info: I can't actually see this error being mentioned in the upstream repo issues post 1.1.0, last was 9 months ago. Although it seems to have happened twice with changes in TB. Although could it have been https://gitlab.com/sequoia-pgp/sequoia-octopus-librnp/-/issues/44 that fixed it before it was an issue. Anyway 1.2.1 current release manually installed: ``` git clone https://gitlab.com/sequoia-pgp/sequoia-octopus-librnp.git cd sequoia-octopus-librnp cargo build --release sudo cp target/release/libsequoia_octopus_librnp.so /usr/lib64/thunderbird/librnp.so sudo chcon system_u:object_r:lib_t:s0 /usr/lib64/thunderbird/librnp.so ``` ... worked for me™ with TB91.
Sorry for the trouble. It looks like the latest release fixes the problem? The recent sequoia-openpgp updates had been blocked by debugging / troubleshooting in a new hash function they use. For now I disabled the new hash function in Fedora builds, so I should hopefully be able to update sequoia-octopus-librnp soon.
> It looks like the latest release fixes the problem? Yes it seem it does. > so I should hopefully be able to update sequoia-octopus-librnp soon. Nice, thanks. I'll watch out and hopefully it can just overwrite my compiled and copied version :)
Yup, once the new version will get installed as an update, it should just replace your manually copied file. All Fedora systems are currently running at full load due to the mass rebuild for Fedora 36, so everything might take a bit longer than I'd like :/
FEDORA-2022-f227d92426 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-f227d92426
FEDORA-2022-f227d92426 has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.