Bug 325073

Summary: kcmshell4 clock
Product: [I don't know] kde Reporter: Thomas Sisson <thomas.sisson.1>
Component: generalAssignee: Unassigned bugs mailing-list <unassigned-bugs>
Status: RESOLVED DUPLICATE    
Severity: grave CC: cfeck
Priority: NOR    
Version: 4.10.5   
Target Milestone: ---   
Platform: Kubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Thomas Sisson 2013-09-18 20:13:27 UTC
This belongs under kcmshell4, but kcmshell4 does not show up in the list.

Something keeps resetting local time to UTC. I disabled ntpd (another unresolved bug), so I can set my time zone. The clock is still set to the time UTC is, but with my local time zone. These means that I am four hours out of sync.

This is an extreme issue in my mind because the clock does not show the correct time. Even if one knows the clock is wrong, one's mind tends to focus on the displayed time and forgets about it being wrong. It would be better to have no clock, but disabling or removing the clock is not a solution.

Additionally, I don't care if this has been fixed in a newer version because I am stuck with this version until I get an update from Ubuntu. This needs to be pushed downstream as a security update so that it gets updated for all.

Marking a bug as WORKSFORME is not viable in my mind. I don't care that it works for you any more than you don't care that it doesn't work for me. This way of marking a bug sounds arrogant and condescending.

Reproducible: Always

Steps to Reproduce:
1. Boot the computer.
2. Set the correct time.
3. Reboot the computer.
Actual Results:  
The time is wrong.

Expected Results:  
The time should ALWAYS be correct.
Comment 1 Christoph Feck 2013-09-18 21:54:57 UTC
Do you see the same bug when using a different distribution? From what I see at comments for similar bugs, it is a (K)Ubuntu-specific problem.
Comment 2 Christoph Feck 2013-09-18 22:09:35 UTC

*** This bug has been marked as a duplicate of bug 317999 ***