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

2011-03-05 Thread Vincent Lefevre
On 2011-02-26 10:35:18 +0100, Josselin Mouette wrote: > Le jeudi 24 février 2011 à 23:32 +0100, Vincent Lefevre a écrit : > > > This is not the same software. It is not compatible. Should we also > > > document the differences with xdm, slim and kdm? > > > > You miss the point that gdm3 is descri

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

2011-02-26 Thread Josselin Mouette
Le jeudi 24 février 2011 à 23:32 +0100, Vincent Lefevre a écrit : > > This is not the same software. It is not compatible. Should we also > > document the differences with xdm, slim and kdm? > > You miss the point that gdm3 is described as the successor of gdm: Successor, yes. Compatible, no. Ot

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

2011-02-24 Thread Vincent Lefevre
On 2011-02-24 22:45:58 +0100, Josselin Mouette wrote: > Le jeudi 24 février 2011 à 22:32 +0100, Vincent Lefevre a écrit : > > I also think that > > * there should be some file mentioning the main differences (in > > particular, those not very visible) between gdm and gdm3; > > This is not th

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

2011-02-24 Thread Josselin Mouette
Le jeudi 24 février 2011 à 22:32 +0100, Vincent Lefevre a écrit : > In the README file or README.Debian if Debian specific, and in the > man page? Why not. It looks like a valuable addition indeed. > I also think that > * there should be some file mentioning the main differences (in > parti

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

2011-02-24 Thread Vincent Lefevre
On 2011-02-24 21:51:19 +0100, Josselin Mouette wrote: > Le jeudi 24 février 2011 à 18:00 +0100, Vincent Lefevre a écrit : > > But the .Xauthority location change should have been documented and > > announced! > > Announced where? In the README file or README.Debian if Debian specific, and in the

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

2011-02-24 Thread Josselin Mouette
Le jeudi 24 février 2011 à 18:00 +0100, Vincent Lefevre a écrit : > But the .Xauthority location change should have been documented and > announced! Announced where? It’s already documented, in the user manual. -- .''`. Josselin Mouette : :' : `. `' “If you behave this way because you ar

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

2011-02-24 Thread Vincent Lefevre
retitle 614972 Undocumented .Xauthority location change can break login / X applications thanks On 2011-02-24 17:54:45 +0100, Vincent Lefevre wrote: > On 2011-02-24 17:09:04 +0100, Vincent Lefevre wrote: > > Agent pid 2891 > > No protocol specified > > [fvwm][main]: <> can't open display :0 > >

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

2011-02-24 Thread Vincent Lefevre
On 2011-02-24 17:09:04 +0100, Vincent Lefevre wrote: > Agent pid 2891 > No protocol specified > [fvwm][main]: <> 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 bef

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

2011-02-24 Thread Vincent Lefevre
Package: gdm3 Version: 2.30.5-7 Severity: important I've switched from gdm to gdm3, and I can no longer login after this change. The file ":0-slave.log.1" contains: gdm-session-worker[2767]: pam_unix(gdm3:session): session opened for user vlefevre by (uid=0) gdm-session-worker[2767]: pam_ck_con