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 58485 - crashes if system time is way in the past
crashes if system time is way in the past
Status: RESOLVED DUPLICATE of bug 56111
Product: ORBit
Classification: Deprecated
Component: general
0.5
Other Linux
: Normal minor
: ---
Assigned To: Yanko Kaneti
Yanko Kaneti
Depends on:
Blocks:
 
 
Reported: 2001-08-03 08:17 UTC by jronne
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
bug buddy backtrace (2.52 KB, text/plain)
2001-08-03 19:02 UTC, jronne 		Details

Description jronne 2001-08-03 08:17:57 UTC 
Due to some other problems, my system clock got set to 1904.
I this state, galeon would crash every time I tried to run it.
When I finally realize the system time was messed up and fixed
it, Galeon behaved normally again.
Comment 1 Yanko Kaneti 2001-08-03 11:14:08 UTC 
ugh, i dont believe its possible to set the system date to something
before jan 1 1970, the unix time is counted from there on, in seconds

and you should provide a backtrace
Comment 2 jronne 2001-08-03 19:02:11 UTC 
Created attachment 842 [details]
bug buddy backtrace
Comment 3 jronne 2001-08-03 19:08:11 UTC 
I believe system time is an signed 32-bit number.  I believe the
largest negative number comes out to a date in 1904.

I've found that I'm only able to reproduce the failure when I boot
the system with an incorrect negative time.  Once it has been set
to the correct time, it doesn't seem to trigger anymore even if
I set it back to 1904.
Comment 4 Marco Pesenti Gritti 2001-08-03 22:39:17 UTC 
looks an Orbit problem, you may want to report it there
Comment 5 Elliot Lee 2001-09-11 04:48:00 UTC 

*** This bug has been marked as a duplicate of 56111 ***