Bug 351008 - Automatic change of Timezone based on location
Summary: Automatic change of Timezone based on location
Status: RESOLVED INTENTIONAL
Alias: None
Product: plasmashell
Classification: Plasma
Component: Digital Clock widget (show other bugs)
Version: 5.3.2
Platform: Fedora RPMs Linux
: NOR wishlist
Target Milestone: 1.0
Assignee: Martin Klapetek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-08-05 19:03 UTC by Peter Tselios
Modified: 2018-01-02 21:41 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Tselios 2015-08-05 19:03:08 UTC
I travel a lot and I need to modify the timezone of my laptop. It would be really nice to have Plasmashell to detect the location (during startup?) and modify the timezone accordingly. 
Ideally, the clock should change automatically to a predefined TZ or to prompt user in order to change to the correct one. 
Obviously, a check box should enable/disable that. 

Reproducible: Always



Expected Results:  
TZ should be automatically adjusted. 

I am very willing to test this functionality as long as you can provide me with the necessary rpms :)
Comment 1 Martin Klapetek 2015-08-05 19:05:26 UTC
Thanks for the report

This is quite some long standing wish as I understand. I totally agree that it would be nice to have something like that, it can even be based on geoip stuff.

I wonder if systemd has anything like that? I mean...it has everything.
Comment 2 Peter Tselios 2015-08-05 19:15:37 UTC
Why mess with systemd? GeoIP is enough for that! freegeoip.net has all the necessary info! I  have almost lost my C programming skills, otherwise, I would go a grab the code and help the developers. But I would do more harm than good. 
Android gets time data from GSM networks. We, on the other hand, we have the Internet!
Comment 3 Martin Klapetek 2015-08-05 19:19:45 UTC
> Why mess with systemd? 

Because systemd handles timezones these days. At least on systems where systemd is supported and the list of these systems is getting bigger and bigger.

So it would make sense if systemd would already have such feature.
Comment 4 Peter Tselios 2015-08-12 15:55:17 UTC
I will start to hate systemd. Why do they mess with timezones? It's not their job to do so... Isn't there any option to bypass that?
Comment 5 David Edmundson 2015-08-12 15:56:56 UTC
It is the repsonsibility of timedated to mess with timezones, that's what it does.

There will be no option.
Comment 6 Peter Tselios 2015-08-12 16:05:52 UTC
(In reply to Peter Tselios from comment #4)
> I will start to hate systemd. Why do they mess with timezones? It's not
> their job to do so... Isn't there any option to bypass that?

Also, even if systemd is responsible for timezone, that is the kernel only, right? We talk about a multiuser OS, let's not forget that. It might be possible to share a laptop (stand-by laptops for example). A person my not have configured a second timezone in KDE. So, how would systemd get involved in that? 

The more I think about it, the more I am convinced that this is a KDE related thing.
Comment 7 David Edmundson 2015-08-12 16:07:56 UTC
if it's a laptop, and you're in one timezone, then the other person is presumably also in that timezone.
Comment 8 Peter Tselios 2015-08-14 08:32:52 UTC
People travel. So they can be in different timezones.
Comment 9 Peter Tselios 2015-08-19 09:48:33 UTC
I will just demo a case of different timezones.

Support laptop uses Fedora 22 and is common to all Linux sysadmins of the company.
Customer A is located in the UK and uses BST.
Company's home offices are located in Germany.
Sysadmin 1 travels inside Germany
Sysadmin 2 travels to UK.
Sysadmin 3 travels to eastern Europe.
Sysadmin 4 travels to Nordic countries

So, at least 3-4 different timezones for one laptop.
Comment 10 David Edmundson 2015-08-19 09:50:23 UTC
Not arguing that. 

What I was aruging is that user 1 can't be using it in the UK, whilst user 2 is also using it in Germany.
Comment 11 Peter Tselios 2017-11-27 21:11:51 UTC
I would like to reopen the bug because I think it is a very useful feature for people that travel a lot. 

So, let's start from scratch. 
system-timesyncd is used in order to sync the local **clock**. Local clocks should be in UTC (as all distros advice uses to set the clocks to UTC) and Timezones should be handled by the shells/Desktop Environments. 

Other DE already have this implemented and I would just love to have this in KDE as well.
Comment 12 David Edmundson 2017-11-27 21:41:42 UTC
> Other DE already have this implemented

Which one(s)?
Comment 13 Peter Tselios 2017-12-19 21:29:47 UTC
In Gnome 3 it's already there and enabled by default, even in RHEL (not just Fedora). 
Also, in the latest update of KDE in my Fedora 26 I noticed that there  geolocation libraries (plasma-workspace-geolocation & plasma-workspace-geolocation-libs).
I suspect that all the necessary bits are in place.
I really hope that you will implement it :) I wished I could help, but unfortunately, I am out of coding years know :(
Comment 14 Christoph Feck 2018-01-02 21:41:43 UTC
> In Gnome 3

Are you sure it isn't implemented in some lower libraries/daemons/services? If the timezone changes, there needs to be a signal (DBus etc.) from whatever service watches your geolocation.

It cannot be implemented in Plasma, because then the timezone that Plasma thinks you are in would be different to the timezone your system thinks you are in.