Comment 4 for bug 1271484

The 13.10 fix in lp:~charlesk/indicator-datetime/13.10-lp-1271484 is also part of that cpp MR for trunk and seb128 and I are both seeing that branch work on the Desktop.

There's a separate issue on the phone, though. For some reason the GFileMonitor that's watching /etc/timezone isn't emitting any 'changed' signals when /etc/timezone changes. Interestingly, it seems to be something about /etc/timezone itself.

For comparison, here's indicator-datetime running on the phone. In this run I've changed the compile-time flags to watch /tmp/tz instead and am editing that file inside of vi to switch between London and Chicago:

Indicator-Datetime-Message: timezone-file.cpp:32 ctor /tmp/tz
Indicator-Datetime-Message: timezone-file.cpp:62 setFilename(/tmp/tz)
Indicator-Datetime-Message: timezone-file.cpp:70 0x422045b8 is now monitoring /tmp/tz
Indicator-Datetime-Message: timezone-file.cpp:80 Monitoring timezone file '/tmp/tz', id is 2
Indicator-Datetime-Message: timezone-file.cpp:81 refcount is 1
Indicator-Datetime-Message: timezone-file.cpp:84 setFilename(/tmp/tz) calling reload now
Indicator-Datetime-Message: timezone-file.cpp:100 void unity::indicator::datetime::FileTimezone::reload()
Indicator-Datetime-Message: timezone-file.cpp:110 void unity::indicator::datetime::FileTimezone::reload() Europe/London
Indicator-Datetime-Message: timezone-file.cpp:91 FILE CHANGED!!
Indicator-Datetime-Message: timezone-file.cpp:100 void unity::indicator::datetime::FileTimezone::reload()
Indicator-Datetime-Message: timezone-file.cpp:110 void unity::indicator::datetime::FileTimezone::reload() America/Chicago
Indicator-Datetime-Message: timezone-file.cpp:91 FILE CHANGED!!
Indicator-Datetime-Message: timezone-file.cpp:100 void unity::indicator::datetime::FileTimezone::reload()
Indicator-Datetime-Message: timezone-file.cpp:110 void unity::indicator::datetime::FileTimezone::reload() Europe/London

Here's the same test and setup, using the standard /etc/timezone and swapping that one back and forth between London and Chicago. GFileMonitor doesn't emit any 'changed' signals in this setup:

Indicator-Datetime-Message: timezone-file.cpp:32 ctor /etc/timezone
Indicator-Datetime-Message: timezone-file.cpp:62 setFilename(/etc/timezone)
Indicator-Datetime-Message: timezone-file.cpp:70 0x422045b8 is now monitoring /etc/timezone
Indicator-Datetime-Message: timezone-file.cpp:80 Monitoring timezone file '/etc/timezone', id is 2
Indicator-Datetime-Message: timezone-file.cpp:81 refcount is 1
Indicator-Datetime-Message: timezone-file.cpp:84 setFilename(/etc/timezone) calling reload now
Indicator-Datetime-Message: timezone-file.cpp:100 void unity::indicator::datetime::FileTimezone::reload()
Indicator-Datetime-Message: timezone-file.cpp:110 void unity::indicator::datetime::FileTimezone::reload() Europe/London

Also, the automatic unit tests which use a local temporary file instead of /etc/timezone also work.