Bug 315989 - ktimezoned doesn't watch for /etc/localtime changes if the file didn't exist at startup time
Summary: ktimezoned doesn't watch for /etc/localtime changes if the file didn't exist ...
Status: RESOLVED FIXED
Alias: None
Product: kdelibs
Classification: Unmaintained
Component: kded (show other bugs)
Version: 4.10.0
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Kevin Kofler
URL: https://bugzilla.redhat.com/show_bug....
Keywords:
Depends on:
Blocks:
 
Reported: 2013-03-01 23:07 UTC by Kevin Kofler
Modified: 2013-03-01 23:08 UTC (History)
0 users

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Kevin Kofler 2013-03-01 23:07:31 UTC 
This bug is fixed in 4.10.1, I'm filing it so it shows up in the list of fixed bugs.

ktimezoned would only watch for changes to /etc/localtime if the file already existed. So if the file was not there and it gets created, nothing would happen.

Reproducible: Always

Steps to Reproduce:
On a Fedora 18 installation with the fix for bug #315987 applied:
1. Visit System Settings->System Administration->Date & Time
2. Click on the Time Zone tab
3. Select a time zone different from the default (UTC) and hit Apply.
Actual Results:  
The time zone jumps back to UTC, and closing the dialog asks whether to apply the changes (resetting the time zone to UTC) or discard the (bogus) changes.

Expected Results:  
kcm_clock notices the changed time.

See:
https://bugzilla.redhat.com/show_bug.cgi?id=906972
https://git.reviewboard.kde.org/r/108727/

Fixed in 4.10.1 by:
http://commits.kde.org/kde-runtime/7a42d977c90a5f0f387d170745e8a7b01f7d9675