Just to confirm this problem is specific to lucid. The previous desktop images were jaunty, and I have just tested that this problem does not exist on the jaunty client!
On the jaunty install (no trailing line in /etc/group, no gdm:optional pam_group.so line.) li...@senegal:~$ grep 192 /etc/yp.conf ypserver 192.168.42.2 li...@senegal:~$ grep nis /etc/nsswitch.conf group: compat nis netgroup: nis li...@senegal:~$ grep liesl /etc/security/group.conf * ;:0 ;liesl ;Al0000-2400 ;aimsadmr,aimsadmrw li...@senegal:~$ grep group /etc/pam.d/*|grep -v \# /etc/pam.d/common-auth:auth optional pam_group.so /etc/pam.d/login:auth optional pam_group.so li...@senegal:~$ grep + /etc/group li...@senegal:~$ grep + /etc/passwd li...@senegal:~$ ypcat group|grep aims aimsadmr:x:20003:jan,lynne,ike,fjwh,gudrun,aeeda,barrie,liesl,bwg,asharma aimsadrw2:x:20005:lynne,aeeda aimsadmrw:x:20004:liesl,aeeda aimsr:x:900:jan,lynne,ike,fjwh,gudrun,aeeda,bwg,asharma li...@senegal:~$ i...@senegal:~$ groups staff2009 aimsadmr aimsadmrw li...@senegal:~$ id uid=1498(liesl) gid=509(staff2009) groups=509(staff2009),20003(aimsadmr),20004(aimsadmrw) li...@senegal:~$ touch /home/aeeda/Desktop/Visitors_Overview_2007.ods So it is not server side. Adding the optional pam_group.so line to /etc/pam.d/gdm (as I have on lucid) to the jaunty machine did not reproduce the problem. It looks as if REMOVING the line "auth optional pam_group.so" from the lucid client FIXES this. Is there something wrong with that syntax? -- gdm does not obey NIS settings for user groups https://bugs.launchpad.net/bugs/553142 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
