[ 21261.465] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 21261.465] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 21261.465] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 21261.466] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 21261.466] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 21261.466] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 21261.466] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 21261.466] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 21261.466] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 21261.466] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 21261.466] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 21261.466] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 21261.466] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 21261.466] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 21261.466] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 21261.466] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 21261.466] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 21261.466] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 21261.466] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 21261.466] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 21261.466] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 21261.466] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 21261.466] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 21261.466] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
[ 21261.466] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
......
On Monday, August 5, 2019, 12:07:30 PM GMT+8, David Wright <deblis@lionunicorn.co.uk> wrote:
On Sun 04 Aug 2019 at 20:56:01 (+0000), Long Wind wrote:
the file is more than 3 G, i can't read it with nanoi have 3 G memory, no swap
why don't X print important error msg to terminals?i can't see any of them
is it a bug of X?? my problem isn't solved,
ls .local/share/xorg/ -ltotal 3770920
-rw-r--r-- 1 zhou zhou 32654 Aug 5 04:40 Xorg.0.log
-rw-r--r-- 1 zhou zhou 39127 Aug 5 04:38 Xorg.0.log.old
-rw-r--r-- 1 zhou zhou 3861332996 Aug 4 22:16 Xorg.1.log
You reported Sun, 4 Aug 2019 10:43:06 +0000 (UTC) that:
Xorg.0.log.old
it's more than 3.9G
it seems keeping growing
clearly i don't need it,
i delete it
Since then it would appear that you've run X twice, so any Xorg.0.log*
files from that era have long gone. But now you've sprung the file
Xorg.1.log on us, which looks as though you've run 2 X servers at the
same time, just on the one occasion, the evening of 2019-08-04.
(But I don't know whether you timezone is really UTC.)
I'm guessing that whatever made Xorg.0.log huge also had the same
effect on Xorg.1.log so it would be useful to look at that file
before you delete it.
$ tail -100 ~/.local/share/xorg/Xorg.1.log
will show you the last 100 lines which might be enough. If not,
you can sample the file with
$ less ~/.local/share/xorg/Xorg.1.log
and then by typing 50p 70p 90p 95p which will move to 50%,
70%, 90%, 95% of the way through the file, faster than scrolling.
It's quite possible that the files' sizes were entirely caused by
your running two X servers at the same time. The log may tell
you what the issue was, and it would be useful to post it
(the issue, and perhaps a few lines from the log) here.
below is Xorg.0.log:
[snipped]
On Sunday, August 4, 2019, 11:37:07 PM GMT+8, David Wright <deblis@lionunicorn.co.uk> wrote:
On Sun 04 Aug 2019 at 13:06:07 (+0200), Pascal Hambourg wrote:
Le 04/08/2019 à 12:43, Long Wind a écrit :
i think i find out
it's in ~/.local it's Xorg.0.log.old
it's more than 3.9G
it seems keeping growing
clearly i don't need it, i delete it
it should solve my problem
What about Xorg.0.log ?
If these files keep growing up to such a size, then it means that they
are flooded by repeated messages. Before deleting them, you should
read their contents and fix the underlying issue or they will fill
your disk space again and again.
Agreed. It would be odd if Xorg.0.log.old is still growing because
that's the log from the previous session. So I'd assume it's
probably Xorg.0.log that's growing, and Xorg.0.log.old is just
sitting there.
Bear in mind that if you delete a file that is still held open by
some process, you won't reclaim the free space until that process
closes the file. So until that time, du will no longer see its
space as used but df will not see it as available either.
Cheers,
David.