Theme name: oxygen-gtk Kernel version = 3.8.13.4-desktop-1.mga3 Distribution=Mageia release 3 (Official) for x86_64 CPU=Pentium(R) Dual-Core CPU E5800 @ 3.20GHz I am unable to set the clock to the correct time here in Israel. I have tried to do this as root but it freezes or the window wants to close. I have even removed the tick from the set Enable Network Time Protocol.
(In reply to moshe brace from comment #0) > Theme name: oxygen-gtk > Kernel version = 3.8.13.4-desktop-1.mga3 > Distribution=Mageia release 3 (Official) for x86_64 > CPU=Pentium(R) Dual-Core CPU E5800 @ 3.20GHz > > I am unable to set the clock to the correct time here in Israel. I have > tried to do this as root but it freezes or the window wants to close. I have > even removed the tick from the set Enable Network Time Protocol. Can you try wether you have the same problem in one or more other Desktop environments? In LXDE I can switch timezone without problem, but in KDE it doesn't always work well atm, and the analog clock widget doesn't follow the change at all, not even after logging out and back in (didn't try reboot)
CC: (none) => marja11
Found out why I couldn't get hwclock to work: it needs to be run as root :-[ Anyway, in KDE, when the taskbar clock doesn't follow the changed timezone, hwclock shows it has been set correctly. So, for me, the problem isn't in drakclock, but in KDE @ mikala, neoclust Sorry, don't know which KDE package to assign this bug to, so I may have assigned to the wrong maintainer @ Moshe you are using KDE too, aren't you? If not, I'll clone this report for the problem in KDE and we'll keep this one for your bug.
CC: (none) => balcaen.johnSource RPM: drakxtools-15.54.1-2.mga3 => (none)
again trying to assign
Assignee: bugsquad => nicolas.lecureuil
Reported again against Cauldron, still not fixed. Drakclock issue. Closing this old one since Mageia 3 is EOL. Newer report has more info. *** This bug has been marked as a duplicate of bug 15534 ***
Status: NEW => RESOLVEDResolution: (none) => DUPLICATE
Turns out this one's drakclock and the other one's kcm_clock, so different issues. Closing as OLD, but this could be reopened if it's still valid (probably is) and isn't a duplicate of another bug (probably is).
Resolution: DUPLICATE => OLD
Have you tried manaclock? it should work for that as user by using dbus, it will not though for ntp iirc.
CC: (none) => anaselli
ah it's closed :)