I haven't tracked down the cause, but I have seen this. It appears to be a strange 10.2 issue, and it may have something to do with Microsoft Word (that's the only common denominator I could find — all the computers that had it were running Word). Anyway, a restart fixes it for me. Logging out and back in probably would have the same effect, but I like to fsck whenever a computer is acting funny anyway.