[clug] Diagnosing display freeezes

[Hal Ashburner]

On 29 January 2015 at 18:40, Scott Ferguson
<scott.ferguson.clug at gmail.com> wrote:

>
> And... if something is awry and filling the xsession-error log, that'd
> be the first place I'd look for hints - though I presume in this
> instance the OP would have already done so (as well as other logs).
>
>
> Centos 7 is systemd??

Yep. Pretty ignorant of (the controversial) systemd at this stage.


> /var/log/journal can grow too large for the allocated space if
> SystemMaxUse= is not set correctly (but that normally just results in a
> freeze rather than intermittent freezes)

no /var/log/journal
the entire contents of /var/log are 1.5G, mostly messages* 40G
available. local flash drive with LVM indirection.


> Perhaps the following may show something not in the logs:-
> systemctl --state=failed

[hal at davis 18:49 ~] systemctl --state=failed --all
UNIT            LOAD   ACTIVE SUB    DESCRIPTION
network.service loaded failed failed LSB: Bring up/down networking
rngd.service    loaded failed failed Hardware RNG Entropy Gatherer Daemon

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.

2 loaded units listed.
To show all installed unit files use 'systemctl list-unit-files'.

hmm, clearly my networking is functioning.


>
> The only similar errors I've had that 'might' be relevant were dbus
> errors (KDE Plasma) - which would occasionally cause the mouse to freeze
> (permanently) and the lights on the keyboard to flash.

Sounds like a different symptoms, but thanks for the clue concerning
dbus, something else for hypotheses.