On 02/08/18 23:57, Dave Close wrote:
Ed Greshko wrote:
> On 02/08/18 19:30, Patrick O'Callaghan wrote:
>> I think you said that Gnome does start but KDE doesn't, so it's likely
>> that something in the KDE config is causing the problem.
> Well, unless GNOME is using Wayland?
The way I read the release notes, it is. Though there apparently is a
way to override and force it back to X. I haven't tried, mostly because
I really don't like Gnome so I avoid it.
> But, one should try creating another user and then try starting
> KDE on that new pristine account.
I've done that without any change.
Hummm.... Very odd....
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.
These are the systemd-logind lines in my file on a VM.
[egreshko@f27k xorg]$ grep systemd-logi Xorg.0.log
[ 85.105] (II) systemd-logind: took control of session
/org/freedesktop/login1/session/_31
[ 85.111] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 11 paused 0
[ 85.644] (II) systemd-logind: got fd for /dev/input/event0 13:64 fd 19 paused 0
[ 85.650] (II) systemd-logind: got fd for /dev/input/event1 13:65 fd 22 paused 0
[ 85.651] (II) systemd-logind: got fd for /dev/input/event5 13:69 fd 23 paused 0
[ 85.658] (II) systemd-logind: got fd for /dev/input/event6 13:70 fd 24 paused 0
[ 85.713] (II) systemd-logind: got fd for /dev/input/event4 13:68 fd 25 paused 0
[ 85.723] (II) systemd-logind: got fd for /dev/input/event2 13:66 fd 26 paused 0
[ 85.729] (II) systemd-logind: got fd for /dev/input/event3 13:67 fd 27 paused 0
[ 4965.630] (II) systemd-logind: releasing fd for 13:67
[ 4965.936] (II) systemd-logind: releasing fd for 13:66
[ 4965.940] (II) systemd-logind: releasing fd for 13:68
[ 4966.008] (II) systemd-logind: releasing fd for 13:70
[ 4966.012] (II) systemd-logind: releasing fd for 13:69
[ 4966.015] (II) systemd-logind: releasing fd for 13:65
[ 4966.022] (II) systemd-logind: releasing fd for 13:64
I suppose you could try with selinux disabled as this appears to be a system-wide
issue as opposed to a use configuration issue. I've upgraded several systems without
issue. The HW in my case is all nVidia.
Probably should ask as well on the KDE list.
--
A motto of mine is: When in doubt, try it out