[Users] PGP key selection issue

[Norwid Behrnd]

PGP key selection issue

Dear users,

I'm unsure if I broke CM's PGP management -- can one of you please check if
this pattern equally is seen on her/his installation?

Running a Linux Debian 12/bookworm (branch testing), I run a dist upgrade by
`sudo apt-get dist-upgrade`.  By this, CM 4.1.1 (by 20th October 2022; Debian's
package 4.1.1-2+1); and plugins PGP/Core, PGP/inline, PGP/MIME 4.1.1 are the
most recent available from this source.  Again from Debian's repositories is an
installation of Kleopatra version 3.1.22.220803 (22.08.3) which uses GnuPG
(version 2.2.40) and Libgcrypt 1.10.1.

For normal sign and encryption of files, I use "key A"; it equally is known and
used by CM via "Specify key manually" and its key ID.  A couple of days ago, I
had to sign a file with a new, separate "key B".  Both are keys only belong to
me, are set up and managed by Kleopatra, and of same type RSA.  By Kleopatra's
display, both keys' validation did not expired yet.  The key ID of "key B"
never was added to CM's "Specify key manually" either on this, nor an other
email account.  I don't want to use "key B" to sign/encrypt emails.

Then

* for purpose of testing, I sign an email sent to myself (text only, without an
  attachment).  As anticipated, and in line with earlier experience, CM picks
  the elder "key A" CM uses.

* for purpose of testing I sign and encrypt an email sent to myself.  This
  time, CM picks "key B", and I have to use passphrase B (instead of
  passphrase A) to decrypt the received message (again, text only, no
  attachment).

Can someone replicate this observation?  What is the reasoning for CM to pick 
once the key I wanted/set up as default and the other time an other key
instead?

With regards,

Norwid