[EN] Login Manager not working with Nvidia Driver

[Sir_Aim]

Hi, I did a fresh install this weekend, and all seems to be fine - but after I switched to the Nvidia Driver I can not log in from the graphical login manager.

After login the screen turns black for a few seconds and throws me back to the login screen...
When I login in a new terminal and launch KDE with startx it works without a promblem.

Does anyone know this issue and how to fix it?

Code: [Select]

System:
  Host: i9 Kernel: 6.8.2-1-siduction-amd64 arch: x86_64 bits: 64 compiler: gcc
    v: 14.0.1
  Desktop: KDE Plasma v: 5.27.10 Distro: siduction 2023.1.1 giants - kde -
    (202403291554) base: Debian GNU/Linux trixie/sid
Machine:
  Type: Desktop Mobo: ASUSTeK model: PRIME Z370-A II v: Rev X.0x
    serial: <superuser required> UEFI-[Legacy]: American Megatrends v: 0602
    date: 03/12/2019
CPU:
  Info: 8-core model: Intel Core i7-9700K bits: 64 type: MCP arch: Coffee Lake
    rev: D cache: L1: 512 KiB L2: 2 MiB L3: 12 MiB
  Speed (MHz): avg: 800 min/max: 800/4900 cores: 1: 800 2: 800 3: 800 4: 800
    5: 800 6: 800 7: 800 8: 800 bogomips: 57600
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: NVIDIA TU116 [GeForce GTX 1660 Ti] vendor: ASUSTeK driver: nvidia
    v: 550.67 arch: Turing bus-ID: 01:00.0
  Display: server: X.Org v: 21.1.11 with: Xwayland v: 23.2.4 driver: X:
    loaded: nvidia unloaded: fbdev,modesetting,nouveau,vesa gpu: nvidia
    resolution: 1: 1920x1200~60Hz 2: 1920x1200~60Hz 3: 1920x1200~60Hz
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 550.67
    glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce GTX 1660 Ti/PCIe/SSE2


[synapsenstau]

I have exactly the same problem (login loop after Nvidia driver installation) and start my PC the same way as you (startx...). There is no further information about errors to be found in Nvidia and Xorg log.

At some point I found this error with "journalctl -p err -b":

Code: [Select]

Apr 07 09:41:10 xxxx login[3533]: PAM unable to dlopen(pam_lastlog.so): /usr/lib/security/pam_lastlog.so: cannot open shared object file: No such file or directory
Apr 07 09:41:10 xxxx login[3533]: PAM adding faulty module: pam_lastlog.so
Apr 07 09:41:25 xxxx login[5199]: PAM unable to dlopen(pam_lastlog.so): /usr/lib/security/pam_lastlog.so: cannot open shared object file: No such file or directory
Apr 07 09:41:25 xxxx login[5199]: PAM adding faulty module: pam_lastlog.so

The reason why it can't find /usr/lib/security/pam_lastlog.so is because there is no /secutity folder under /lib.
Since English is not my native language, I unfortunately didn't understand the solutions on Stackoverflow and co.

[dibl]

After login the screen turns black for a few seconds and throws me back to the login screen...

If you have accidentally left a file owned by root in the user's /home/user directory, it can cause that problem. Also, take a look at the file /home/user/.xsession-errors and see if tells anything useful.

[Sir_Aim]

I just checked that: 'find . ! -user aim' in my homedir does not show any result - so all file permissions should be ok.

The failed graphical logins don't appear in .xsession-errors. It only has entries for the successful starts from startx.
So i guess whatever goes wrong happens before the xsession is started.

[ro_sid]

@synapsenstau

Code: [Select]

Apr 07 09:41:10 xxxx login[3533]: PAM unable to dlopen(pam_lastlog.so): /usr/lib/security/pam_lastlog.so: cannot open shared object file: No such file or directory
Apr 07 09:41:10 xxxx login[3533]: PAM adding faulty module: pam_lastlog.so
Apr 07 09:41:25 xxxx login[5199]: PAM unable to dlopen(pam_lastlog.so): /usr/lib/security/pam_lastlog.so: cannot open shared object file: No such file or directory
Apr 07 09:41:25 xxxx login[5199]: PAM adding faulty module: pam_lastlog.sopam_lastlog.so does not/no longer exist/s in "unstable" for the amd64 architecture, just in "stable" and "testing" [- and /usr/lib/security/ would have been the wrong path, anyhow, it should be (/usr)/lib/x86_64-linux-gnu/security/ ].

May be that this is @Sir_Aim's problem, too.

[hendrikL]

https://wiki.debian.org/PamLastlog2

[Sir_Aim]

May be that this is @Sir_Aim's problem, too.

No, I don't have any PAM related errors. And sddm login works fine with nouveau.

[Sir_Aim]

Update / correction: sddm login does not work with nouveau - I switched back from nvidia-drivers and found out sddm freezes with nouveau. Different outcome - but definitely not working.

I thought it was pretty obvious that this was caused by the driver change. I don't know if the nvidia install chances something in a configuration file which caused this issue. But as I always do a full-upgrade first after the install is completed, that maybe pulled an update which broke wayland.

I chose X11 for sddm and was able to login successfully.
So Wayland is not working at all, neither with nvidia-drivers nor nouveau.

@synapsenstau Maybe this will working for you: On the login screen click the left button (triangle in my theme) and choose X11.
Would be nice to know if this works with nvidia-driver...

[hendrikL]

Did you try another sddm-theme?
Like the breeze theme (for kde/plasma users)?
Search for them.
It would be interesting if others theme work.