My system was running relatively well until last night. I tried accessing some streaming video content (no, not that kind...). The end result is that mplayer-plugin freaked out and froze the whole system...I had to do a hard reboot. ReiserFS seems to have checked everything out at boot time, so I wasn't worried. Two major issues have popped up today:

1) My clock is an hour behind. Seems like DST was lost/forgotten.
2) k3b now only allows me to select burn speeds up to 12x. It used to correctly suggest speeds as high as 52x. (The fact that it only burns at 2x is irrelevant, it's always done that and I've been emailing Sebastian about it.)

Any other errors are as yet unknown. Is this a result of the crash, or is my hardware going to pieces, or what? The only change I've made over the past few days is installing the Slack10.2 x11 security patch (just did it yesterday *after* the crash).

Slack 10.2 (linux 2.6.16.3)
AMD Duron 850
0.5G RAM
Memorex 52MAXX CD-RW
"et cetera, et cetera, et cetera"

Matt

After getting home from classes, I noticed my clock has gone haywire again (I reset it this morning, and the proper timezone/daylight savings was selected). It now reads 21:28 EDT when the time is actually 17:32 EDT.

Is my system about to die?

Matt

Run

Ah, but due to a failed attempt to dual-boot (Win2k crashed irreparably after 2 weeks), my hwclock is keeps local time. Should I still use the --utc option?

Thanks for the help, btw!

Matt