View Single Post
Posts: 24 | Thanked: 5 times | Joined on Oct 2010 @ Portugal
#9
Originally Posted by jprobichaud View Post
That doesn't work as the log file handle is still open and kept by the X server. You will see that the file is gone, but the disk space won't be available again.

The echo > Xorg.0.log trick seems to work (at least "df" is happy about it)

Now am I the only one seeing these lines in their Xorg log?

Code:
(II) button (value): 0(0)                                                  
(II) EV_KEY (code, value, ignored, ev.code, val, flags): 0, 0, 0, 28, 0, 33
Just a completely wild guess, but could it be a keyboard hardware problem?
My logic is: if EV_KEY is a keyboard event, then maybe the system is being overrun by spurious events generated by a hardware problem...