"Do not know how to create missing GreeterUID user kdm"

I get this message any time I try to upgrade KDM. I’ve found several other forums where this error was posted, but I haven’t found a solution to it. I’ve tried backing up and removing /usr/share/kde4/config/kdm/kdmrc to see if it would regenerate, but it didn’t work. Any ideas?

First, as we are not clairvoyant, please allways tell which version of openSUSE you use. Then, we can deduct from you talking about KDM, that you use KDE. But it never hurts to tell this also when you ask something.

Then I have tried to understand who that user Bash is that you quote. But then it cam to my mind that it is part of the computer text in a terminal session. Please put such terminal text between CODE tags (you get them by clicking on the ## button in the toolbar aboce the post editor). And then please complete. That is the prompt, the command you use, the output up until and inclusing the next prompt. It wil tell us much more in most circumstances. In this case it could e.g. explain what you do to “upgrade KDM”.

This message has always been there since upgrading to 12.2 if the splash screen
is changed from the default (maybe it was there on earlier versions)

After each kernel or kdm change the install script can only handle the default,
hence the message & it then defaults to the blue vertical graphic

No functional loss has been noticed after this message occurs

Hi. How are you?

Thank you. This was exactly the answer I was looking for.

In any case, I’m using Tumbleweed, and I was upgrading KDM (maybe upgrade doesn’t quite make sense here—my background is in aptitude upgrade-ing packages) using this command:

sudo zypper up kdm

I did this in an attempt to get out of dependency hell before I realized that it was a common occurrence with Tumbleweed. I’m not getting this message anymore anyway.

Next time you have a Tumbleweed question, please post that in the Tumbleweed subforum.
There is more change you meet people with Tumbleweed experience there. After all that is where we created that subforum for.