On Thu, 2005-03-24 at 11:23 -0500, Christopher Martin wrote: > On March 24, 2005 05:56, Nicolas Raspail wrote: > > yesterday I've upgraded my debian Sid to kde 3.4.0 with the packages > > from alioth. I've purged the kdm package and install the newer but I can > > log in anymore. In my .xsession-errors I've the following error : > > > > Xsession: X session started for fireball at Thu Mar 24 11:39:44 CET 2005 > > /etc/X11/Xsession:.:104: no such file or > > directory: /etc/X11/Xsession.d/20xfree86-common_process-args > > \n/etc/X11/Xsession.d/30xfree86-common_xresources > > \n/etc/X11/Xsession.d/50xfree86-common_determine-startup > > \n/etc/X11/Xsession.d/90xfree86-common_ssh-agent > > \n/etc/X11/Xsession.d/92xprint-xpserverlist > > \n/etc/X11/Xsession.d/99xfree86-common_start > > > > So, I've edited the file /etc/kde3/kdm/Xsession and comment the > > following lines > > > > [ -z "$ZSH_NAME" ] && exec $SHELL $0 "$@" > > emulate -R zsh > > > > and now I can log in without problems. If I removed kdm, startx works > > fine. > > The problem seems to be that I re-added the sourcing of shell config files > in KDE 3.4. On startup, kdm uses zsh to source /etc/X11/Xsession (after > sourcing its own config files), but fails because zsh handles expansion in > an unusual way (the expansion, in this case, of the files > in /etc/X11/Xsession.d). To get it to work, we need to set: > > setopt shwordsplit > > I've attached an alternate Xsession script that includes this change. Could > you test it? > > Thanks, > Christopher Martin
I've just replaced my Xsession file by yours and now I can log in without problem, thanks. For the multiple connections bug, if I run the command w, I get the following results with your new file fireball(pts/1)@deus:~ % w 19:54:29 up 18 min, 2 users, load average: 0.33, 0.20, 0.17 USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT fireball :0 - 19:41 ?xdm? 38.81s 0.03s /bin/sh /usr/bin/startkde fireball :0 - 19:41 ?xdm? 38.81s 0.03s /bin/sh /usr/bin/startkde So this problem is always here Regards Nicolas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
