Can't login if UID is greater than 7354396 and displaymanager ist kdm, openSUSE 13.1

Hi,

problem is that users with a UID greater than 7354396 can’t login if the
displaymanager is kdm.
gdm, terminal, ssh works fine, but not kdm.

/var/log/messages:


2014-02-05T14:47:30.041820+01:00 xyz119 kdm: :0[12579]: pam_unix(xdm:session): session opened for user tester by (uid=0)
2014-02-05T14:47:30.046893+01:00 xyz119 systemd[1]: Starting Session 46 of user tester.
2014-02-05T14:47:30.047931+01:00 xyz119 systemd-logind[672]: New session 46 of user tester.
2014-02-05T14:47:30.048942+01:00 zyx119 systemd-logind[672]: Linked /tmp/.X11-unix/X0 to /run/user/7354397/X11-display.
2014-02-05T14:47:30.049968+01:00 xyz119 systemd[1]: Started Session 46 of user tester.
2014-02-05T14:47:30.082342+01:00 xyz119 kdm: :0 '[12604]: Startup script returned non-zero exit code
2014-02-05T14:47:30.136462+01:00 xyz119 kdm: :0[12579]: pam_unix(xdm:session): session closed for user tester
2014-02-05T14:47:30.147574+01:00 xyz119 systemd-logind[672]: Removed session 46.

Anyone else has or had the same problem and maybe found a solution?
For the moment i use gdm.
Thanks,

Michael

I’m wondering why that is a problem. Why would anybody need a UID that large?

Currently, I am using “lightdm”. But I see no point in creating a using with such a large UID just to test if it works.

You could file a bug report. I guess you would report that to bugs.kde.org.

On 2014-02-05 16:36, nrickert wrote:
> I’m wondering why that is a problem. Why would anybody need a UID that
> large?

I saw a usecase for that time ago, but the OP has not mentioned that
here. It is not a standard install, so better illuminate us :slight_smile:


Cheers / Saludos,

Carlos E. R.

(from 13.1 x86_64 “Bottle” (Minas Tirith))

Some big companies, that use OpenSuSE in a professional environment like us, need UIDS up to 99.000.000 using LDAP. In OpenSuSE 13.2 this bug appears as well but with a slight difference:
UIDs like 20.000.000+x work fine. 28.000.000 don’t. This behaviour seems rather strange to me. A bugfix would be nice.

  1. this thread is very old, please do not expect that many people still watch it for new posts;

  2. you are talking about 13.2, which is NOT where the original thread is about and NOT what the title shows;

Conclusion: when you want to draw the maximum of attention to a problem you have, you better start a fresh thread, with a title fit for YOUR problem.
In the description, you may of course link to this old thread when you think that is of use.

This thread is CLOSED.