Adding an empty line at the end of login.conf fixed my problem. -- Patrick Harper paia...@fastmail.com
On Tue, 17 Sep 2019, at 14:21, Patrick Harper wrote: > Hi All, > > For a while this file has instructed a new login class to be added to > the end of /etc/login.conf, as per below. > > gnome:\ > :datasize-cur=1024M:\ > :tc=default: > > On both my amd64 machines, this does not effectuate following a reboot. > If I try to create a new user in the class with adduser and try to > specify gnome, > > gnome: is not allowed! > > is printed. gnome is not listed in the 'Default login class list' > either. If I use the usermod command as written in the readme, > > usermod: No such login class `gnome' > > is printed. > > If I try to force the gnome class by editing the chpass database for > the user and rebooting, users will appear on the gdm greeter but it is > impossible to login to them. Users created through the GNOME Settings > are added to the default class and are also impossible to login to, I > think because the password encoding is different. > > My workaround for now is to use the 'staff' login class, which seems to > have resource limits high enough for gnome to work, although it is "not > recommended". With this setup there is a functionality issue - logging > out through the UI causes gdm to exit to the console (although the > daemon seems to continue running), whereas it should display the gdm > greeter. Whether or not this is a byproduct of the staff class settings > I don't know. > > -- > Patrick Harper > paia...@fastmail.com > >