Comment 13 for bug 553142

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.)

liesl@senegal:~$ grep 192 /etc/yp.conf
ypserver 192.168.42.2
liesl@senegal:~$ grep nis /etc/nsswitch.conf
group: compat nis
netgroup: nis
liesl@senegal:~$ grep liesl /etc/security/group.conf
* ;:0 ;liesl ;Al0000-2400 ;aimsadmr,aimsadmrw
liesl@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
liesl@senegal:~$ grep + /etc/group
liesl@senegal:~$ grep + /etc/passwd
liesl@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
liesl@senegal:~$ iesl@senegal:~$ groups
staff2009 aimsadmr aimsadmrw
liesl@senegal:~$ id
uid=1498(liesl) gid=509(staff2009) groups=509(staff2009),20003(aimsadmr),20004(aimsadmrw)
liesl@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?