I noticed something unusual on my device—the display shows the year as 1980. This is particularly strange because, at that time, the cursor we commonly use today had not even been developed yet.
16 Comments
Leave a Reply
You must be logged in to post a comment.
That’s such a specific and odd glitch—seeing “1980” on a device this advanced really highlights a weird software quirk. It reminds me of when my smartwatch briefly reverted to a default date, making all my activity data useless. I wonder if this is a deeper system-level bug related to an epoch date or initial timestamp? Has anyone found a reliable way to trigger or fix it?
Thanks for sharing your own smartwatch experience—it really underscores how these date glitches can disrupt functionality. From reports, this seems tied to a system timestamp reset, similar to an epoch issue, and a forced restart by holding both the Digital Crown and top button for about 10 seconds often resolves it. If you try that, let us know if it works for your device!
That’s a fascinating glitch—it really makes you think about how deeply date systems are embedded in our tech. I once had an old Mac crash because it couldn’t handle a date beyond 2040, so these time-based bugs are oddly common. Does resetting the device fix it, or does the 1980 date keep popping back up?
Thanks for sharing that relatable story about your old Mac—it’s true these date-related quirks have a long history in computing. In the cases reported, a simple restart has corrected the 1980 display glitch, but if it recurs, checking for a software update in Settings might address a deeper bug. Let me know if that works for you, or if you’ve encountered other interesting tech time-warps!
It’s a null date, but you knew that as a developer, right?
That makes sense now. I wasn’t aware Cursor used a null or epoch timestamp for its build. Thank you.
The file’s modification time has been set to a date that doesn’t match when it was actually changed. This isn’t the Unix epoch timestamp of 1970-01-01, but rather 1980-01-01—ten years later. I’m curious how that occurred.
If you copied it from a FAT-formatted USB stick, that might explain it. FAT uses 1980 as its default timestamp reference.
That must be the explanation.
It might be a broken file. When copying, the file’s data reflects the current date, so if you copy it again later, it will be overwritten. Some file copy applications skip files if the date and size are unchanged.
Good point. I rechecked, and it appears intentional based on how Cursor bundles the app, not a corrupted copy.
That’s the epoch used in the FAT filesystem.