Bug#359629: Bug #359629 solved? (gdm Fails to read/write .Xauthority in users home dir)

[Géraud Meyer]

None of the problems reported in my previous email (shown below) happen
anymore in unstable (gdm version 2.20.3-2). Could it be that bug #359629
can be closed?
I would be interested to know what solved it.

Géraud Meyer wrote:
> Package: gdm
> Version: 2.18.4-1
>
> I have the same problem as bug #359629: the following message appears in
> the log:
>     gdm[4431]: gdm_auth_user_add: Could not open cookie file
> /home/<user>/.Xauthority
> and the Xauthority file used by gdm is in /tmp.
>
> By changing the permissions of /home/<user> from 700 to 750 (which was
> the default I believe), gdm stops complaining and uses
> /home/<user>/.Xauthority. /home/<user> is owned by the user <user> and
> the group <user>. Permissions of 700 should work as well as permissions
> of 750.
>
> The problem appeared only very recently although the gdm package has not
> been upgraded nor its configuration altered. Could it be caused by some
> other package's upgrade (like an upgrade of pam)?
>
> Incidentally I tested a gdm theme with a face browser, and gdm does not
> display the different faces but only the same default face for everybody
> (this even with home directories with 750 permissions). This might be a
> related bug.
>
> P.S. /home is not an NFS mount. Here is the content of /etc/gdm.conf:
>
> [daemon]
> AlwaysRestartServer=true
> [security]
> [xdmcp]
> Enable=true
> DisplaysPerHost=1
> HonorIndirect=false
> MaxSessions=1
> [gui]
> [greeter]
> SoundOnLogin=false
> UseCirclesInEntry=true
> LockPosition=true
> GraphicalThemeRand=false
> [chooser]
> [debug]
> [servers]
>