On 02/08/2018 09:26 PM, Dave Close wrote:
Ed Greshko wrote:
> Looking at your Xorg.0.log I see this at the end.
> [ 221.964] (II) AIGLX: Suspending AIGLX clients for VT switch
> [ 222.058] (II) systemd-logind: got pause for 13:65
> [ 222.058] (II) systemd-logind: got pause for 13:69
> [ 222.059] (II) systemd-logind: got pause for 13:64
> [ 222.059] (II) systemd-logind: got pause for 226:0
> [ 222.059] (II) systemd-logind: got pause for 13:66
> [ 222.059] (II) systemd-logind: got pause for 13:67
> [ 222.059] (II) systemd-logind: got pause for 13:68
> You should check on your working system what you get. I don't
> have any of those types of pause messages.
That's because you aren't switching to a different console to read the log.
On the working system, the above messages are followed by
[ 72483.987] (II) AIGLX: Resuming AIGLX clients after VT switch
I'm not switching consoles. I haven't yet reached the opportunity
to do so when the system hangs and the black screen appears. After
that, yes, I can and do switch to a text console so I can kill the
hung KDE session.
You do switch consoles and you just again said you did. You switched
consoles and then killed the session. I get those same messages when I
switch to a text console and then back again. Those messages are normal
and not a problem.
But it certainly does look like the systemd-logind pause is stuck
and could be the cause of my problem.
Try switching back to the "stuck" X session, wait 10 seconds, and then
switch back again to the console. See what is in the log. I bet you
will see the logind resume and the AIGLX resume messages.
Have I mentioned that I installed TigerVNC on the system, then
connected from a different one? In that situation, KDE starts fine.
The problem is only on the main screen.
This starts the session differently. How are you starting vnc and KDE
in this case. That might give a hint to why the other method isn't working.