On 01/27/18 13:05, InvalidPath wrote:
I'm about to go down your list here and fill you, and everyone
else in:
_ "Are you getting a login display?"_ No.
When I replaced the symlink with one pointing to sddm.service and rebooted I got a
solid black screen with no keyboard input being accepted and no mouse cursor
either. It did the exact same thing when I tried LightDM too.
_And auid=1000 is "actual user ID" which is the numeric ID of the user
contained in
the /etc/passwd file.
So, one of two things can be happening. Either one is getting a login screen and
typing in a password *or* at some point the system has been configured for
"auto-login"_
The AUID of 1000 is my user, bhart. And no, nothing configured for auto-login.
You say you're not getting a Login GUI and you say nothing is set for auto-login. It
just boots to a blank screen. With that being the case, I can't for the life of me
think how this can be in the logs you've posted.
Jan 25 19:50:19 Vostok sddm-helper[1937]: pam_unix(sddm:session): session opened for
user bhart by (uid=0)
Jan 25 19:50:19 Vostok audit[1937]: USER_START pid=1937 uid=0 auid=1000 ses=2
subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:session_open
grantors=pam_selinux,pam_loginuid,pam_selinux,pam_keyinit,pam_namespace,pam_keyinit,pam_limits,pam_systemd,pam_unix,pam_gnome_keyring,pam_kwallet5,pam_kwallet,pam_lastlog
acct="bhart" exe="/usr/libexec/sddm-helper" hostname=? addr=?
terminal=:0 res=success'
Jan 25 19:50:19 Vostok sddm-helper[1937]: pam_kwallet5(sddm:session): pam_kwallet5:
pam_sm_open_session
Jan 25 19:50:19 Vostok sddm-helper[1937]: pam_kwallet5(sddm:session): pam_kwallet5:
final socket path: /run/user/1000/kwallet5.socket
Jan 25 19:50:19 Vostok sddm-helper[1937]: pam_kwallet(sddm:session): pam_kwallet:
pam_sm_open_session
Jan 25 19:50:19 Vostok sddm-helper[1937]: pam_kwallet(sddm:session): pam_kwallet:
final socket path: /run/user/1000/kwallet.socket
Jan 25 19:50:19 Vostok sddm-helper[1937]: Starting: "/etc/X11/xinit/Xsession
\"env
GNOME_SHELL_SESSION_MODE=classic gnome-session --session gnome-classic\""
_ "Do you have a /var/lib/sddm/state.conf
file. If so, what are the contents." _
_
_
Yes I do, and it's contents*were:*
Last]
# Name of the last logged-in user.
# This user will be preselected when the login screen appears
User=bhart
# Name of the session for the last logged-in user.
# This session will be preselected when the login screen appears.
Session=/usr/share/xsessions/gnome.desktop
Although this is "wrong" since you've said you've removed all gnome bits
it should
not affect things. I found that on a pure KDE system if you login with that info it
will just overwrite the info for the Session with plasma.desktop and bring up KDE.
Also, even if I have bogus entries in the xsession directory it will find that the
Session isn't valid and bring up KDE.
Today I changed that to 'plasma.desktop. but have not rebooted as of yet. I do
question that files usefulness simply because I do not use the Gnome desktop nor do
I interactively select it at the login screen. I compared that to the same file on
my home rig which is also F27 w/Plasma.... it had plasma.desktop already populated.
OK, now you are confusing me....
You say.... "because I do not use the Gnome desktop nor do I interactively select
it
at the login screen". But I asked if you get a Login GUI and you've said no.
Now
you talk of a login screen.
So?
Anyway.... What do you have in /usr/share/xsessions with all of the "gnome
bits"
removed.
The feeling I'm getting is that while you think you've removed all of the gnome
bits
you really haven't and sddm thinks the default DE is GNOME.
I suppose I may try
dnf group remove "Fedora Workstation"
--
A motto of mine is: When in doubt, try it out