Cannot login at start-up but root can login in recovery mode

[DanshilMungur]

I've recently installed Jackd2, Qtractor, Ardour on my Debian system. However when starting Ardour for the first time, I get an error 'your system has a limit to locked memory'. After some Googling, I found this https://wiki.debian.org/Ardour and decide to follow the instructions at the Trouble shooting section. After editing /etc/security/limits.conf and /etc/pam.d/common-session, I leave my desk and when I come back my laptop is locked (that's xcfe-power-manager, nothing weird) but when I try to unlock it, I never get the password right. I also cannot log in to the root account neither.
I reboot and go in recovery mode to check if I'm not inputting wrong passwords (checked with passwd) but it works there. Just not when I boot up normally.
I then decide to revert the changes I made to the 2 files, do pam-auth-update, but still, when I reboot after that and try logging again, it won't work. I checked all the files in the /etc/pam.d/ folder and made sure they are at their default values.
Now I don't know what went wrong anymore and cannot use my Debian except in recovery mode.

[dilberts_left_nut]

Put /etc/pam.d/common-session back the way it was.

[sunrat]

Ardour development happens rapidly whereas that wiki page is over 3 years old so may be irrelevant. Or maybe not.
Do what dilberts_left_nut suggests, then see if Ardour actually does run out of memory. Maybe the error message is a non-issue. I have never seen it, although I use Ardour in KX Studio which is pre-configured for audio.
The best help you can get for Ardour is their mailing list - http://lists.ardour.org/listinfo.cgi/ar ... ardour.org or IRC channel.

[DanshilMungur]

I reverted the common-session to what it was. Here are the contents:

Code: Select all

#
# /etc/pam.d/common-session - session-related modules common to all services
#
# This file is included from other service-specific PAM config files,
# and should contain a list of modules that define tasks to be performed
# at the start and end of sessions of *any* kind (both interactive and
# non-interactive).
#
# As of pam 1.0.1-6, this file is managed by pam-auth-update by default.
# To take advantage of this, it is recommended that you configure any
# local modules either before or after the default block, and use
# pam-auth-update to manage selection of other modules.  See
# pam-auth-update(8) for details.

# here are the per-package modules (the "Primary" block)
session	[default=1]			pam_permit.so
# here's the fallback if no module succeeds
session	requisite			pam_deny.so
# prime the stack with a positive return value if there isn't one already;
# this avoids us returning an error just because nothing sets a success code
# since the modules above will each just jump around
session	required			pam_permit.so
# and here are more per-package modules (the "Additional" block)
session	required	pam_unix.so 
session	optional	pam_systemd.so 
# end of pam-auth-update config

I can't boot in Debian at all, so I can't start Ardour at all. All I have is a terminal I can use when I boot in recovery mode.