On Wed, Sep 09, 2026 at 11:00:51AM -0400, Noah Meyerhans wrote: > Control: tags -1 + unreproducible > > On Wed, Sep 09, 2026 at 04:00:55PM +0200, Joerg Dorchain wrote: > > > > following test, I noticed the following error while doing an > > > > apt-get upgrade > > > > > > > > [...] > > > > Preparing to unpack .../03-dovecot-sieve_1%3a2.4.5+dfsg1-2_amd64.deb ... > > > > Unpacking dovecot-sieve (1:2.4.5+dfsg1-2) over (1:2.4.4+dfsg1-2) ... > > > > Preparing to unpack .../04-dovecot-imapd_1%3a2.4.5+dfsg1-2_amd64.deb ... > > > > doveconf: Error: Couldn't load plugin > > > > /usr/lib/dovecot/modules/settings/libpigeonhole_settings.so: dlopen() > > > > failed: > > > > /usr/lib/dovecot/libdovecot-sieve.so.0: undefined symbol: t_openat_safe > > > > [...] > > > > > > I don't get this warning when performing the same upgrade tasks, and I > > > suspect that it's related somehow to your local configuration. > > > > > > Can you post the output of `doveconf -n`? > > > > Here you are: > > # doveconf -n > > <snip> > > Interesting. I'm still unable to reproduce this. What's the complete > set of dovecot-* binary packages that you have installed? Have you > encountered any instances of this error after completion of the upgrade? # dpkg-query -W|grep dovecot dovecot-core 1:2.4.5+dfsg1-2 dovecot-imapd 1:2.4.5+dfsg1-2 dovecot-sieve 1:2.4.5+dfsg1-2
I have only seen this once during the upgrade. If I have to guess wildly, I would assume a race condition between the installation of old and new dovecot-core and dovecot-sieve. I would have to deep dive into the symbols in the different versions and which script is run when and how to confirm. As the installation works for me(tm) despite of the message during upgrade, I do not see a need to raise severity. > > Upgrading from 1:2.4.4+dfsg1-2 to 1:2.4.5+dfsg1-2 looks like this for > me: [...] FTR I used apt-get upgrade (not apt). Best regards, Joerg
signature.asc
Description: PGP signature
