On Sun, Feb 25, 2007 at 09:53:32PM +0100, Brice Goglin wrote: > > There's probably another problem apart from X freezing when the time is > changed. Maybe the system clock is not stored correctly in the hardware > clock before shutdown. I remember having problems like this on a core > duo processor because hwclock needed the --directisa command line option. > > You could try without a X server at all, check the time from a virtual > text console, change it, shutdown, restart and see what time you get. > Anyway, that would be a bug in another package. > > Brice > I was able to change the time using the date-command. This worked from within KDE using a text console as well as in single-user-mode without a X server running using the virtual console.
The new time was stored in the hw clock in both cases and displayed when using '$ date' after restarting the laptop. The time displayed using '$ date' was still one hour behind the time displayed by the KDE clock. To look after the one hour difference between the two clock-displays I used '# tzconfig'. It said "Your current time zone is set to Unknown Do you want to change that? [n]: y ... Your default time zone is set to 'Europe/Berlin'. Local time is now: Mo 26. Feb 10:48:17 CET 2007. Universal Time is now: Mo 26. Feb 09:48:17 UTC 2007.". After that the time show in the 'Adjust Date & Time...'-dialogue was the same as the time show in the KDE clock. When I then open the 'Adjust Date & Time...'-dialogue again and change the time, clicking OK still makes the screen dark and freezes the system. Ralph -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
