Daily timers next activated in on 2033-05-08

[aplund]

I have tried playing around with this for a while and cannot seem to find what is going on:

$this->bbcode_second_pass_code('', '# systemctl list-timers | grep man-db.timer
Mon 2033-05-09 00:00:00 AEST 18 years 2 months left Sun 2033-05-08 10:01:14 AEST 18 years 2 months left man-db.timer man-db.service
')

I've tried restarting the timer and it just ends up in exactly the same state. I'm using the bog standard .timer file

$this->bbcode_second_pass_code('', '# systemctl status man-db.timer
● man-db.timer - Daily man-db cache update
Loaded: loaded (/usr/lib/systemd/system/man-db.timer; static; vendor preset: disabled)
Active: active (waiting) since Tue 2015-03-03 12:13:43 AEST; 4min 56s ago
')

$this->bbcode_second_pass_code('', '# cat /usr/lib/systemd/system/man-db.timer
[Unit]
Description=Daily man-db cache update

[Timer]
OnCalendar=daily
AccuracySec=12h
Persistent=true
')

Exactly the same thing for shadow.timer and updatedb.timer. I have a number of custom timers which all work fine.

$this->bbcode_second_pass_code('', '# pacman -Qi systemd | grep Version
Version : 218-2
')

Is this some obscure systemd feature?