Leap 42.1 login problem

While booting Leap 42.1, my root password always fails. Using the rescue disk to re-emphasize or rename the root passwd, still unable to login as root with known password. Any ideas?


I am not 100% on this, but it did happen to me previously where root access got borked when I changed root’s password.

Not much you can do if you have no root access - I had to use snapper to roll back to a working state.

My suspicion is that it was a conflict between the different user and root passwords, and the “User’s passwords is root’s” setting. I could not and cannot verify this however.
If it broke after changing roots password, try unchecking the “use this users password for root” option and THEN change root’s password.
I have been meaning to try this but in the midst of upgrading :slight_smile:

You should never ever log into a GUI as root. It is never needed and doing so can bork your system.

Does root work else where??

Weird. While booting, I am never asked for password. I suppose that would happen if it went into emergency mode (as when I was running the beta1 release).

Using the rescue disk to re-emphasize or rename the root passwd, still unable to login as root with known password.

I haven’t heard of “re-emphasize” applied to password. And “rename” seems as if it should mean something other than changing the password.

But I’ll guess that you just mean changing the password to what you already thought it was.

It does sound as if you are trying to login to the GUI (graphic desktop). I think that’s not allowed in a standard configuration, though perhaps it depends on the login manager being used. In any case it is not needed and, arguably, unwise.

New question: Is it possible to boot to a console rather than a KDE desktop or any desktop? If yes, what would be the procedure?


Jet Driver


at boot screen press e find the line starting linux or linuxefi go to true end (it wraps) add a space and 3 press F10 to continue boot to terminal

Disregard new question. Have answer. Thanks to all of you for your help. Over and out.

Is this your opinion, or is this a Suse problem?

I’ve done this with several distros since about 2002. And I’ve had Suse 13.2 with a root login with GUI.

Frankly, I find GUI easier to use than command line mode/interface.

BTW – I do z/Frames. I stopped doing TSO native DECADES ago. I can probably still install z/OS. Now Hercules with MVS 3.8J – need to remember how to use TSO native and TSO Edit.

So, not new to computers. Not new to SUSE. I just think that this has become a stock standard answer and no one can back it up with what exactly goes wrong – it’s OWT.

No the problem is with all Unix GUIs. Any GUI is messing with stuff in the back ground when it happens to do so in a user area the ownership of files can change. This happens without user intervention. the most common problem is with ~/.Xathority and ~/.ICEathority.not to mention it being a basic security no no. If those files ownership changes the user can not log into his home.

No problem to run a program as root it is logging into the GUI that can cause the problem. There is never a need to do so I have not logged in as root for years and have no problem. Back when when I did sometimes do that I did have problems because of it until I was enlightened. Some destroy do not by default have a root account thus the problem is not there unless you create a true root user. Ubuntu and family. Logging into a terminal as root is also no problem it is the nature of the GUI that causes the problem and it has been around since Unix first got GUIs

Your machine do as you like but we like to always warn so others might not think it was a good idea.

Good Evening,

As often in life, what is good for one is not good for another. I have been using SuSE and SUSE since the '90 on both x86_64 and s390x and I’d say at least once a week I’d access my trusty KDE with root. I am sure access via the GUI has never “bork” my system, it has been “bork” quite often with root line command access. The GUI dose offer a certain amount of security, not done via the command line.

Access via a GUI will always offer a security level better than the command line, less typo and less wrong commands at the wrong time.

For some oddball reason LEAP seems to have a bad hair day on allowing root to logon / login. It’s been Okay for 20 odd years, why now ?


The point is that new users see that someone says it is OK but it really is not and can get new users into trouble. If you only deal with system stuff when logged in then all is ok but you start browsing in the home directories and the GUI may take it upon itself to modify those hidden files to it’s own ownership. This breaks the that users login. I know, been there done that back in 10.1. Suddenly your user can not log until you go in and change the files back to the user’s ownership.

Your machine your rules but we wish not to encourage it for those that may not understand how to recover.