On Fri, Jan 26, 2018 at 10:05 PM, InvalidPath <invalid.path@xxxxxxxxx> wrote:
On Fri, Jan 26, 2018 at 4:36 PM, Ed Greshko <ed.greshko@xxxxxxxxx> wrote:______________________________On 01/27/18 04:41, InvalidPath wrote:
> So tonight, I guess I should try again.. maybe remove and reinstall sddm and I'd
> firstly think that installing a few other DM's would be a good idea but then I'm
> left with so many other dependencies that I'd be in the same boat as now. So am I
> correct in thinking that reinstalling sddm, I will retry the enable command and see
> if the results are different this time.. and if greeted with a black screen then
> journalctl should be my friend.. Oh and also check that state.conf file to make
> sure it's not still pointing to GDM... Is this a solid plan?
I apologize, sort of, for the diatribe which follows. Please understand that it is a
general rant while, unfortunately, using examples from this thread.
A solid plan would be to answer *specific* questions with *specific* answers to those
trying to assist.
I speak only for myself. When I ask a question I ask it with a foundation. I may,
or may not, go into detail as to the foundation behind my question. The reason for
that is the foundation may be complex and time consuming to write out. And, I have
found that many people aren't interested in the ramblings of my thought process they
are only interested in results.
With that in mind, here is an example.
I asked the simple, yes or no question. "Are you getting a login display?" I did
layout a brief foundation behind my question. Maybe I should have added that in
looking at the logs I also saw...
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,pa m_namespace,pam_keyinit,pam_li mits,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=sucess`
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 answer to the question "Are you getting a login display?" resolves that. And
that question remains unanswered.
I also asked the question (paraphrased here) "Do you have a /var/lib/sddm/state.conf
file. If so, what are the contents." A specific question which would have a
specific answer along the lines of....
[root@acer ~]# cat /var/lib/sddm/state.conf
[Last]
# Name of the last logged-in user.
# This user will be preselected when the login screen appears
User=egreshko
# Name of the session for the last logged-in user.
# This session will be preselected when the login screen appears.
Session=/usr/share/xsessions/plasma.desktop
I can only guess what is in it since you used words to indicate there may be Gnome
stuff in it. Then my advice would probably have been to either delete the file or
change the "Session" contents. I *also* would have gone on to explain that erasing
and re-installing the sddm package would probably *not* remove that file. That file
is *not* supplied by the package but created by running sddm and those types of
"info" files are generally not removed. So, an erase/install would be ineffective.
You have added a message to this thread talking about "system-switch-displaymanager
<https://apps.fedoraproject.org/packages/system-switch-displ >". Thataymanager
command is nothing more than a shell script. And, an unnecessary one at that. The
bottom line is that it performs two commands.
rm -f /etc/systemd/system/display-manager.service
systemctl enable $DM.service
This is, in effect, the same as "systemctl -f enable sddm". If that command
"fails" to do what it is intended to do and doesn't provide an error message would be
a source of concern to me.
Sorry for the rambling nature of the above. Full disclosure, I was out late last
night eating and drinking. With the emphasis on drinking. I woke up early as I
needed to. So, I am not hung-over since I still have plenty of alcohol in my
bloodstream.
--
A motto of mine is: When in doubt, try it out
_________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@lists.fedoraproject.org
Lol Ed.. Don't worry about it, I have my big boy pants on. I do tend to jump around easily, pose questions, try things.. I'm not a person who sends a question upstream then just waits for replies before I try stuff, never have been and never will be. Although in saying that I do take suggestions strongly and try to be as verbose as I can, admittedly though sometimes I give as much info as I think is required. Which might be what I did to you (actually regarding the state.conf file I *DID* ).. honestly today at work was horrid and I was trying to multitask a bit too much. In addition, it feels as though the others have given up so I thank you for sticking in there with me, even if it is to rant a bit, lol.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."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
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.And with regards to system-switch-displaymanager.. I assumed it was a simple script.Now in addition to all of this, I opened the lid from a systemctl suspend leaving work today.. I just opened the lid and was greeted with a black screen. I held down the power button to turn it off. Then booted into rescue mode, I verified the contents of teh state.conf file as still pointing to sddm.service, then ran a sudo systemctl enable sddm.service and this time I did not give me an error. I then attempted to start that service which prompted me for my password in a gui window but then afterwards nothing happened. I decided to reboot and I'm back at the black screen/keyboard lock issue.I really, really wish this thing would work like it should.
Any other suggestions? I think I've proven sufficiently enough that the normal method is not working in this case..
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
