Hello,
I can confirm an OpenPGP regression after upgrading Thunderbird from 140
to 153 on Debian testing (forky).
Installed versions:
- thunderbird: 1:153.4.0esr-1
- libsequoia-octopus-librnp: 1.11.1-10
- librnp0: 0.18.1-2+b1
With libsequoia-octopus-librnp installed, Thunderbird's Troubleshooting
Information page reports:
RNP (OpenPGP):
Status: Failed to load. OpenPGP will not work.
Expected minimum version: 0.18.1
Version in use: -
Path: -
The OpenPGP Key Manager is completely empty, including my own private
key. Under Account Settings -> End-To-End Encryption, Thunderbird still
remembers the configured key ID but displays:
This key could not be found! If you want to use it
you must import it to Thunderbird.
Both pubring.gpg and secring.gpg are still present in my Thunderbird
profile.
The installed librnp.so symlink points to:
/usr/lib/thunderbird/librnp.so
-> ../sequoia/libsequoia_octopus_librnp.so
As a test, I removed libsequoia-octopus-librnp.
After doing so, Thunderbird successfully loads the standard RNP library,
reporting:
Status: Unofficial version. OpenPGP might not
work as expected.
Expected minimum version: 0.18.1
Version in use: 0.18.1-2+b1
Path: librnp.so.0
However, removing libsequoia-octopus-librnp is not a satisfactory
workaround for users who rely on its integration with GnuPG.
Sequoia Octopus makes keys managed by GnuPG available to Thunderbird,
including private keys accessed through gpg-agent. Removing it therefore
breaks the existing GnuPG-based OpenPGP workflow.
The test indicates that the initialisation failure is specific to the
Sequoia Octopus replacement library. A fix is needed that restores
compatibility with Thunderbird 153 while preserving the GnuPG
integration provided by Sequoia Octopus.
Best regards
Norbert
P.S. I would normally OpenPGP-sign messages to Debian mailing lists and
the BTS, but unfortunately this regression currently prevents me from
doing so.
