kmail / openpgp expire warning wrong

Version: 1.6.52 (using KDE 3.2.90 (3.3 alpha1, CVS >= 20040522), compiled sources)
Compiler: gcc version 3.2.3
OS: Linux (i686) release 2.4.22

Trying to send a mail which shall be signed pops up a dialog:

Your OpenPGP signing key
Martin Koller (KeyID 0x8DFB0F86)
expires in less than 4294954719 days.

Well, yes ... and ? ;-)

(The key has unlimited expiration)

Created attachment 6645
a snapshot of the error window

look here for an example.

*** Bug 85787 has been marked as a duplicate of this bug. ***

Note: in my case (bug 85787) I got this error although the message has *NOT* been signed.

Got the same error in 3.2.92

Can s/o of you please attach a gdb to and say something like:

gdb> break 'GpgME::Key::neverExpires()'
<let it hit the breakpoint>
gdb> print *theGpgMEKeyObject.d->key

Thanks.

As I have already upgraded to latest CVS, and also updated all the crypto stuff kmail uses, I can no longer reproduce this.

Me neither. I'm not even on the latest CVS but on 3.3.0 with all the crypto dependencies updated, it's not happening anymore.

I have seen it in a beta 3.3 as well, but not in the official 3.3. Lets close until someone reports it again.

Ok, lets report it again:

I just saw a message saying that my key expires in less than 4294967294 days while sending a message.
I did NOT sign it and the key expired 4 days ago.
I'm using KDE 3.3.2.

Reopening then - can you try the gdb session suggested by Marc?

Ok, I tried but I'm not quite expirienced with gdb.
I tried to break on GpgME::Key::neverExpires() and on GpgME::Key::isExpired() (because in my case the key is already expired), but I'm afraid gdb did not stop when I sent the message (and got again the message, that my key expires in 4......... days).

This might be a silly question but might it be a problem that gdb says:
(gdb) break 'GpgME::Key::isExpired()'
Function "GpgME::Key::isExpired()" not defined.
Make breakpoint pending on future shared library load? (y or [n]) y
Breakpoint 1 ('GpgME::Key::isExpired()') pending.

Are there any special flags i have to compile gpgme or kdepim with?
fyi: I am using gpgme-1.0.2

> (gdb) break 'GpgME::Key::isExpired()'

Try
break 'GpgME::Key::isExpired(
and then press <tab> to complete it.

Make sure to start kmail first [in gdb], set the breakpoint only after interrupting kmail with Ctrl+C in gdb.

Ok, no it hit the breakpoint, but the symbol Marc mentioned was not found.
This might be a special case for keys that never expire. For which symbol shall I look?

(gdb) print *theGpgMEKeyObject.d->key
No symbol "theGpgMEKeyObject" in current context.

This bug is also valid for me in kde-3.4.

*** Bug 109059 has been marked as a duplicate of this bug. ***

This bug still exists in kmail/1.9.7 (kontact/1.2.5) with KDE 3.5.7.
A key that expired 5 days ago, will expire in less than 4294967293 days according to the dialog

Created attachment 22848
KMail 1.9.5 compiled for x86-64 Debian ‘Etch‘

same here for kmail "Version 1.9.6 (enterprise 0.20070907.709405)" on Kubuntu 7.10-x86 with kde 3.5.8. Expired 3days ago and shows 4294967294.

Tested with a certificate expired two days ago. It says that the key is expiring in less than -2 Days...

So Kmail threats expired certificates as an expiring one.
(bug triage day 09 november 2008), opensourcecat.

Thank you for taking the time to file a bug report.

KMail2 was released in 2011, and the entire code base went through significant changes. We are currently in the process of porting to Qt5 and KF5. It is unlikely that these bugs are still valid in KMail2.

We welcome you to try out KMail 2 with the KDE 4.14 release and give your feedback.