I upgraded from Leap 15.3 to 15.4 both via .iso on a flash drive and then again (after duplicating the backup to main OS drive) using zypper dup. Same result.
Everything seems fine. Nice fast boot. 15.4 shows login screen and recognizes my user account. All I have to do is input my password. Therefore Leap 15.4 hangs/freezes and will not log me in.
At the login screen, select a session type other than whatever is your normal type, e.g. IceWM instead of Plasma, or X11 instead of Wayland for Gnome.
Create a virgin user to try logging in with your normal session type. You should be able to use text mode YaST for new user creation via Ctrl-Alt-F3 to reach a shell login prompt. Return to login screen with Alt-F7 or Alt-F1 after finishing with YaST. There’s also a useradd command you could use instead of YaST.
After Ctrl-Alt-F4, login as root, then try startx, just to see whether a session starts at all. Once started, if successful, open a terminal, then run: ]zypper in inxi]inxi -U*]inxi -Faz > 154data1.txt
and exit the startx session. Copy and paste the content of 154data1.txt here if you can manage it. Otherwise, try uploading it thus:```
cat 154data1.txt | susepaste -e 151200
Then paste the resulting URI here.
- After fresh reboot, then failing a normal login, Ctrl-Alt-F5, login as normal user, then[list=1]*]loginctl list-sessions*]loginctl session-status **ID**
, where **ID** is the first ID resulting from list-sessions*]If a lot of output results, repeat with **> 154data2.txt** appended.*]Copy & paste the content of ~/154data2.txt here, if you can, or do **cat ~/154data2.txt | susepaste -e 151200** to upload.
*]After Ctrl-Alt-F6, try logging in as your normal user. If successful, if ~/.xsession-errors exists, copy its content here, or use susepaste as above.[/list]
Thank you very much for a detailed reply. I should have stated I am running KDE as my only desktop manager.
I think KDE is actually working as below but I cannot complete login and formation of a desktop:
I directly boot into the KDE Display Manager (KDM). There is no interim login screen. There is no option for selecting a session type.
CTRL-ALT-F1,2,3,4,5,6,7 etc. has no effect whatsoever in the KDM.
I am easily able to log in as root. KDE desktop appears.
My user account does not have a .xinitrc file. I copied the openSUSE default file .xinitrc.template to .xinitrc. That had no effect.
As root I went to my home directory and on CLI entered $ echo “startkde” > .xinitrc.
This created a .xinitrc with a single line (“startkde”) that changed behavior.
Now in KDM when I enter my user password a login begins to take effect. KDM screen disappears. Arrow appears against black background.
Almost there. Then oops popped back to the KDM again. So close, yet so far.
I tried saving the original .Xauthority to .Xauthority_old and having no .Xauthority. No change. Created a new .Xauthority with (root) $ touch /home/myuser/.Xauthority. No change.
I created a new user account. Same login short circuit behavior for the new user.
I got rid of the NVIDIA driver because its upgrade screwed up my resolution. I could not get the upgraded NVIDIA proprietary driver to work period. As I recall openSUSE did not like the older NVIDIA driver. So I use Nouveau.
The root login does just fine with Nouveau driver.
Also in /etc/default/grub I already set:
[LEFT] GRUB_CMDLINE_LINUX_DEFAULT=“quiet splash nouveau.modeset=0 mem_sleep_default=deep”[/LEFT]
Excuse me no for Leap 15.3 I do not do nomodeset. I did have to fix grub so I could get the computer to sleep. Even after that I am having problems with freezes and crashes on resuming from sleep. But that is another story. I am hoping to leave all that behind for Leap 15.4 if I could only log in.
[LEFT] Leap 15.3 edited for sleep == 2022.02.05 (worked for sleep and SSD resume from sleep)[/LEFT] [LEFT] GRUB_CMDLINE_LINUX_DEFAULT="splash=silent mitigations=auto quiet resume=/dev/sda3 apci_osi=Linux pci=nomsi,noaer[/LEFT]
Thanks
I directly boot into the KDE Display Manager (KDM).
This is highly unlikely. KDM was removed from openSUSE several years ago, after KDE moved from v4 to v5. Very most likely your DM is SDDM, or possibly LightDM, or GDM, or XDM. If you enabled the optional openSUSE Build Service repo for KDE3, then KDM3 would be an option. Is this what you did? What does update-alternatives --query default-displaymanager report?
There is no interim login screen. There is no option for selecting a session type.
This is a common misfortune of having selected automatic login at installation time. When the usual session type is broken, the fallback provided, usually IceWM, is usually unavailable via the login manager.
CTRL-ALT-F1,2,3,4,5,6,7 etc. has no effect whatsoever in the KDM.
Holding down all three, Ctrl, Alt & F3, at once, produces no response, or a black screen?
I am easily able to log in as root. KDE desktop appears.
This statement is inconsistent with your statement of there being no interim login screen. If there is a GUI login screen where you can choose who can login, then there should also be a way to select the session type. The exception is if using XDM rather than any of the others listed above.
My user account does not have a .xinitrc file. I copied the openSUSE default file .xinitrc.template to .xinitrc. That had no effect.
.xinitrc is not relevant to Plasma sessions opened from SDDM, LightDM, GDM, etc. Normal Plasma users don’t need it, and having one may interfere.
As root I went to my home directory and on CLI entered $ echo “startkde” > .xinitrc.
This created a .xinitrc with a single line (“startkde”) that changed behavior.
This may have created an .xinitrc file with root ownership. If so, it needs fixing. All files in your homedir should be owner you, group you.
Now in KDM when I enter my user password a login begins to take effect. KDM screen disappears. Arrow appears against black background.
Almost there. Then oops popped back to the KDM again. So close, yet so far.
So you have a login problem, not a Plasma problem per se. Are there files other than .xinitrc owned by root in your homedir? If yes, correct and try again. If not, use loginctl to attempt to diagnose after creating a virgin normal user with YaST to compare behavior with.
nouveau.modeset=0 equates to nomodeset, which disables KMS for all GPUs, whereas nouveau.modeset=0 only disables KMS for NVidia GPUs. Disabling KMS forces X to run on a fallback driver with severely limited performance.
I logged into 15.4 as root and removed both .Xauthority and .xinitrc files.
ArchLinux Wiki promises removing .Xauthority and then without reboot log into the user account will work.
That did not work. I still get the pre-.xinitrc hang on login.
However permission issues should now be absent.
I also have aliases to simply change ownership & permissions to my user account.
By “interim login screen” I meant some sort of text based login screen. That does not appear prior to the display manager GUI.
Yes I have IceWM installed by default
$ rpm -qa | grep icewm [return]
icewm-1.4.2-15000.7.15.1.x86_64
icewm-default-1.4.2-15000.7.15.1.x86_64
icewm-lang-1.4.2-q15000.7.15.1.noarch
icewm-them-branding-1.2.5-lp154.2.1.noarch
You are correct on KDM of course. I only know what I read on the internet which is often old and overcome by events.
I also typically do the openSUSE default installation process, trusting SUSE knows best.
So no extra SUSE install repos.
States: /usr/lib/X11/displaymanagers/default-display manager
Status = Auto
Best = /usr/lib/X11/displaymanagers/sddm
Value = /usr/lib/X11/displaymanagers/sddm
Alternative: /usr/X11/displaymanagers/console with Priority=5
Alternative: /usr/X11/displaymanagers/sddm with Priority=25 (twice?)
Alternative: /usr/X11/displaymanagers/xdm with Priority = 10
The SDDM Display Manager GUI only displays the following options:
Sleep, Restart, Shutdown, Other = log in with username+password or list users
No SDDM options for changing session.
I never consciously choose automatic login for security reasons, but obviously I do get an automatic seque to SDDM.
On my AMD desktop workstation at issue CTRL-ALT-F# (held down simultaneously) has no resulting behavior for 15.3 or 15.4.
Conversely on my HP Intel laptop running Leap 15.3 that works just fine to pop to a text based login from the SDDM display manager.
Yes this seems to be a login problem not a Plasma problem per se.
I did create a virgin test user. I can’t log into that one either. Same hangup behavior.
Well guess what. Leap 15.4 SDDM is apparently buggy for logins.
As root I booted the YaST GUI (Miscellaneous->Alternatives) and chose XDM as the display manager. That did not go well. Leap 15.4 gave me the bad swirly circle and refused to boot.
Re-cloned the Leap 15.4 OS drive from backup. I cannot praise hard drive cloners enough. You can play and not die if you screw up.
This time logged into 15.4 as root and did the Superuser Terminal (another great app) CLI solution:
I get a simple text choice. I entered the number corresponding to XDM display manager.
Then in an abundance of caution I tried to enable XDM:
$ systemctl.enable xdm.service
Leap 15.4 just complained and refused to do it. Oh well. Then:
$ systemctl.restart xdm.service
That took me directly to the XDM display manager. I was able to log in as my user with no problem. KDE desktop for Leap 15.4 is a little different but nothing serious.
Overall very encouraging. So reboot time.
On reboot XDM came up as the display manager. I was perfectly able to log in as my user. Yay! I have an openSUSE upgrade future. Life is good again.
I would not call XDM pretty. It is just a gray screen with a single feature of user login.
I would not call XDM full featured. There are no display manager options for sleep, restart or shutdown.
Now that you are familiar with update-alternatives --config default-displaymanager, you might want to try switching to something else, to see if switching to XDM corrected whatever the problem was with what you had been using. That had to be some sort of I/O problem, given the wholesale failure to get expected results from your keyboard.
Note nomodeset is for testing only few would want to run that way normally. Essentially it will tell you if the current video driver is the source of your problems
Thus far no problems booting. I had a prior issue with a green screen with 3 green dots showing up instead of SDDM.
Thence power off & reboot sometimes several times until something in the computer gets it right. I suspect SDDM is just buggy.
Spent some time googling the comparisons and configurations of display managers. I am looking at installing LightDM or KDM if that is still being supported.
It would be nice to choose a desktop/session option from the DM.
Thanks again for your direction and help. It made all the difference.
Definitely not good. You might try force reinstalling input packages:
sudo zypper in -f libinput-udev libinput10 libxcb-xinput0
Spent some time googling the comparisons and configurations of display managers. I am looking at installing LightDM or KDM if that is still being supported.
KDM is not officially supported. KDM3 does remain available by enabling the KDE3 BS repo. I never stopped using it on my primary PC.
It would be nice to choose a desktop/session option from the DM.
This is a normal function of all DM’s I’ve ever used, except for XDM.
Quit YaST2 and went to zypper. Refreshed the repos. The new repo was refreshed.
$ zypper in KDM3 did not work. Also tried $ zypper in KDM which also did not work.
I was able to add lightdm display manager via YaST2 and rebooted into LightDM display manager with no problem (and unlike SDDM it even lets me log in).
Where does openSUSE stow the configuration files for display managers, e.g. XDM and LightDM?
$ locate XDM does not work (I saw it on the internet)
$ which XDM just points back to /usr/lib/X11/displaymanagers which is not much help.
Where does openSUSE stow the configuration files for display managers, e.g. XDM and LightDM?
Each has its own location(s) usually in /etc/. KDM3 is an exception. LightDM is in /etc/lightdm/. man lightdm
$ locate XDM does not work (I saw it on the internet)
$ which XDM just points back to /usr/lib/X11/displaymanagers which is not much help.
Linux filesystems are case sensitive.
# locate xdm | wc -l
435
# which xdm
/usr/bin/xdm
# which lightdm
/usr/sbin/lightdm
# which kdm
/opt/kde3/bin/kdm
# ls -Gg /opt/kde3/share/config/kdm/kdmrc
-rw-r--r-- 1 22694 Jun 3 19:09 /opt/kde3/share/config/kdm/kdmrc
LightDM:
/etc/lightdm is an empty file when I read it in Kate. How to configure that?
/usr/sbin/lightdm is not an ascii file. It not obvious how to edit or configure. It looks like an executable. I expect */sbin/ files are executables.
XDM
/usr/bin/xdm is presumably an executable not a config file. Kate does not bring up an editable configuration file.
You might try force reinstalling input packages: