New comment by daniel-eys on void-packages repository

https://github.com/void-linux/void-packages/issues/20051#issuecomment-599148013

Comment:
Interesting, so lightdm caused this.
Looking at `/etc/pam.d/lightdm`, lightdm seems to delegate pam to `pam_elogind.so` (?), but I don't really know where/when/how elogind sets limits for its sessions.
One workaround would be to explicitly load `pam_limits` (the pam module responsible for setting resource limits) by adding

`session required pam_limits.so`

to `/etc/pam.d/lightdm`, like so:
```
...
# Setup session
session   required pam_unix.so
session   required pam_limits.so
-session   optional pam_elogind.so
-session optional pam_ck_connector.so nox11
```

So with this added, you could actually continue using lightdm. @VoidDuck