After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 592532 - Seahorse is not fully Y2k38 compliant
Seahorse is not fully Y2k38 compliant
Status: RESOLVED DUPLICATE of bug 516787
Product: seahorse
Classification: Applications
Component: general
2.27.x
Other Linux
: Normal normal
: 2.26.0
Assigned To: Seahorse Maintainer
Seahorse Maintainer
Depends on:
Blocks:
 
 
Reported: 2009-08-20 23:48 UTC by Andreas Moog
Modified: 2009-08-21 02:19 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Andreas Moog 2009-08-20 23:48:11 UTC 
(Partially forwarded from http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=463690)

My key has its expiration date set to 2080-31-12. This is correctly 
displayed by gpg, and on the calendar icon next to "Expires:" on the 
key's properties on Seahorse, but as 1944-11-25 on the field, in the 
same window.

--

Additionally, it is impossible to set an expiry date over 2038 via the user interface, giving the (obviously wrong) error "The expiry date must be in the future".
Comment 1 Adam Schreiber 2009-08-21 02:06:33 UTC 

*** This bug has been marked as a duplicate of bug 516787 ***
Comment 2 Andreas Moog 2009-08-21 02:11:46 UTC 
Hmm, ok. What about the part with being unable to set a expiration date later than 2038?
Comment 3 Adam Schreiber 2009-08-21 02:19:06 UTC 
That's from the same thing.  There's overflow to 1944 if they try to set 2080, because when we try to get the time from the widget it appears to be in the past.