It works! :D
Quoting the thing "in /etc/pam.d/login add the line session required /lib/security/pam_limits.so to the bottom then do the same for the file associated with your DM i.e. /etc/pam.d/lightdm"
oh yea it's probably something like that, if I go directly to console to login it works like it should, I can't start any DEs like that cuz they're not setup but yea, and I guess the sudo thing works for some weird reason related.
Also I think you got like cutoff.
No, it didn't work, what I did find weird is that I can login as even root or any other even new user and it says 4096 but if I enter the sudo shell it does the number I put in the file.
# /etc/security/limits.conf
#
#This file sets the resource limits for the users logged in via PAM.
#It does not affect resource limits of the system services.
#
#Also note that configuration files in /etc/security/limits.d directory,
#which are read in alphabetical order, override the settings in this
#file in case the domain is the same or more specific.
#That means, for example, that setting a limit for wildcard domain here
#can be overridden with a wildcard setting in a config file in the
#subdirectory, but a user specific setting here can be overridden only
#with a user specific setting in the subdirectory.
#
#Each line describes a limit for a user in the form:
#
#<domain> <type> <item> <value>
#
#Where:
#<domain> can be:
# - a user name
# - a group name, with @group syntax
# - the wildcard *, for default entry
# - the wildcard %, can be also used with %group syntax,
# for maxlogin limit
#
#<type> can have the two values:
# - "soft" for enforcing the soft limits
# - "hard" for enforcing hard limits
#
#<item> can be one of the following:
# - core - limits the core file size (KB)
# - data - max data size (KB)
# - fsize - maximum filesize (KB)
# - memlock - max locked-in-memory address space (KB)
# - nofile - max number of open file descriptors
# - rss - max resident set size (KB)
# - stack - max stack size (KB)
# - cpu - max CPU time (MIN)
# - nproc - max number of processes
# - as - address space limit (KB)
# - maxlogins - max number of logins for this user
# - maxsyslogins - max number of logins on the system
# - priority - the priority to run user process with
# - locks - max number of file locks the user can hold
# - sigpending - max number of pending signals
# - msgqueue - max memory used by POSIX message queues (bytes)
# - nice - max nice priority allowed to raise to values: [-20, 19]
# - rtprio - max realtime priority
#
#<domain> <type> <item> <value>
#
#* soft core 0
#@student hard nproc 20
#@faculty soft nproc 20
#@faculty hard nproc 50
# End of file
* hard nofile 1048576
* soft nofile 1048576
mine has looked like this for multiple hours and I've rebooted my computer multiple times.
No it's not that apparently, if I do sudo and enter that one and there I do ulimit -Hn the limit was changed, it just doesn't change for my normal user even if I specify it just for it.
Also, it did not change. I added
"* hard nofile 1048576"
"* soft nofile 1048576"
to /etc/security/limits.conf and everything else is commented. but ulimit -Hn still outputs 4096 after a reboot.
That seems like you're complaining about people complaining, we should totally bully you. /j