On recently started processes, ksysguard claims they have been launched -1 day and some hours ago. Hovering over the entry in the relative start time column reveals that it believes it has been started one hour in the future (possibly due to timezone or DST), and then makes a bogus calculation.

Reproducible: Always




# hwclock
2016-07-01 16:32:37.140183+1:00

# hwclock -c
hw-time      system-time         freq-offset-ppm   tick                                      
1467383595   1467383595.038249                                                               
1467383605   1467383605.038727                48      0
^C

$ locale                                                                 
LANG=en_GB.UTF-8                                                                             
LC_CTYPE="en_GB.UTF-8"
LC_NUMERIC="en_GB.UTF-8"
LC_TIME="en_GB.UTF-8"
LC_COLLATE="en_GB.UTF-8"
LC_MONETARY="en_GB.UTF-8"
LC_MESSAGES="en_GB.UTF-8"
LC_PAPER="en_GB.UTF-8"
LC_NAME="en_GB.UTF-8"
LC_ADDRESS="en_GB.UTF-8"
LC_TELEPHONE="en_GB.UTF-8"
LC_MEASUREMENT="en_GB.UTF-8"
LC_IDENTIFICATION="en_GB.UTF-8"
LC_ALL=

$ timedatectl
      Local time: Fri 2016-07-01 16:34:23 CEST
  Universal time: Fri 2016-07-01 14:34:23 UTC
        RTC time: Fri 2016-07-01 14:34:23
       Time zone: Europe/Zurich (CEST, +0200)
 Network time on: yes
NTP synchronized: yes
 RTC in local TZ: no

The output of ps -o start_time is actually the correct start time.