Review Request 125029: Monitor timezone changing from timedated rather than our clock KCM

[Martin Klapetek]

> On Sept. 2, 2015, 4:35 p.m., Martin Klapetek wrote:
> > But the ktimezoned should do exactly that; it monitors various files which timedate modifies and then sends that signal. Does ktimezoned not work in that case (it did when I last test it)? I think better place for this signal watcher would be in ktimezoned itself actually.

Edit: timedatectl set-timezone Europe/Prague changes my clock immediatelly, so does "echo "Europe/Prague" > /etc/timezone


- Martin


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/125029/#review84766
-----------------------------------------------------------


On Sept. 2, 2015, 12:33 p.m., David Edmundson wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://git.reviewboard.kde.org/r/125029/
> -----------------------------------------------------------
> 
> (Updated Sept. 2, 2015, 12:33 p.m.)
> 
> 
> Review request for Plasma.
> 
> 
> Repository: plasma-workspace
> 
> 
> Description
> -------
> 
> This means we get update the UI immedidately if the timezone is changed
> from an external source, such as timedatectl or some user script based
> on location for example.
> 
> This patch would put more of a dependency on timedated..unless we
> monitor both?
> 
> CCBUG: 351008
> 
> 
> Diffs
> -----
> 
>   dataengines/time/timeengine.cpp 2fd9792209ff5e78bd3dee1ed938eb0b1173de8d 
> 
> Diff: https://git.reviewboard.kde.org/r/125029/diff/
> 
> 
> Testing
> -------
> 
> 
> Thanks,
> 
> David Edmundson
> 
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/plasma-devel/attachments/20150902/2b492269/attachment.html>