where is my disk space

classic Classic list List threaded Threaded
23 messages Options
12
Reply | Threaded
Open this post in threaded view
|

where is my disk space

Long Wind-2
i have stretch at sda2, which has 9.8G
free space is far more than 1 G
but some program i'm unware of take all space

how to find out and solve? Thanks!
Reply | Threaded
Open this post in threaded view
|

Re: where is my disk space

tomas@tuxteam.de
On Sun, Aug 04, 2019 at 08:32:00AM +0000, Long Wind wrote:
> i have stretch at sda2, which has 9.8Gfree space is far more than 1 Gbut some program i'm unware of take all space
> how to find out and solve? Thanks!

Your request is too general for a meaningful answer.

First off, space on a file system is taken up by "files". If you want
to find out where the space is missing, "du" is a good command.

Files live on file systems, so "sda2" (the device) is pretty meaningless
in this context [1]. Let's assume /dev/sda2 is mounted on / -- then

  sudo du -sh /*

will give you, directory for directory, where the space goes (the option
"-s" says "summary", the option "-h" is for "human readable" (i.e. it
would say "1.2G" instead of "1201345", for example).

Then you can work your way down. May be you find a file you "know" and
decide you can remove it. Maybe you aren't sure -- then the next step
would be to find out which program is generating those files.

There are many details I left off, but you'd have to be more specific
if you want more specific help.

Cheers

[1] Blame stupid desktop environments for leading users to mix up
   all that stuff.

-- tomás

signature.asc (205 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: where is my disk space

Long Wind-2
thank!  i enter "du -sh /home", it's 5.8G. it's unbelievable

i enter "df -h"
Filesystem      Size  Used Avail Use% Mounted on
udev            1.5G     0  1.5G   0% /dev
tmpfs           298M  4.5M  293M   2% /run
/dev/sda2       9.8G  9.3G     0 100% /
......

0.5 G seems missing

On Sunday, August 4, 2019, 5:27:01 PM GMT+8, <[hidden email]> wrote:


On Sun, Aug 04, 2019 at 08:32:00AM +0000, Long Wind wrote:

> i have stretch at sda2, which has 9.8Gfree space is far more than 1 Gbut some program i'm unware of take all space
> how to find out and solve? Thanks!


Your request is too general for a meaningful answer.

First off, space on a file system is taken up by "files". If you want
to find out where the space is missing, "du" is a good command.

Files live on file systems, so "sda2" (the device) is pretty meaningless
in this context [1]. Let's assume /dev/sda2 is mounted on / -- then

  sudo du -sh /*

will give you, directory for directory, where the space goes (the option
"-s" says "summary", the option "-h" is for "human readable" (i.e. it
would say "1.2G" instead of "1201345", for example).

Then you can work your way down. May be you find a file you "know" and
decide you can remove it. Maybe you aren't sure -- then the next step
would be to find out which program is generating those files.

There are many details I left off, but you'd have to be more specific
if you want more specific help.

Cheers

[1] Blame stupid desktop environments for leading users to mix up
  all that stuff.

-- tomás
Reply | Threaded
Open this post in threaded view
|

Re: where is my disk space

Étienne Mollier
In reply to this post by tomas@tuxteam.de
tomás, on 2019-08-04:

> On Sun, Aug 04, 2019 at 08:32:00AM +0000, Long Wind wrote:
> > i have stretch at sda2, which has 9.8G
> > free space is far more than 1 G
> > but some program i'm unware of take all space
> >
> > how to find out and solve? Thanks!
>
> Your request is too general for a meaningful answer.
>
> First off, space on a file system is taken up by "files". If you want
> to find out where the space is missing, "du" is a good command.
>
> Files live on file systems, so "sda2" (the device) is pretty meaningless
> in this context [1]. Let's assume /dev/sda2 is mounted on / -- then
>
>   sudo du -sh /*
>
> will give you, directory for directory, where the space goes (the option
> "-s" says "summary", the option "-h" is for "human readable" (i.e. it
> would say "1.2G" instead of "1201345", for example).
>
> Then you can work your way down. May be you find a file you "know" and
> decide you can remove it. Maybe you aren't sure -- then the next step
> would be to find out which program is generating those files.
>
> There are many details I left off, but you'd have to be more specific
> if you want more specific help.
Good day Long Wind,

In complement to the advice from tomás about using "du", if you
have a bit of space left, you can install "ncdu" and use it to
identify which directory takes all the space:

        $ sudo apt install ncdu

To scan your root file system, assuming it is the mount point of
your /dev/sda2, for instance you could run the following
command, give some time to the command for proceeding to the
scan, and navigate in your file system tree, sorted by disk
usage:

        $ sudo ncdu -x /

Note the "-x" switch, which will avoid to cross file system
mount points, this is useful for instance to /not/ scan
directories such as /proc or /sys, which are not stored on disk
but in memory, and generally it avoids to scan files which are
not members of the partition.  The "du" command also accepts
this option, by the way, but is a bit tricky to use when
scanning /* as one would have to exclude explicitly mount points
such as /sys, /proc and /dev with several --exclude= options.

Kind Regards
--
Étienne Mollier <[hidden email]>
               5ab1 4edf 63bb ccff 8b54 2fa9 59da 56fe fff3 882d



signature.asc (673 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: where is my disk space

Étienne Mollier
In reply to this post by Long Wind-2
Long Wind, on 2019-08-04:
> i enter "df -h"
> Filesystem      Size  Used Avail Use% Mounted on
> [...]
> /dev/sda2       9.8G  9.3G     0 100% /
> ......
>
> 0.5 G seems missing

This space is most likely taken up by file system metadata, such
as inode tables, or journaling space.  0.5 G looks a lot like 5%
of a 10 G partition, which is the default setting for Ext4
metadata as provided in Debian Installer.

Kind Regards
--
Étienne Mollier <[hidden email]>
               5ab1 4edf 63bb ccff 8b54 2fa9 59da 56fe fff3 882d



signature.asc (673 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: where is my disk space

andreimpopescu
In reply to this post by Long Wind-2
On Du, 04 aug 19, 08:32:00, Long Wind wrote:
> i have stretch at sda2, which has 9.8Gfree space is far more than 1 Gbut some program i'm unware of take all space
> how to find out and solve? Thanks!


To find out what files are taking up the space

Command line:

    du -hx --maxdepth=1 <directory> | sort -h

Start with the mountpoint of the drive and work your way through the
directories.

Run as root if you get permission errors (e.g. you start at /)


Text user interface:

Press Ctrl+Space in mc to find out the size of directories, though the
display is not so friendly for large sizes (KiB or B only).

ncdu uses adaptive units and a sort of graphical aid, but you'll have to
go back to mc (or command line) to actually do something about it.


Graphical user interface:

My preferred tool for something like this would be one of the Total
Commander clones, e.g. Tux Commander (package tuxcmd), but there is also
Double Commander (doublecmd-gtk or doublecmd-qt, depending on your
environment), as well as Krusader (package krusader, all the bells and
whistles, but also heavier).


Solutions depend a lot on what is using up your space.


Hope this helps,
Andrei
--
http://wiki.debian.org/FAQsFromDebianUser

signature.asc (849 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: where is my disk space

Thomas Schmitt
In reply to this post by Long Wind-2
Hi,

Long Wind wrote:
> /dev/sda2       9.8G  9.3G     0 100% /

I place my bet on the highest rated answer in
  https://unix.stackexchange.com/questions/7950/reserved-space-for-root-on-a-filesystem-why
mattdm wrote there:
  "Ext3 is pretty good at avoiding filesystem fragmentation, but once
   you get above about 95% full, that behavior falls off the cliff,
   and suddenly filesystem performance becomes a mess. So leaving 5%
   reserved gives you a buffer against this."


Have a nice day :)

Thomas

Reply | Threaded
Open this post in threaded view
|

Re: where is my disk space

andreimpopescu
In reply to this post by Étienne Mollier
On Du, 04 aug 19, 11:46:31, Étienne Mollier wrote:
>
> This space is most likely taken up by file system metadata, such
> as inode tables, or journaling space.  0.5 G looks a lot like 5%
> of a 10 G partition, which is the default setting for Ext4
> metadata as provided in Debian Installer.

The 5% are "reserved for the super-user", not metadata, see the manpage
for mke2fs.

Kind regards,
Andrei
--
http://wiki.debian.org/FAQsFromDebianUser

signature.asc (849 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: where is my disk space

Étienne Mollier
On 04/08/2019 11.58, Andrei POPESCU wrote:
> On Du, 04 aug 19, 11:46:31, Étienne Mollier wrote:
>> This space is most likely taken up by file system metadata, such
>> as inode tables, or journaling space.  0.5 G looks a lot like 5%
>> of a 10 G partition, which is the default setting for Ext4
>> metadata as provided in Debian Installer.
> The 5% are "reserved for the super-user", not metadata, see the manpage
> for mke2fs.

My bad, I shouldn't intervene from memory like this.  Now you
mention it, I recall it's also worded this way in d-i too.

Thanks,
--
Étienne Mollier <[hidden email]>
               5AB1 4EDF 63BB CCFF 8B54 2FA9 59DA 56FE FFF3 882D


signature.asc (673 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: where is my disk space

tomas@tuxteam.de
In reply to this post by Long Wind-2
On Sun, Aug 04, 2019 at 09:37:12AM +0000, Long Wind wrote:
>  thank!  i enter "du -sh /home", it's 5.8G. it's unbelievable

You mean: it is more than you expected? If so, you can try

  du -sh /home/*

to see which subdirectory holds the biggest chunk, and slowly
work your way down the directory tree (note: this will exclude
the dot files and directories, because the glob ("*") doesn't
include them, at least usually. If you suspect one of those,
better do

  du -sh $(ls -A /home)

or something similar)

> i enter "df -h"Filesystem      Size  Used Avail Use% Mounted on
> udev            1.5G     0  1.5G   0% /dev
> tmpfs           298M  4.5M  293M   2% /run
> /dev/sda2       9.8G  9.3G     0 100% /......
>
> 0.5 G seems missing

Others have chimed in with good ideas. First, 0.5G seems reasonable
for "file system internal use" -- inodes, possibly journal, etc.

On my box:

  tomas@trotzki:~$ sudo du -sh /home
  [sudo] password for tomas:
  368G    /home
 
  tomas@trotzki:~$ df -h
  Filesystem                Size  Used Avail Use% Mounted on
  [...]
  /dev/mapper/trotzki-home  640G  368G  241G  61% /home

That's (368 - 241) / 368 -- around 35 percent (it's an ext4 file system).

Cheers
-- tomás

signature.asc (205 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: where is my disk space

Long Wind-2
i think i find out
it's in ~/.local
it's more than 3.9G
it seems keeping growing
clearly i don't need it, i delete it
it should solve my problem

Thanks to all that reply!

On Sunday, August 4, 2019, 6:26:11 PM GMT+8, [hidden email] <[hidden email]> wrote:


On Sun, Aug 04, 2019 at 09:37:12AM +0000, Long Wind wrote:
>  thank!  i enter "du -sh /home", it's 5.8G. it's unbelievable

You mean: it is more than you expected? If so, you can try

  du -sh /home/*

to see which subdirectory holds the biggest chunk, and slowly
work your way down the directory tree (note: this will exclude
the dot files and directories, because the glob ("*") doesn't
include them, at least usually. If you suspect one of those,
better do

  du -sh $(ls -A /home)

or something similar)

> i enter "df -h"Filesystem      Size  Used Avail Use% Mounted on
> udev            1.5G     0  1.5G   0% /dev
> tmpfs           298M  4.5M  293M   2% /run
> /dev/sda2       9.8G  9.3G     0 100% /......
>
> 0.5 G seems missing

Others have chimed in with good ideas. First, 0.5G seems reasonable
for "file system internal use" -- inodes, possibly journal, etc.

On my box:

  [hidden email]:~$ sudo du -sh /home
  [sudo] password for tomas:
  368G    /home
 
  [hidden email]:~$ df -h
  Filesystem                Size  Used Avail Use% Mounted on
  [...]
  /dev/mapper/trotzki-home  640G  368G  241G  61% /home

That's (368 - 241) / 368 -- around 35 percent (it's an ext4 file system).


Cheers
-- tomás
Reply | Threaded
Open this post in threaded view
|

Re: where is my disk space

Pascal Hambourg-2
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.

Reply | Threaded
Open this post in threaded view
|

Re: where is my disk space

David Wright-3
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.

Reply | Threaded
Open this post in threaded view
|

Re: where is my disk space

Long Wind-2
the file is more than 3 G, i can't read it with nano
i 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/ -l
total 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

below is Xorg.0.log:
[    57.911] 
X.Org X Server 1.19.2
Release Date: 2017-03-02
[    57.912] X Protocol Version 11, Revision 0
[    57.912] Build Operating System: Linux 4.9.0-8-amd64 i686 Debian
[    57.912] Current Operating System: Linux debian 4.9.0-8-686-pae #1 SMP Debian 4.9.130-2 (2018-10-27) i686
[    57.912] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.9.0-8-686-pae root=UUID=9fa45cf1-3294-4a9e-92df-70ffe9a9aa06 ro quiet
[    57.913] Build Date: 03 November 2018  03:08:43AM
[    57.913] xorg-server 2:1.19.2-1+deb9u5 (https://www.debian.org/support) 
[    57.913] Current version of pixman: 0.34.0
[    57.913] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[    57.913] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[    57.914] (==) Log file: "/home/zhou/.local/share/xorg/Xorg.0.log", Time: Mon Aug  5 04:40:20 2019
[    57.932] (==) Using config file: "/etc/X11/xorg.conf"
[    57.933] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[    57.953] (==) No Layout section.  Using the first Screen section.
[    57.953] (**) |-->Screen "Default Screen" (0)
[    57.954] (**) |   |-->Monitor "Configured Monitor"
[    57.955] (==) No device specified for screen "Default Screen".
	Using the first device section listed.
[    57.955] (**) |   |-->Device "Configured Video Device"
[    57.955] (==) Automatically adding devices
[    57.955] (==) Automatically enabling devices
[    57.955] (==) Automatically adding GPU devices
[    57.955] (==) Max clients allowed: 256, resource mask: 0x1fffff
[    57.960] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[    57.961] 	Entry deleted from font path.
[    57.965] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
[    57.965] 	Entry deleted from font path.
[    57.965] (WW) The directory "/usr/share/fonts/X11/Type1" does not exist.
[    57.965] 	Entry deleted from font path.
[    57.966] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist.
[    57.966] 	Entry deleted from font path.
[    57.966] (==) FontPath set to:
	/usr/share/fonts/X11/misc,
	/usr/share/fonts/X11/100dpi/:unscaled,
	/usr/share/fonts/X11/100dpi,
	built-ins
[    57.966] (==) ModulePath set to "/usr/lib/xorg/modules"
[    57.966] (II) The server relies on udev to provide the list of input devices.
	If no devices become available, reconfigure udev or disable AutoAddDevices.
[    57.966] (II) Loader magic: 0x750720
[    57.966] (II) Module ABI versions:
[    57.966] 	X.Org ANSI C Emulation: 0.4
[    57.966] 	X.Org Video Driver: 23.0
[    57.966] 	X.Org XInput driver : 24.1
[    57.966] 	X.Org Server Extension : 10.0
[    57.968] (++) using VT number 1

[    57.972] (II) systemd-logind: took control of session /org/freedesktop/login1/session/_31
[    57.974] (II) xfree86: Adding drm device (/dev/dri/card0)
[    57.975] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 11 paused 0
[    57.978] (--) PCI:*(0:1:5:0) 1002:5954:103c:3009 rev 0, Mem @ 0xd8000000/134217728, 0xfd9f0000/65536, I/O @ 0x0000bc00/256, BIOS @ 0x????????/131072
[    57.978] (II) LoadModule: "glx"
[    58.007] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[    58.126] (II) Module glx: vendor="X.Org Foundation"
[    58.126] 	compiled for 1.19.2, module version = 1.0.0
[    58.126] 	ABI class: X.Org Server Extension, version 10.0
[    58.126] (II) LoadModule: "ati"
[    58.127] (II) Loading /usr/lib/xorg/modules/drivers/ati_drv.so
[    58.132] (II) Module ati: vendor="X.Org Foundation"
[    58.133] 	compiled for 1.19.0, module version = 7.8.0
[    58.133] 	Module class: X.Org Video Driver
[    58.133] 	ABI class: X.Org Video Driver, version 23.0
[    58.133] (II) LoadModule: "radeon"
[    58.133] (II) Loading /usr/lib/xorg/modules/drivers/radeon_drv.so
[    58.157] (II) Module radeon: vendor="X.Org Foundation"
[    58.157] 	compiled for 1.19.0, module version = 7.8.0
[    58.157] 	Module class: X.Org Video Driver
[    58.158] 	ABI class: X.Org Video Driver, version 23.0
[    58.158] (II) RADEON: Driver for ATI/AMD Radeon chipsets:
	ATI Radeon Mobility X600 (M24), ATI FireMV 2400,
	ATI Radeon Mobility X300 (M24), ATI FireGL M24 GL,
	ATI Radeon X600 (RV380), ATI FireGL V3200 (RV380),
	ATI Radeon IGP320 (A3), ATI Radeon IGP330/340/350 (A4),
	ATI Radeon 9500, ATI Radeon 9600TX, ATI FireGL Z1, ATI Radeon 9800SE,
	ATI Radeon 9800, ATI FireGL X2, ATI Radeon 9600, ATI Radeon 9600SE,
	ATI Radeon 9600XT, ATI FireGL T2, ATI Radeon 9650, ATI FireGL RV360,
	ATI Radeon 7000 IGP (A4+), ATI Radeon 8500 AIW,
	ATI Radeon IGP320M (U1), ATI Radeon IGP330M/340M/350M (U2),
	ATI Radeon Mobility 7000 IGP, ATI Radeon 9000/PRO, ATI Radeon 9000,
	ATI Radeon X800 (R420), ATI Radeon X800PRO (R420),
	ATI Radeon X800SE (R420), ATI FireGL X3 (R420),
	ATI Radeon Mobility 9800 (M18), ATI Radeon X800 SE (R420),
	ATI Radeon X800XT (R420), ATI Radeon X800 VE (R420),
	ATI Radeon X850 (R480), ATI Radeon X850 XT (R480),
	ATI Radeon X850 SE (R480), ATI Radeon X850 PRO (R480),
	ATI Radeon X850 XT PE (R480), ATI Radeon Mobility M7,
	ATI Mobility FireGL 7800 M7, ATI Radeon Mobility M6,
	ATI FireGL Mobility 9000 (M9), ATI Radeon Mobility 9000 (M9),
	ATI Radeon 9700 Pro, ATI Radeon 9700/9500Pro, ATI FireGL X1,
	ATI Radeon 9800PRO, ATI Radeon 9800XT,
	ATI Radeon Mobility 9600/9700 (M10/M11),
	ATI Radeon Mobility 9600 (M10), ATI Radeon Mobility 9600 (M11),
	ATI FireGL Mobility T2 (M10), ATI FireGL Mobility T2e (M11),
	ATI Radeon, ATI FireGL 8700/8800, ATI Radeon 8500, ATI Radeon 9100,
	ATI Radeon 7500, ATI Radeon VE/7000, ATI ES1000,
	ATI Radeon Mobility X300 (M22), ATI Radeon Mobility X600 SE (M24C),
	ATI FireGL M22 GL, ATI Radeon X800 (R423), ATI Radeon X800PRO (R423),
	ATI Radeon X800LE (R423), ATI Radeon X800SE (R423),
	ATI Radeon X800 XTP (R430), ATI Radeon X800 XL (R430),
	ATI Radeon X800 SE (R430), ATI Radeon X800 (R430),
	ATI FireGL V7100 (R423), ATI FireGL V5100 (R423),
	ATI FireGL unknown (R423), ATI Mobility FireGL V5000 (M26),
	ATI Mobility Radeon X700 XL (M26), ATI Mobility Radeon X700 (M26),
	ATI Radeon X550XTX, ATI Radeon 9100 IGP (A5),
	ATI Radeon Mobility 9100 IGP (U3), ATI Radeon XPRESS 200,
	ATI Radeon XPRESS 200M, ATI Radeon 9250, ATI Radeon 9200,
	ATI Radeon 9200SE, ATI FireMV 2200, ATI Radeon X300 (RV370),
	ATI Radeon X600 (RV370), ATI Radeon X550 (RV370),
	ATI FireGL V3100 (RV370), ATI FireMV 2200 PCIE (RV370),
	ATI Radeon Mobility 9200 (M9+), ATI Mobility Radeon X800 XT (M28),
	ATI Mobility FireGL V5100 (M28), ATI Mobility Radeon X800 (M28),
	ATI Radeon X850, ATI unknown Radeon / FireGL (R480),
	ATI Radeon X800XT (R423), ATI FireGL V5000 (RV410),
	ATI Radeon X700 XT (RV410), ATI Radeon X700 PRO (RV410),
	ATI Radeon X700 SE (RV410), ATI Radeon X700 (RV410),
	ATI Radeon X1800, ATI Mobility Radeon X1800 XT,
	ATI Mobility Radeon X1800, ATI Mobility FireGL V7200,
	ATI FireGL V7200, ATI FireGL V5300, ATI Mobility FireGL V7100,
	ATI FireGL V7300, ATI FireGL V7350, ATI Radeon X1600, ATI RV505,
	ATI Radeon X1300/X1550, ATI Radeon X1550, ATI M54-GL,
	ATI Mobility Radeon X1400, ATI Radeon X1550 64-bit,
	ATI Mobility Radeon X1300, ATI Radeon X1300, ATI FireGL V3300,
	ATI FireGL V3350, ATI Mobility Radeon X1450,
	ATI Mobility Radeon X2300, ATI Mobility Radeon X1350,
	ATI FireMV 2250, ATI Radeon X1650, ATI Mobility FireGL V5200,
	ATI Mobility Radeon X1600, ATI Radeon X1300 XT/X1600 Pro,
	ATI FireGL V3400, ATI Mobility FireGL V5250,
	ATI Mobility Radeon X1700, ATI Mobility Radeon X1700 XT,
	ATI FireGL V5200, ATI Radeon X2300HD, ATI Mobility Radeon HD 2300,
	ATI Radeon X1950, ATI Radeon X1900, ATI AMD Stream Processor,
	ATI RV560, ATI Mobility Radeon X1900, ATI Radeon X1950 GT, ATI RV570,
	ATI FireGL V7400, ATI Radeon 9100 PRO IGP,
	ATI Radeon Mobility 9200 IGP, ATI Radeon X1200, ATI RS740,
	ATI RS740M, ATI Radeon HD 2900 XT, ATI Radeon HD 2900 Pro,
	ATI Radeon HD 2900 GT, ATI FireGL V8650, ATI FireGL V8600,
	ATI FireGL V7600, ATI Radeon 4800 Series, ATI Radeon HD 4870 x2,
	ATI Radeon HD 4850 x2, ATI FirePro V8750 (FireGL),
	ATI FirePro V7760 (FireGL), ATI Mobility RADEON HD 4850,
	ATI Mobility RADEON HD 4850 X2, ATI FirePro RV770,
	AMD FireStream 9270, AMD FireStream 9250, ATI FirePro V8700 (FireGL),
	ATI Mobility RADEON HD 4870, ATI Mobility RADEON M98,
	ATI FirePro M7750, ATI M98, ATI Mobility Radeon HD 4650,
	ATI Radeon RV730 (AGP), ATI Mobility Radeon HD 4670,
	ATI FirePro M5750, ATI RV730XT [Radeon HD 4670], ATI RADEON E4600,
	ATI Radeon HD 4600 Series, ATI RV730 PRO [Radeon HD 4650],
	ATI FirePro V7750 (FireGL), ATI FirePro V5700 (FireGL),
	ATI FirePro V3750 (FireGL), ATI Mobility Radeon HD 4830,
	ATI Mobility Radeon HD 4850, ATI FirePro M7740, ATI RV740,
	ATI Radeon HD 4770, ATI Radeon HD 4700 Series, ATI RV610,
	ATI Radeon HD 2400 XT, ATI Radeon HD 2400 Pro,
	ATI Radeon HD 2400 PRO AGP, ATI FireGL V4000, ATI Radeon HD 2350,
	ATI Mobility Radeon HD 2400 XT, ATI Mobility Radeon HD 2400,
	ATI RADEON E2400, ATI FireMV 2260, ATI RV670, ATI Radeon HD3870,
	ATI Mobility Radeon HD 3850, ATI Radeon HD3850,
	ATI Mobility Radeon HD 3850 X2, ATI Mobility Radeon HD 3870,
	ATI Mobility Radeon HD 3870 X2, ATI Radeon HD3870 X2,
	ATI FireGL V7700, ATI Radeon HD3690, AMD Firestream 9170,
	ATI Radeon HD 4550, ATI Radeon RV710, ATI Radeon HD 4350,
	ATI Mobility Radeon 4300 Series, ATI Mobility Radeon 4500 Series,
	ATI FirePro RG220, ATI Mobility Radeon 4330, ATI RV630,
	ATI Mobility Radeon HD 2600, ATI Mobility Radeon HD 2600 XT,
	ATI Radeon HD 2600 XT AGP, ATI Radeon HD 2600 Pro AGP,
	ATI Radeon HD 2600 XT, ATI Radeon HD 2600 Pro, ATI Gemini RV630,
	ATI Gemini Mobility Radeon HD 2600 XT, ATI FireGL V5600,
	ATI FireGL V3600, ATI Radeon HD 2600 LE,
	ATI Mobility FireGL Graphics Processor, ATI Radeon HD 3470,
	ATI Mobility Radeon HD 3430, ATI Mobility Radeon HD 3400 Series,
	ATI Radeon HD 3450, ATI Radeon HD 3430, ATI FirePro V3700,
	ATI FireMV 2450, ATI Radeon HD 3600 Series, ATI Radeon HD 3650 AGP,
	ATI Radeon HD 3600 PRO, ATI Radeon HD 3600 XT,
	ATI Mobility Radeon HD 3650, ATI Mobility Radeon HD 3670,
	ATI Mobility FireGL V5700, ATI Mobility FireGL V5725,
	ATI Radeon HD 3200 Graphics, ATI Radeon 3100 Graphics,
	ATI Radeon HD 3300 Graphics, ATI Radeon 3000 Graphics, SUMO, SUMO2,
	ATI Radeon HD 4200, ATI Radeon 4100, ATI Mobility Radeon HD 4200,
	ATI Mobility Radeon 4100, ATI Radeon HD 4290, ATI Radeon HD 4250,
	AMD Radeon HD 6310 Graphics, AMD Radeon HD 6250 Graphics,
	AMD Radeon HD 6300 Series Graphics,
	AMD Radeon HD 6200 Series Graphics, PALM, CYPRESS,
	ATI FirePro (FireGL) Graphics Adapter, AMD Firestream 9370,
	AMD Firestream 9350, ATI Radeon HD 5800 Series,
	ATI Radeon HD 5900 Series, ATI Mobility Radeon HD 5800 Series,
	ATI Radeon HD 5700 Series, ATI Radeon HD 6700 Series,
	ATI Mobility Radeon HD 5000 Series, ATI Mobility Radeon HD 5570,
	ATI Radeon HD 5670, ATI Radeon HD 5570, ATI Radeon HD 5500 Series,
	REDWOOD, ATI Mobility Radeon Graphics, CEDAR, ATI FirePro 2270,
	ATI Radeon HD 5450, CAYMAN, AMD Radeon HD 6900 Series,
	AMD Radeon HD 6900M Series, Mobility Radeon HD 6000 Series, BARTS,
	AMD Radeon HD 6800 Series, AMD Radeon HD 6700 Series, TURKS, CAICOS,
	ARUBA, TAHITI, PITCAIRN, VERDE, OLAND, HAINAN, BONAIRE, KABINI,
	MULLINS, KAVERI, HAWAII
[    58.171] (II) [KMS] Kernel modesetting enabled.
[    58.171] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[    58.171] (**) RADEON(0): Depth 24, (--) framebuffer bpp 32
[    58.171] (II) RADEON(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps)
[    58.171] (==) RADEON(0): Default visual is TrueColor
[    58.171] (==) RADEON(0): RGB weight 888
[    58.172] (II) RADEON(0): Using 8 bits per RGB (8 bit DAC)
[    58.172] (--) RADEON(0): Chipset: "ATI Radeon XPRESS 200" (ChipID = 0x5954)
[    58.172] (II) Loading sub module "fb"
[    58.172] (II) LoadModule: "fb"
[    58.172] (II) Loading /usr/lib/xorg/modules/libfb.so
[    58.182] (II) Module fb: vendor="X.Org Foundation"
[    58.182] 	compiled for 1.19.2, module version = 1.0.0
[    58.182] 	ABI class: X.Org ANSI C Emulation, version 0.4
[    58.182] (II) Loading sub module "dri2"
[    58.182] (II) LoadModule: "dri2"
[    58.182] (II) Module "dri2" already built-in
[    58.182] (II) Loading sub module "exa"
[    58.182] (II) LoadModule: "exa"
[    58.183] (II) Loading /usr/lib/xorg/modules/libexa.so
[    58.188] (II) Module exa: vendor="X.Org Foundation"
[    58.188] 	compiled for 1.19.2, module version = 2.6.0
[    58.188] 	ABI class: X.Org Video Driver, version 23.0
[    58.188] (II) RADEON(0): KMS Color Tiling: enabled
[    58.188] (II) RADEON(0): KMS Color Tiling 2D: disabled
[    58.188] (II) RADEON(0): KMS Pageflipping: enabled
[    58.188] (II) RADEON(0): SwapBuffers wait for vsync: enabled
[    58.201] (II) RADEON(0): Output VGA-0 using monitor section Configured Monitor
[    58.202] (II) RADEON(0): Output DVI-0 has no monitor section
[    58.214] (II) RADEON(0): EDID for output VGA-0
[    58.214] (II) RADEON(0): Not using mode "1024x768" (hsync out of range)
[    58.214] (II) RADEON(0): Not using mode "800x600" (vrefresh out of range)
[    58.214] (II) RADEON(0): Not using mode "848x480" (hsync out of range)
[    58.214] (II) RADEON(0): Not using mode "640x480" (hsync out of range)
[    58.214] (II) RADEON(0): Printing probed modes for output VGA-0
[    58.214] (II) RADEON(0): Modeline "800x600"x60.3   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz UeP)
[    58.215] (II) RADEON(0): EDID for output DVI-0
[    58.215] (II) RADEON(0): Output VGA-0 connected
[    58.215] (II) RADEON(0): Output DVI-0 disconnected
[    58.215] (II) RADEON(0): Using user preference for initial modes
[    58.215] (II) RADEON(0): Output VGA-0 using initial mode 800x600 +0+0
[    58.215] (II) RADEON(0): mem size init: gart size :1fdff000 vram size: s:4000000 visible:7cc0000
[    58.215] (II) RADEON(0): EXA: Driver will allow EXA pixmaps in VRAM
[    58.215] (==) RADEON(0): DPI set to (96, 96)
[    58.215] (==) RADEON(0): Using gamma correction (1.0, 1.0, 1.0)
[    58.215] (II) Loading sub module "ramdac"
[    58.215] (II) LoadModule: "ramdac"
[    58.216] (II) Module "ramdac" already built-in
[    58.216] (--) Depth 24 pixmap format is 32 bpp
[    58.216] (II) RADEON(0): [DRI2] Setup complete
[    58.217] (II) RADEON(0): [DRI2]   DRI driver: r300
[    58.217] (II) RADEON(0): [DRI2]   VDPAU driver: r300
[    58.217] (II) RADEON(0): Front buffer size: 1976K
[    58.217] (II) RADEON(0): VRAM usage limit set to 113162K
[    58.219] (==) RADEON(0): DRI3 disabled
[    58.219] (==) RADEON(0): Backing store enabled
[    58.219] (II) RADEON(0): Direct rendering enabled
[    58.219] (II) RADEON(0): Render acceleration enabled for R300/R400/R500 type cards.
[    58.219] (II) EXA(0): Driver allocated offscreen pixmaps
[    58.219] (II) EXA(0): Driver registered support for the following operations:
[    58.219] (II)         Solid
[    58.219] (II)         Copy
[    58.219] (II)         Composite (RENDER acceleration)
[    58.219] (II)         UploadToScreen
[    58.219] (II)         DownloadFromScreen
[    58.219] (II) RADEON(0): Acceleration enabled
[    58.219] (**) RADEON(0): DPMS enabled
[    58.219] (==) RADEON(0): Silken mouse enabled
[    58.220] (II) RADEON(0): Set up textured video
[    58.220] (II) RADEON(0): [XvMC] Associated with Radeon Textured Video.
[    58.220] (II) RADEON(0): [XvMC] Extension initialized.
[    58.220] (II) RADEON(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[    58.222] (--) RandR disabled
[    58.239] (II) SELinux: Disabled on system
[    58.973] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[    58.974] (II) AIGLX: enabled GLX_ARB_create_context
[    58.974] (II) AIGLX: enabled GLX_ARB_create_context_profile
[    58.974] (II) AIGLX: enabled GLX_EXT_create_context_es{,2}_profile
[    58.974] (II) AIGLX: enabled GLX_INTEL_swap_event
[    58.974] (II) AIGLX: enabled GLX_SGI_swap_control
[    58.974] (II) AIGLX: enabled GLX_EXT_framebuffer_sRGB
[    58.974] (II) AIGLX: enabled GLX_ARB_fbconfig_float
[    58.974] (II) AIGLX: enabled GLX_EXT_fbconfig_packed_float
[    58.974] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
[    58.976] (II) AIGLX: Loaded and initialized r300
[    58.976] (II) GLX: Initialized DRI2 GL provider for screen 0
[    58.977] (II) RADEON(0): Setting screen physical size to 211 x 158
[    59.278] (II) config/udev: Adding input device Power Button (/dev/input/event5)
[    59.278] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[    59.278] (II) LoadModule: "libinput"
[    59.278] (II) Loading /usr/lib/xorg/modules/input/libinput_drv.so
[    59.316] (II) Module libinput: vendor="X.Org Foundation"
[    59.316] 	compiled for 1.19.0, module version = 0.23.0
[    59.316] 	Module class: X.Org XInput Driver
[    59.316] 	ABI class: X.Org XInput driver, version 24.1
[    59.316] (II) Using input driver 'libinput' for 'Power Button'
[    59.318] (II) systemd-logind: got fd for /dev/input/event5 13:69 fd 21 paused 0
[    59.318] (**) Power Button: always reports core events
[    59.318] (**) Option "Device" "/dev/input/event5"
[    59.319] (**) Option "_source" "server/udev"
[    59.320] (II) input device 'Power Button', /dev/input/event5 is tagged by udev as: Keyboard
[    59.320] (II) input device 'Power Button', /dev/input/event5 is a keyboard
[    59.320] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input8/event5"
[    59.320] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[    59.320] (**) Option "xkb_model" "pc105"
[    59.320] (**) Option "xkb_layout" "us"
[    59.322] (II) input device 'Power Button', /dev/input/event5 is tagged by udev as: Keyboard
[    59.322] (II) input device 'Power Button', /dev/input/event5 is a keyboard
[    59.323] (II) config/udev: Adding input device Power Button (/dev/input/event4)
[    59.323] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[    59.323] (II) Using input driver 'libinput' for 'Power Button'
[    59.326] (II) systemd-logind: got fd for /dev/input/event4 13:68 fd 24 paused 0
[    59.326] (**) Power Button: always reports core events
[    59.326] (**) Option "Device" "/dev/input/event4"
[    59.326] (**) Option "_source" "server/udev"
[    59.327] (II) input device 'Power Button', /dev/input/event4 is tagged by udev as: Keyboard
[    59.327] (II) input device 'Power Button', /dev/input/event4 is a keyboard
[    59.327] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input7/event4"
[    59.327] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
[    59.327] (**) Option "xkb_model" "pc105"
[    59.327] (**) Option "xkb_layout" "us"
[    59.328] (II) input device 'Power Button', /dev/input/event4 is tagged by udev as: Keyboard
[    59.328] (II) input device 'Power Button', /dev/input/event4 is a keyboard
[    59.329] (II) config/udev: Adding input device SIGMACHIP USB Keyboard (/dev/input/event0)
[    59.330] (**) SIGMACHIP USB Keyboard: Applying InputClass "libinput keyboard catchall"
[    59.330] (II) Using input driver 'libinput' for 'SIGMACHIP USB Keyboard'
[    59.331] (II) systemd-logind: got fd for /dev/input/event0 13:64 fd 25 paused 0
[    59.331] (**) SIGMACHIP USB Keyboard: always reports core events
[    59.331] (**) Option "Device" "/dev/input/event0"
[    59.331] (**) Option "_source" "server/udev"
[    59.332] (II) input device 'SIGMACHIP USB Keyboard', /dev/input/event0 is tagged by udev as: Keyboard
[    59.332] (II) input device 'SIGMACHIP USB Keyboard', /dev/input/event0 is a keyboard
[    59.332] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:13.0/usb2/2-2/2-2:1.0/0003:1C4F:0002.0001/input/input3/event0"
[    59.332] (II) XINPUT: Adding extended input device "SIGMACHIP USB Keyboard" (type: KEYBOARD, id 8)
[    59.332] (**) Option "xkb_model" "pc105"
[    59.332] (**) Option "xkb_layout" "us"
[    59.333] (II) input device 'SIGMACHIP USB Keyboard', /dev/input/event0 is tagged by udev as: Keyboard
[    59.333] (II) input device 'SIGMACHIP USB Keyboard', /dev/input/event0 is a keyboard
[    59.334] (II) config/udev: Adding input device SIGMACHIP USB Keyboard (/dev/input/event1)
[    59.334] (**) SIGMACHIP USB Keyboard: Applying InputClass "libinput keyboard catchall"
[    59.334] (II) Using input driver 'libinput' for 'SIGMACHIP USB Keyboard'
[    59.336] (II) systemd-logind: got fd for /dev/input/event1 13:65 fd 26 paused 0
[    59.336] (**) SIGMACHIP USB Keyboard: always reports core events
[    59.336] (**) Option "Device" "/dev/input/event1"
[    59.336] (**) Option "_source" "server/udev"
[    59.337] (II) input device 'SIGMACHIP USB Keyboard', /dev/input/event1 is tagged by udev as: Keyboard
[    59.337] (II) input device 'SIGMACHIP USB Keyboard', /dev/input/event1 is a keyboard
[    59.337] (II) libinput: SIGMACHIP USB Keyboard: needs a virtual subdevice
[    59.337] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:13.0/usb2/2-2/2-2:1.1/0003:1C4F:0002.0002/input/input4/event1"
[    59.337] (II) XINPUT: Adding extended input device "SIGMACHIP USB Keyboard" (type: MOUSE, id 9)
[    59.337] (**) Option "AccelerationScheme" "none"
[    59.337] (**) SIGMACHIP USB Keyboard: (accel) selected scheme none/0
[    59.337] (**) SIGMACHIP USB Keyboard: (accel) acceleration factor: 2.000
[    59.337] (**) SIGMACHIP USB Keyboard: (accel) acceleration threshold: 4
[    59.338] (II) input device 'SIGMACHIP USB Keyboard', /dev/input/event1 is tagged by udev as: Keyboard
[    59.338] (II) input device 'SIGMACHIP USB Keyboard', /dev/input/event1 is a keyboard
[    59.339] (II) config/udev: Adding input device Logitech USB Receiver (/dev/input/event8)
[    59.339] (**) Logitech USB Receiver: Applying InputClass "libinput keyboard catchall"
[    59.339] (II) Using input driver 'libinput' for 'Logitech USB Receiver'
[    59.340] (II) systemd-logind: got fd for /dev/input/event8 13:72 fd 27 paused 0
[    59.340] (**) Logitech USB Receiver: always reports core events
[    59.340] (**) Option "Device" "/dev/input/event8"
[    59.340] (**) Option "_source" "server/udev"
[    59.341] (II) input device 'Logitech USB Receiver', /dev/input/event8 is tagged by udev as: Keyboard
[    59.341] (II) input device 'Logitech USB Receiver', /dev/input/event8 is a keyboard
[    59.341] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:13.0/usb2/2-4/2-4:1.0/0003:046D:C534.0005/input/input11/event8"
[    59.341] (II) XINPUT: Adding extended input device "Logitech USB Receiver" (type: KEYBOARD, id 10)
[    59.341] (**) Option "xkb_model" "pc105"
[    59.341] (**) Option "xkb_layout" "us"
[    59.342] (II) input device 'Logitech USB Receiver', /dev/input/event8 is tagged by udev as: Keyboard
[    59.342] (II) input device 'Logitech USB Receiver', /dev/input/event8 is a keyboard
[    59.344] (II) config/udev: Adding input device Logitech USB Receiver (/dev/input/event9)
[    59.344] (**) Logitech USB Receiver: Applying InputClass "libinput pointer catchall"
[    59.344] (**) Logitech USB Receiver: Applying InputClass "libinput keyboard catchall"
[    59.344] (II) Using input driver 'libinput' for 'Logitech USB Receiver'
[    59.345] (II) systemd-logind: got fd for /dev/input/event9 13:73 fd 28 paused 0
[    59.345] (**) Logitech USB Receiver: always reports core events
[    59.345] (**) Option "Device" "/dev/input/event9"
[    59.345] (**) Option "_source" "server/udev"
[    59.346] (II) input device 'Logitech USB Receiver', /dev/input/event9 is tagged by udev as: Keyboard Mouse
[    59.346] (II) input device 'Logitech USB Receiver', /dev/input/event9 is a pointer caps
[    59.346] (II) input device 'Logitech USB Receiver', /dev/input/event9 is a keyboard
[    59.346] (II) libinput: Logitech USB Receiver: needs a virtual subdevice
[    59.346] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:13.0/usb2/2-4/2-4:1.1/0003:046D:C534.0006/input/input12/event9"
[    59.346] (II) XINPUT: Adding extended input device "Logitech USB Receiver" (type: MOUSE, id 11)
[    59.346] (**) Option "AccelerationScheme" "none"
[    59.346] (**) Logitech USB Receiver: (accel) selected scheme none/0
[    59.346] (**) Logitech USB Receiver: (accel) acceleration factor: 2.000
[    59.346] (**) Logitech USB Receiver: (accel) acceleration threshold: 4
[    59.347] (II) input device 'Logitech USB Receiver', /dev/input/event9 is tagged by udev as: Keyboard Mouse
[    59.347] (II) input device 'Logitech USB Receiver', /dev/input/event9 is a pointer caps
[    59.347] (II) input device 'Logitech USB Receiver', /dev/input/event9 is a keyboard
[    59.348] (II) config/udev: Adding input device Logitech USB Receiver (/dev/input/mouse1)
[    59.348] (II) No input driver specified, ignoring this device.
[    59.348] (II) This device may have been added with another device file.
[    59.350] (II) config/udev: Adding input device 2.4G 2.4G Wireless Device (/dev/input/event2)
[    59.350] (**) 2.4G 2.4G Wireless Device: Applying InputClass "libinput keyboard catchall"
[    59.350] (II) Using input driver 'libinput' for '2.4G 2.4G Wireless Device'
[    59.351] (II) systemd-logind: got fd for /dev/input/event2 13:66 fd 29 paused 0
[    59.351] (**) 2.4G 2.4G Wireless Device: always reports core events
[    59.351] (**) Option "Device" "/dev/input/event2"
[    59.351] (**) Option "_source" "server/udev"
[    59.352] (II) input device '2.4G 2.4G Wireless Device', /dev/input/event2 is tagged by udev as: Keyboard
[    59.352] (II) input device '2.4G 2.4G Wireless Device', /dev/input/event2 is a keyboard
[    59.352] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:13.2/usb1/1-4/1-4.4/1-4.4:1.0/0003:25A7:2402.0003/input/input5/event2"
[    59.352] (II) XINPUT: Adding extended input device "2.4G 2.4G Wireless Device" (type: KEYBOARD, id 12)
[    59.352] (**) Option "xkb_model" "pc105"
[    59.352] (**) Option "xkb_layout" "us"
[    59.353] (II) input device '2.4G 2.4G Wireless Device', /dev/input/event2 is tagged by udev as: Keyboard
[    59.353] (II) input device '2.4G 2.4G Wireless Device', /dev/input/event2 is a keyboard
[    59.355] (II) config/udev: Adding input device 2.4G 2.4G Wireless Device (/dev/input/event3)
[    59.355] (**) 2.4G 2.4G Wireless Device: Applying InputClass "libinput pointer catchall"
[    59.355] (**) 2.4G 2.4G Wireless Device: Applying InputClass "libinput keyboard catchall"
[    59.355] (II) Using input driver 'libinput' for '2.4G 2.4G Wireless Device'
[    59.356] (II) systemd-logind: got fd for /dev/input/event3 13:67 fd 30 paused 0
[    59.356] (**) 2.4G 2.4G Wireless Device: always reports core events
[    59.356] (**) Option "Device" "/dev/input/event3"
[    59.356] (**) Option "_source" "server/udev"
[    59.357] (II) input device '2.4G 2.4G Wireless Device', /dev/input/event3 is tagged by udev as: Keyboard Mouse
[    59.357] (II) input device '2.4G 2.4G Wireless Device', /dev/input/event3 is a pointer caps
[    59.357] (II) input device '2.4G 2.4G Wireless Device', /dev/input/event3 is a keyboard
[    59.357] (II) libinput: 2.4G 2.4G Wireless Device: needs a virtual subdevice
[    59.357] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:13.2/usb1/1-4/1-4.4/1-4.4:1.1/0003:25A7:2402.0004/input/input6/event3"
[    59.357] (II) XINPUT: Adding extended input device "2.4G 2.4G Wireless Device" (type: MOUSE, id 13)
[    59.358] (**) Option "AccelerationScheme" "none"
[    59.358] (**) 2.4G 2.4G Wireless Device: (accel) selected scheme none/0
[    59.358] (**) 2.4G 2.4G Wireless Device: (accel) acceleration factor: 2.000
[    59.358] (**) 2.4G 2.4G Wireless Device: (accel) acceleration threshold: 4
[    59.359] (II) input device '2.4G 2.4G Wireless Device', /dev/input/event3 is tagged by udev as: Keyboard Mouse
[    59.359] (II) input device '2.4G 2.4G Wireless Device', /dev/input/event3 is a pointer caps
[    59.359] (II) input device '2.4G 2.4G Wireless Device', /dev/input/event3 is a keyboard
[    59.360] (II) config/udev: Adding input device 2.4G 2.4G Wireless Device (/dev/input/mouse0)
[    59.360] (II) No input driver specified, ignoring this device.
[    59.360] (II) This device may have been added with another device file.
[    59.361] (II) config/udev: Adding input device saa7134 IR (LifeView FlyVIDEO30 (/dev/input/event7)
[    59.361] (**) saa7134 IR (LifeView FlyVIDEO30: Applying InputClass "libinput keyboard catchall"
[    59.361] (II) Using input driver 'libinput' for 'saa7134 IR (LifeView FlyVIDEO30'
[    59.362] (II) systemd-logind: got fd for /dev/input/event7 13:71 fd 31 paused 0
[    59.362] (**) saa7134 IR (LifeView FlyVIDEO30: always reports core events
[    59.362] (**) Option "Device" "/dev/input/event7"
[    59.362] (**) Option "_source" "server/udev"
[    59.363] (II) input device 'saa7134 IR (LifeView FlyVIDEO30', /dev/input/event7 is tagged by udev as: Keyboard
[    59.363] (II) input device 'saa7134 IR (LifeView FlyVIDEO30', /dev/input/event7 is a keyboard
[    59.363] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.4/0000:05:0a.0/rc/rc0/input10/event7"
[    59.363] (II) XINPUT: Adding extended input device "saa7134 IR (LifeView FlyVIDEO30" (type: KEYBOARD, id 14)
[    59.363] (**) Option "xkb_model" "pc105"
[    59.363] (**) Option "xkb_layout" "us"
[    59.364] (II) input device 'saa7134 IR (LifeView FlyVIDEO30', /dev/input/event7 is tagged by udev as: Keyboard
[    59.364] (II) input device 'saa7134 IR (LifeView FlyVIDEO30', /dev/input/event7 is a keyboard
[    59.364] (II) config/udev: Adding input device PC Speaker (/dev/input/event6)
[    59.365] (II) No input driver specified, ignoring this device.
[    59.365] (II) This device may have been added with another device file.
[    59.421] (**) SIGMACHIP USB Keyboard: Applying InputClass "libinput keyboard catchall"
[    59.421] (II) Using input driver 'libinput' for 'SIGMACHIP USB Keyboard'
[    59.421] (II) systemd-logind: returning pre-existing fd for /dev/input/event1 13:65
[    59.421] (**) SIGMACHIP USB Keyboard: always reports core events
[    59.421] (**) Option "Device" "/dev/input/event1"
[    59.421] (**) Option "_source" "_driver/libinput"
[    59.421] (II) libinput: SIGMACHIP USB Keyboard: is a virtual subdevice
[    59.421] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:13.0/usb2/2-2/2-2:1.1/0003:1C4F:0002.0002/input/input4/event1"
[    59.421] (II) XINPUT: Adding extended input device "SIGMACHIP USB Keyboard" (type: KEYBOARD, id 15)
[    59.421] (**) Option "xkb_model" "pc105"
[    59.421] (**) Option "xkb_layout" "us"
[    59.422] (**) Logitech USB Receiver: Applying InputClass "libinput pointer catchall"
[    59.422] (**) Logitech USB Receiver: Applying InputClass "libinput keyboard catchall"
[    59.422] (II) Using input driver 'libinput' for 'Logitech USB Receiver'
[    59.422] (II) systemd-logind: returning pre-existing fd for /dev/input/event9 13:73
[    59.422] (**) Logitech USB Receiver: always reports core events
[    59.422] (**) Option "Device" "/dev/input/event9"
[    59.422] (**) Option "_source" "_driver/libinput"
[    59.422] (II) libinput: Logitech USB Receiver: is a virtual subdevice
[    59.422] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:13.0/usb2/2-4/2-4:1.1/0003:046D:C534.0006/input/input12/event9"
[    59.422] (II) XINPUT: Adding extended input device "Logitech USB Receiver" (type: KEYBOARD, id 16)
[    59.422] (**) Option "xkb_model" "pc105"
[    59.422] (**) Option "xkb_layout" "us"
[    59.422] (**) 2.4G 2.4G Wireless Device: Applying InputClass "libinput pointer catchall"
[    59.422] (**) 2.4G 2.4G Wireless Device: Applying InputClass "libinput keyboard catchall"
[    59.422] (II) Using input driver 'libinput' for '2.4G 2.4G Wireless Device'
[    59.422] (II) systemd-logind: returning pre-existing fd for /dev/input/event3 13:67
[    59.423] (**) 2.4G 2.4G Wireless Device: always reports core events
[    59.423] (**) Option "Device" "/dev/input/event3"
[    59.423] (**) Option "_source" "_driver/libinput"
[    59.423] (II) libinput: 2.4G 2.4G Wireless Device: is a virtual subdevice
[    59.423] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:13.2/usb1/1-4/1-4.4/1-4.4:1.1/0003:25A7:2402.0004/input/input6/event3"
[    59.423] (II) XINPUT: Adding extended input device "2.4G 2.4G Wireless Device" (type: KEYBOARD, id 17)
[    59.423] (**) Option "xkb_model" "pc105"
[    59.423] (**) Option "xkb_layout" "us"



On Sunday, August 4, 2019, 11:37:07 PM GMT+8, David Wright <[hidden email]> 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.


Reply | Threaded
Open this post in threaded view
|

Re: where is my disk space

Pascal Hambourg-2
Le 04/08/2019 à 22:56, Long Wind a écrit :
>   the file is more than 3 G, i can't read it with nanoi have 3 G memory, no swap

You do not use an *editor* to *read* a file, you use a pager such as
more, less, most...

> 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
>
> below is Xorg.0.log:

This one is normal.

Reply | Threaded
Open this post in threaded view
|

Re: where is my disk space

David Wright-3
In reply to this post by Long Wind-2
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 <[hidden email]> 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.

Reply | Threaded
Open this post in threaded view
|

Re: where is my disk space

Long Wind-2
Thank David!
it seems it's bug of X

 tail -100 .local/share/xorg/Xorg.1.log

[ 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 <[hidden email]> 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 <[hidden email]> 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.

Reply | Threaded
Open this post in threaded view
|

Re: where is my disk space

davidson-2
On Mon, 5 Aug 2019, Long Wind wrote:

> Thank David!it seems it's bug of X
>  tail -100 .local/share/xorg/Xorg.1.log

To me it looks like the log below is telling you that your power key
was either being held down or stuck in that position.

That is all.

>
> [ 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 <[hidden email]> 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 <[hidden email]> 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.
>
>
--
  The day will come              |  Last words, August Spies (1855--1887).
  When our silence will be       |  Hanged, by the U.S. state of Illinois,
  More powerful than             |  alongside fellow journalists
  The voices you strangle today  |  Adolf Fischer and Albert Parsons.
Reply | Threaded
Open this post in threaded view
|

Re: where is my disk space

Curt
On 2019-08-05, davidson <[hidden email]> wrote:
>
> To me it looks like the log below is telling you that your power key
> was either being held down or stuck in that position.
>
> That is all.

Whatever libinput is trying to say is apparently repeated to the point
where I would consider the repetition itself to be a form of bug,
whether the power key is going haywire or not (which Long doesn't
mention as a vector of particular concern).

So if the power key goose is wild (or "fixing" the incriminated key is
impractical for one reason or another), how do we get libinput to shut
its redundant trap?

>>
>> [ 21261.465] (EE) libinput bug: Key count for KEY_POWER reached abnormal values


--
“We are all in the gutter, but some of us are looking at the stars.”
― Oscar Wilde, Lady Windermere's Fan

Reply | Threaded
Open this post in threaded view
|

Re: where is my disk space

David Wright-3
On Mon 05 Aug 2019 at 16:33:29 (-0000), Curt wrote:

> On 2019-08-05, davidson <[hidden email]> wrote:
> >
> > To me it looks like the log below is telling you that your power key
> > was either being held down or stuck in that position.
> >
> > That is all.
>
> Whatever libinput is trying to say is apparently repeated to the point
> where I would consider the repetition itself to be a form of bug,
> whether the power key is going haywire or not (which Long doesn't
> mention as a vector of particular concern).

#define KEY_POWER     116    /* SC System Power Down */

doesn't give me much of a clue as to what sort of power key this is,
but from the company is keeps I'd guess it might be for powering
down a Sound Card. We know the OP watches TV through a sound card,
and has wished to shut it up when the computer is switched off.
Perhaps it's something to do with that.

As for key repetition: the OP has communicated here on this topic
before. Could the problem be self-inflicted: it wouldn't necessarily
be noticed if only Xorg.0.log grew, because restarting X would clean
the directory of all but two generations. However, that third file,
Xorg.1.log, is not going to get cleaned until a second simultaneous
X server has been run twice. The lack of any Xorg.1.log.old suggests
that this is not the OP's habit.

> So if the power key goose is wild (or "fixing" the incriminated key is
> impractical for one reason or another), how do we get libinput to shut
> its redundant trap?

That depends. If you can't restart X because of what's running, one
method might be to chattr +i, though that leaves a large file in
place which might mean moving things around to make room.

If the problem keeps recurring, but you don't want to have to fix it
in haste, then you could try linking ~/.local/share/xorg to a small
spare partition that you can allow to fill up. If you're running
Xserver as root, you can set -logfile there instead.

You might try experimenting with -logverbose which defaults to 3.
No idea what range of values might be allowed or suitable.

Cheers,
David.

12