Also using Kubuntu 8.04 and KDE 4.1.00
Same behavior.

Thanks for your report. Regrettably I cannot reproduce the crash. Can have a look at http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and try to install the debugging packages for your distribution and post a backtrace for the crash?

I have obtained details that I think are more helpful than what gdb could produce.

The System Monitor sorted by PID shows the following activites:
*When a new date is applied kdesu runs and asks for a password.
*Then kcmdatetimehelp runs as root with this command:
** /usr/lib/kde4/lib/kde4/libexec/kcmdatetimehelper ntp 5 Public Time Server (pool.ntp.org) asia.pool.ntp.org europe.pool.ntp.org north-america.pool.ntp.org oceania.pool.ntp.org disabled date 081500172008.15 tz America/Denver
*Then, date runs as root and becomes a zombie instantly.

If kcmdatetimehelp is killed, the Date & Time settings unfreezes and responds normally until another date change is applied.


#Command to get backtrace
****$ gdb systemsettings ****
****(gdb) run --nofork   ****
findServiceByDesktopPath:  not found
systemsettings(12130) MainWindow::selectionChanged: Selected item:  "Date & Time"
systemsettings(12130) MainWindow::selectionChanged: Comment:        "Date and time settings"
systemsettings(12130) Dtime::findNTPutility: ntpUtility =  "ntpdate"
systemsettings(12130) MainWindow::selectionChanged: Selected item:  "Date & Time"
systemsettings(12130) MainWindow::selectionChanged: Comment:        "Date and time settings"
systemsettings(12130) MainWindow::selectionChanged: Selected item:  "Date & Time"
systemsettings(12130) MainWindow::selectionChanged: Comment:        "Date and time settings"
systemsettings(12130) MainWindow::selectionChanged: Selected item:  "Date & Time"
systemsettings(12130) MainWindow::selectionChanged: Comment:        "Date and time settings"
systemsettings(12130) Dtime::save: Set date  "081500032008.31"
[New Thread 0xb47a4b90 (LWP 12133)]
Fri Aug 15 00:03:31 CDT 2008
** No more output before or after systemsettings is killed**

(In reply to comment #0)
> Version:           4.1.00 (using KDE 4.1.0)
> Installed from:    Ubuntu Packages
> Compiler:           Used kubuntu Kde4.1 Packages
> OS:                Linux
> 
> A repeatable crash occurs when adjusting 'Date & Time' in 'System Settings'.
> 
> What happens: System Settings Crashes
> 
> *Open 'System Settings'
> *Click on 'Date & Time'
> *Change any setting
> *Click 'Apply'
> *Type in password and press 'OK'
> *Crash occurs and 'System Settings' does not respond and must be killed
> *Some changes in settings are applied
> 
> What's expected to happen: System Settings should not crash.
> 
> Using Kubuntu 8.04 with KDE 4.1
> 

When clicking of "Set date and time automatically", then apply, the app freezes. Part of output:

systemsettings(9502) MainWindow::selectionChanged: Selected item:  "Date & Time"
systemsettings(9502) MainWindow::selectionChanged: Comment:        "Date and time settings"
systemsettings(9502) MainWindow::selectionChanged: Needs root privs: false
systemsettings(9502) Dtime::findNTPutility: ntpUtility =  "ntpdate"
systemsettings(9502) Dtime::save: Setting date from time server  "Public Time Server (pool.ntp.org)"

 4 Sep 20:59:19 ntpdate[9513]: adjust time server 18.103.0.198 offset -0.001321 sec

Then nothing - everything just hangs...

I have reproduced the crash in KDE 4.1.1. When open time and date in systems settings, and I click on the automatic update tab, the program freezes. Nothing else wrong as far as I can see. Internet connection fine.

Let me know what to do to test futher

Running KDE 4.1.1 on  Toshiba notebook Intel Duo 

Here (KDE 4.1.3 on ArchLinux x86_64) : I can't reproduce this freeze/crash. Can you still reproduce it with a recent KDE version? (4.1.3 / 4.2beta1 / 4.2svn)

I just tried it again, and cannot reproduce the original problem. Seems to be working now. (Kubuntu 4.1.3)

Yes, I agree. In Kubuntu 4.1.3 it works now.

If anyone can't reproduce this bug again with updated KDE versions, this bug can be marked as resolved with a WORKSFORME resolution. And If anyone experiences it again later, the bug report can be re-opened. Thanks :)

closing as people seeing it valid with kde 4.1.1 on Kubuntu can't reproduce it now.

Please reopen this bug if it appears again