Comment 1 for bug 395027

I can confirm this.

tangogps-0.9.3-2--i386

ccurley@dragon:~/Maps$ cat 20090730_203638.log
43.644043,-108.214592,1347.0,0.0,219.0,4.4,2009-07-31T08:36:36Z
43.644048,-108.214592,1347.0,0.1,-316.3,4.4,2009-07-31T08:36:37Z
43.644052,-108.214592,1347.1,0.1,-323.2,4.4,2009-07-31T08:36:39Z
43.644050,-108.214595,1347.3,0.1,-326.6,4.4,2009-07-31T08:36:40Z
43.644052,-108.214597,1347.4,0.3,5.5,4.4,2009-07-31T08:36:41Z
43.644058,-108.214597,1347.5,0.7,18.6,4.4,2009-07-31T08:36:42Z
ccurley@dragon:~/Maps$ ll 20090730_203638.log
-rw-r--r-- 1 ccurley ccurley 384 2009-07-30 20:36 20090730_203638.log
ccurley@dragon:~/Maps$ date
Thu Jul 30 20:41:05 MDT 2009
ccurley@dragon:~/Maps$ date -u
Fri Jul 31 02:41:48 UTC 2009
ccurley@dragon:~/Maps$

If Tangogps is trying to log UTC (which would be preferable to local time), it's failing at that. Note that the times in the file are well after the time I examined it, even correcting for UTC.

xgps (a gpsd client, package gpsd-clients-2.38-1ubuntu3--i386) reports the time correctly.