[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: where is my disk space



On Mon 05 Aug 2019 at 16:33:29 (-0000), Curt wrote:
> On 2019-08-05, davidson <davidson@freevolt.org> 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.


Reply to: