🚀 go-pugleaf

My machine mysteriously locked up sometime between around lunch on 
December 31 and about 9 am January 1.  I was unable to get to it
physically to see what state it was in, however I assumed that there
had been a power outage and the machine had simply not rebooted
(another big pain in the b***, but that's unrelated to my current
question.  I was lucky to find someone around who could reboot the
machine for me, but I did not talk to him afterwards and did not
find out any information about the state in which he found it,
though it did appear from wtmp that there had not been a power
outage as I had thought.  I did not really think any more about it
until today, when I noticed the following lines in my auth log file:

Jan  1 02:47:19 lusty loginwindow[2880]: loginwindow: could not find WindowServe
r port!
Jan  1 02:52:24 lusty -[2883]: DPS client library error: Connection closed unexp
ectedly, DPSContext 3e270, data 0
Jan  1 02:52:27 lusty -[2883]: DPS client library error: Error while writing to
connection, DPSContext 3e270, data -102
Jan  1 02:52:28 lusty -[2883]: DPS error dps_err_write
Jan  1 02:52:28 lusty last message repeated 20 times
Jan  1 02:52:28 lusty -[2883]: exiting due to excessive DPS errors
Jan  1 02:55:06 lusty loginwindow[2887]: loginwindow: could not find WindowServe
r port!
Jan  1 02:56:48 lusty loginwindow[2889]: loginwindow: could not find WindowServe
r port!
Jan  1 02:57:40 lusty loginwindow[2893]: loginwindow: could not find WindowServe
r port!
Jan  1 02:59:04 lusty loginwindow[2895]: loginwindow: could not find WindowServe
r port!
Jan  1 03:00:46 lusty loginwindow[2899]: loginwindow: could not find WindowServe
r port!
Jan  1 03:02:43 lusty loginwindow[2903]: loginwindow: could not find WindowServe
r port!
Jan  1 03:07:24 lusty loginwindow[2907]: loginwindow: could not find WindowServe
r port!

Does anyone know the probable cause of these messages?  I'm running 3.0,
if that makes a difference.  Under 2.1 I don't think I ever had this
problem.

Diana