Comment 17 for bug 365065

Binary package hint: gnucash

When I move my laptop eg from Sydney to London timezone, gnucash behaves poorly.

The user model is that transactions are done on a particular day; for example I pay my rent on the first day of each month. When creating a transaction in the ledger or through a recurring transaction, one can only choose a date for it to occur, not a time, and I doubt that tracking the time would be very useful.

However, it looks like gnucash internally stores the transaction as a timestamp, and displays them in the local time. So after moving to London, the rent payments appear to have been done on the last day of the previous month, and if I enter transactions in London they'll appear against the wrong day when I return home.

As a workaround you can set TZ before running gnucash.

There's some discussion of it here:

http://<email address hidden>/msg03494.html