Can not login with gdm3 when user cred is stored in NIS

Bug #1883515 reported by kenjo
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
gdm3 (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

So I no longer can login using gdm3. ssh works fine and from tty console aslo.

This seams to be limited to user that are stored in NIS.

But there also is some issue with local users.

I was running ubuntu 20.20 just fine but after a reboot there is some serious issues with how users are handled. Since I get thrown out directly after typing password there is a very limited amount of information I can give.

lets start with the local user: if I start a gnome-terminal and run "id" I get this.

uid=1000(kenjo_local) gid=1000(ken) groups=1000(ken)

if I then login to the same machine with "ssh localhost" and run id i get the correct

uid=1000(kenjo_local) gid=1000(ken) groups=1000(ken),4(adm),27(sudo)

why ???

-----------------------------------
for nis users I have no information to give as I never get to a bash prompt and can do anything. A critical error looks to be this

pam_systemd(gdm-password:session): Failed to create session: No such process

since that is the first error that shows up for NIS user id that do not show for local user id.
after this error it then terminates with

/usr/lib/gdm3/gdm-x-session[26595]: Unable to run X server

but everything looks to be permission related so if the system got user id and group id correctly things would probably work fine. But I have no idea why gdm3 gets different users than if I ssh into the machine.

Revision history for this message
kenjo (ken-kenjo) wrote :

So I just added the same information that is in NIS to the local file /etc/passwd /etc/group and now its possible to login with the user so it's 100% that gnome now stopped working with user data in NIS.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:

  apport-collect 1883515

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

Changed in gdm3 (Ubuntu):
status: New → Incomplete
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Although, isn't this a duplicate of bug 1882034?

Revision history for this message
kenjo (ken-kenjo) wrote :

Yes its the same issue. has to be something resent as 20.04 used to work fine.

just to be clear I still have the same home(nfs) directory so local user do not mean another user just that the user account information is local instead of in NIS database.

Revision history for this message
kenjo (ken-kenjo) wrote :

the issue with not having the same output of the "id" command has gone away after a reboot but something is still strange with that as I did logout and login the user after changing the group settings for the user to be able to see the change.

its not going to work well if the entire machine needs to be rebooted every time /etc/group is changed. again worked fine when logged into the terminal/ssh but the desktop(gdm) did not pick up the change until after a reboot.

is something caching user data ?? that user id was in nis but the group file was local (the id was added to sudo and adm group)

Revision history for this message
Sebastien Bacher (seb128) wrote :

Could you add your 'journalctl -b 0' log from a session having the issue?

Revision history for this message
Sebastien Bacher (seb128) wrote :

"session having the issue" -> try to log in using gdm, note the exact time you tried, then log into a ssh and get the journal log

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

OK if you say it's the same issue then we should use bug 1882034. Although if it's not the same issue then we can keep discussing it here.

Revision history for this message
Sebastien Bacher (seb128) wrote :

the logind errors are different in the other report and this one though

Revision history for this message
kenjo (ken-kenjo) wrote :
Download full text (3.8 KiB)

I cant make any more test right now but basically its

pam_systemd(gdm-password:session): Failed to create session: No such process

non working (nis)

jun 17 15:11:57 brix gdm-password][453635]: pam_unix(gdm-password:auth): Couldn't open /etc/securetty: No such file or directory
jun 17 15:11:57 brix gdm-password][453635]: gkr-pam: unable to locate daemon control file
jun 17 15:11:57 brix gdm-password][453635]: gkr-pam: stashed password to try later in open session
jun 17 15:11:57 brix gdm-password][453635]: pam_unix(gdm-password:session): session opened for user tester by (uid=0)
jun 17 15:11:57 brix gdm-password][453635]: pam_systemd(gdm-password:session): Failed to create session: No such process
jun 17 15:11:57 brix gdm-password][453635]: gkr-pam: unable to locate daemon control file
jun 17 15:11:57 brix gdm-password][453635]: gkr-pam: gnome-keyring-daemon started properly and unlocked keyring

after this /usr/lib/gdm3/gdm-x-session is running and failing.

----------------

if I use a local user

 jun 17 15:16:35 brix gdm-password][455270]: pam_unix(gdm-password:auth): Couldn't open /etc/securetty: No such file or directory
jun 17 15:16:35 brix gdm-password][455270]: gkr-pam: unable to locate daemon control file
jun 17 15:16:35 brix gdm-password][455270]: gkr-pam: stashed password to try later in open session
jun 17 15:16:35 brix gdm-password][455270]: pam_unix(gdm-password:session): session opened for user kenjo_local by (uid=0)

then a lot of systemd stuff and after that X is started

jun 17 15:16:35 brix systemd[1]: Created slice User Slice of UID 1000.
jun 17 15:16:35 brix systemd[1]: Starting User Runtime Directory /run/user/1000...
jun 17 15:16:35 brix systemd-logind[1014]: New session 734 of user kenjo_local.
jun 17 15:16:35 brix systemd[1]: Finished User Runtime Directory /run/user/1000.
jun 17 15:16:35 brix systemd[1]: Starting User Manager for UID 1000...
jun 17 15:16:35 brix systemd[455298]: pam_unix(systemd-user:session): session opened for user kenjo_local by (uid=0)
jun 17 15:16:35 brix systemd[455298]: Started Pending report trigger for Ubuntu Report.
jun 17 15:16:35 brix systemd[455298]: Reached target Paths.
jun 17 15:16:35 brix systemd[455298]: Reached target Timers.
jun 17 15:16:35 brix systemd[455298]: Starting D-Bus User Message Bus Socket.
jun 17 15:16:35 brix systemd[455298]: Listening on GnuPG network certificate management daemon.
jun 17 15:16:35 brix systemd[455298]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
jun 17 15:16:35 brix systemd[455298]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
jun 17 15:16:35 brix systemd[455298]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
jun 17 15:16:35 brix systemd[455298]: Listening on GnuPG cryptographic agent and passphrase cache.
jun 17 15:16:35 brix systemd[455298]: Listening on debconf communication socket.
jun 17 15:16:35 brix systemd[455298]: Listening on Sound System.
jun 17 15:16:35 brix systemd[455298]: Listening on D-Bus User Message Bus Socket.
jun 17 15:16:35 brix systemd[455298]: Reached target Sockets.
jun 17 15:16:35 brix systemd[455298]: Reached target Basic System.
j...

Read more...

Revision history for this message
kenjo (ken-kenjo) wrote :

is there a way to format text so it is actually readable ?? basically preformat tag or something

Revision history for this message
Ketiw Simplistic (ketiwsim) wrote :

The sam issue here: local user OK NIS user cannot login with gdm3 but can with lighdm
error:
gdm-password][2057]: pam_systemd(gdm-password:session): Failed to create session: Invalid argument

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.