Clock applet problem, unable to connect to ntp servers

[Hveem]

It is not possible for kcmshell4 clock to set the correct time, and connect to a NTP server to get the correct time.

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: kde-runtime 4:4.10.2-0ubuntu3
ProcVersionSignature: Ubuntu 3.2.0-35.55-generic 3.2.34
Uname: Linux 3.2.0-35-generic i686
ApportVersion: 2.9.2-0ubuntu8
Architecture: i386
Date: Fri May 3 12:48:22 2013
ExecutablePath: /usr/bin/kcmshell4
InstallationDate: Installed on 2011-12-16 (504 days ago)
InstallationMedia: Kubuntu 11.04 "Natty Narwhal" - Release i386 (20110427)
MarkForUpload: True
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: kde-runtime
UpgradeStatus: Upgraded to raring on 2013-04-27 (5 days ago)
---
ApportVersion: 2.9.2-0ubuntu8
Architecture: i386
DistroRelease: Ubuntu 13.04
InstallationDate: Installed on 2011-12-16 (504 days ago)
InstallationMedia: Kubuntu 11.04 "Natty Narwhal" - Release i386 (20110427)
MarkForUpload: True
Package: kde-runtime 4:4.10.2-0ubuntu3
PackageArchitecture: i386
ProcVersionSignature: Ubuntu 3.2.0-35.55-generic 3.2.34
Tags: raring
Uname: Linux 3.2.0-35-generic i686
UpgradeStatus: Upgraded to raring on 2013-04-27 (5 days ago)
UserGroups: adm admin audio cdrom dialout fuse kismet lpadmin plugdev sambashare

[Hveem (krbjhvee)]

run from prompt :kcmshell4 clock
false
X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 20 (X_GetProperty)
  Resource id: 0x20000c3
X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 20 (X_GetProperty)
  Resource id: 0x20000d4
X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 20 (X_GetProperty)
  Resource id: 0x20000fb

[Hveem (krbjhvee)]

apport information

[Hveem (krbjhvee)]

apport information

[Harald Sitter (apachelogger)]

Hi there!

Thanks for reporting this bug! Your bug seems to be a problem with the KDE program itself, and not with our KDE packages. While we appreciate your issue, it would be better if it was tracked at https://bugs.kde.org, so that the KDE developers can deal with this speedily and have direct communication with you as the reporter for more effective debugging.

Thanks!