Comment 1 for bug 1199142

I need some information before confirming this bug. First did you set Brighton, UK as your current location by searching and adding it from the world clock list? By default, the clock app shows UTC time. I just tried adding Brighton, UK from the world clock list and it reports the correct time. I get positive results for Lyon, Shoreham and Firenze as well.

If they are off by few minutes, that is something that I anticipated before hand. Currently when you add a world clock, the time is fetched from using an online API and the time difference between that location and your current location is calculated and saved. This is then used to show times. This could result in it being off by few minutes sometimes.

The correct technical way of doing stuff is by using the timezone ID which for Brighton is Europe/London and the time should be displayed based on this. However at the moment Qt 5.0 does not have proper support for Timezones and hence does not use tzdata. Until this is resolved upstream there is nothing much I can do. If there is a better solution, feel free to explain and I can see if that can be implemented.