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.
>
> I suppose you could try with selinux disabled as this appears to
> be a system-wide issue as opposed to a use configuration issue.
SElinux is disabled.
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.
Searching for references to that AIGLX message, I find several
reports, some going back a few years. The solutions are things like
installing a different GUI so they aren't very helpful.
But it certainly does look like the systemd-logind pause is stuck
and could be the cause of my problem.
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.
--
Dave Close, Compata, Irvine CA +1 714 434 7359
d...@compata.com dhcl...@alumni.caltech.edu
"There are now so many exceptions to the Fourth Amendment that
it operates only by accident." --William Hugh Murray, 2013
_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
