I'm not so sure if changing the qt libs _isn't_ the culprit...............what I mean is that lately it seems that there are more and more compile problems with kde and qt libs not being in sync.

I've been browsing around the kde site and the kde bugs site, and I'm starting to see a pattern emerge................mind you, this is only my impression and not to be taken as the absolute fact.........but it seems that whatever qt libs were used when compiling the kde packages, you need to stick with those libs............with the changes being made with both qt and kde, they seem to break a lot of stuff when using the wrong version qt libs than what that particular kde package was compiled with. For the most part, everything sems to work okay, but there are exceptions that crop up, like the clock problem...........

The only other alternative is to compile kde from source using the qt libs you currently have and see if that doesn't solve the problem.................the downside with that solution is that all the kde packages are not as simple as a lot of programs to compile......

Or you might want to upgrade to qt-3.2.3, if you're using kde 3.2, to see if that doesn't fix the clock problem............but then that will cause the well-known konsole font problem...........

I feel that the kde develpment team may need to work a lot closer with the trolltech's development of the qt libs in order to overcome some of the problems that are cropping up, or else review the code from contributors a lot closer...........just a thought

---thegeekster

Okay, thanks for your reply. You seem to have a good feel for how this software interacts (or doesn't).

It sounds like a messy situation. I will take no further action for now, since I can set the clock at the command line anyway.

As for whether qt_libs is the culprit, I will defer to your experience. However, Thom Nuz seemed to imply that installing qt-3.2.2 (and removing qt-3.2.3) fixed the problem. In my situation, at least, I have still have the problem with qt-3.2.2. I'm not sure how the process of installing qt-3.2.3 and then removing it might correct the problem, but perhaps it's possible.

BD

That really shouldn't make any difference, since when the libs are removed everything gets removed...........so replacing them with something else seems unlikely to resolve the problem....

But who knows, stranger things have been known to happen...........................for instance, I had the same clock problem, couldn't set it from the task bar after entering the root passwd (it would just crash).................but I just tried it again when reading your response and now it's working, The only thing I did was to revert back to using the linux-2.4.23 kernel instead of the 2.4.24 kernel.............LOL..........I still have quite a journey learning more Linux programming before I can begin to understand how to modify code to make things works as intedend (I only know enough at this time to get into more trouble ).........

Anyway, best of luck
---thegeekster

Curious indeed.

I just tried it on another computer with the following configuration:
Slackware 9.1
Linux 2.4.23
KDE 3.1.4
qt-3.2.1

As I mentioned before, the kclock was broken in KDE 3.1. However, I just tried it again and it worked! Then I recalled it had worked before the first time I'd set the clock and it had crashed on subsequent attempts upon entering the root password. Sure enough, the second time (and on subsequent attempts) it crashed with the message: "The application KDE Control Module (kcmshell) crashed and caused the signal 11 (SIGSEGV) ."

Maybe you will get the same result if you try again to set the time.

Good luck,
BD.

Still working after changing the time around......... *shrugs*

BTW, I never need to touch it anyway..............I have ntpd installed (the Network Time Protocol daemon) and set up a cron job that syncs the system and hardware time automatically twice a day, using this command in a shell script:

Thanks for the suggestion. It is probably the best approach to setting the time that I'm aware of. I understand you can also use this approach to sync your computers in a subnet where only one (acting as a master) needs to sync externally with NIST.

You've demonstrated that there's more than one way to accomplish the time setting. I guess I'm flagging the issue with KDE/qt_libs because it may be indicative of other, more serious incompatibilities. Also, if the intent of KDE is to provide a simple GUI that's user friendly, it shouldn't crash when attempting a seemingly straightforward operation on an "out-of-the box" distribution. I've had considerable experience with Slackware (though not with the GUI per se), so I've learned that there are other (and better) ways to set the clock. I'm not going to abandon Linux of Slackware because kclock doesn't work properly any longer. However, to a Slackware newbie the crashing kclock is much more disconcerting.

BD