Default login fails

During boot I was getting

Failed to start UID <root ID>

(I presume it was root ID, since it was neither my personal nor test UID)
That was with releases immediately prior to OpenSUSE-release 20250714-3602.1
I had to resort to logging in using the recovery version.

Now, with OpenSUSE-release 20250714-3602.1 I get

Failed to start XDisplay Manager'
Failed to start Postfix mail Transport Agent
login:

However, login with myuser or root returns the error

no shell. Permission denied

As a result, login via recovery continues to be necessary. How can I correct this? Or, alternatively, setting the recovery option to default would be helpful. But how?

As the UID of root is 0, I assume you would have noticed that.

According to the GNOME System monitor, user IDs for root processes start at 1 and go up into the thousands, so I was supposing it was one of those, not the root user itself.
The UID that failed was a 3-digit number, which is within the range of the root process IDs…

I assume your are confusing

  • UID, that is the numeric identification of a user, they are to be found in the third field of /etc/passwdentries.
  • PID, that is the process identification, also a number, it starts with 0 which is the kernel itself and which you will not see mentioned in listings. Then PID 1 is the process started by the kernel after boot is complete and that is in modern Linux system /usr/lib/systemd/systemd and from that one all other processes are started as children, grand-children and so on.

So, UID and PID are certainly very different things. Even so that every PID is owned by a UID.

Well, the 3-digit number in the boot-up message was definitely identified as a UID, (not a PID). I have no 3-digit UIDs

There ae a lot of processes that ar started by (phantom) user ids less then 1000.

You definitely have…they are system users.

I think you are long enough here on the forums to know that we do not accept peoples conclusions, but that we want to see the system output (that made you draw the conclusions) so that we can draw our own conclusions. In this case e.g.

cat /etc/passwd

You definitely have…they are system users.
[/quote]

Sorry. I was referring to the user list shown under YaST ‘User and Group Management’
The message, we are discussing now does not appear any more after the referenced newer release. It is replaced by the two newer ones from post #1.

Which app provides the listing you show?[quote=“hui, post:7, topic:186575, full:true”]

My screenshot is from YaST ‘User and Group Management’. You only need to set the filters properly to see all users including system users.

…oops…got it! Thanks.

And please, understand that the term “system users” used for users with UID < 1000 is only a convention. The system itself (the Kernel) does not know anything about this. This convention is rather old. It is a habit inherited by generations of system managers. The idea is to separate the users that are there for running several system programs/daemons from the real “end users”. Long ago the border was drawn at UID < 500, but the growing number of system users lead to the new convention.
And while the system itself does not care, the convention is implemented in some tools, like you can see in YaST > Users and Groups.

…getting back to the actual problem…

Do I have to live with the situation that login is not possible from the default system because these two processes do not start? Or could I make the recovery system my default?

Why not searching e.g. the journal (in recovery mode), why these processes fail?

How? Where should I find the failed boot log?

Problem persists in OpenSUSE Tumbleweed release 20250716-3606.1

By the way, after installing the above release manually, prior to selecting restart, (and forgetting to uncheck the restart/install flag) my system went into an endless restart cycle,

Where will I find the failed boot log? What should I look for?

This is an introduction for journalctl:

…but has is not evident in release 20250717-3608.1

It seems that the problem is solved for me!! Many thanks for your help!

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.