Bug#614972: gdm3: can't login ("can't open display :0" in .xsession-errors)

[Vincent Lefevre]

On 2011-02-24 17:09:04 +0100, Vincent Lefevre wrote:
> Agent pid 2891
> No protocol specified
> [fvwm][main]: <<ERROR>> can't open display :0

I think the problem comes from the fact that I have

  [[ -n $DISPLAY ]] && export XAUTHORITY=$HOME/.Xauthority

in my ".zshenv" (it is sourced in a zsh script before fvwm is run).
This was needed to be able to start X applications (e.g. emacs)
after a su.

I can login if I choose a Fvwm session (instead of the default that
uses the .xsession script), but I get similar problems from an xterm
probably for the same reason (zsh is my login shell), e.g. with
emacs:

No protocol specified
Display :0 unavailable, simulating -nw

If the Xauthority location has changed, this should be announced,
as this is not the default. The X(7) man page says:

    XAUTHORITY
      This must point to a file that contains authorization data.  The
      default   is   $HOME/.Xauthority.  See  Xsecurity(7),  xauth(1),
      xdm(1), Xau(3).

-- 
Vincent Lefèvre <vincent at vinc17.net> - Web: <http://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / Arénaire project (LIP, ENS-Lyon)