Re: can't connect to ANY desktop !
On Tuesday 18 October 2005 16:23, moi 1392 wrote:
> This morning I could start a desktop session (kde), I apt-get upgrade,
> and after shutting down and up my computer I was unable to start any
> desktop session !
>
> I tried kde / gnome / enlightenment with xdm / kdm / gdm and startx,
> with my account, root and an account that I just created to test !!
>
> Each time, after I enter my password and validate, X restart and
> reprompt x/g/kdm or I return under my VT.
>
> I can't get any useful message from Xorg.0.log, /var/log/syslog, dmesg
> and /var/log/daemon.log.
>
> In gdm, I get this error message :
>
> /etc/X11/gdm/PreSession/Default: Registering your session with wtmp and
> utmp /etc/X11/gdm/PreSession/Default: running: /usr/X11R6/bin/sessreg -a -w
> var/log/wtmp -u /var/run/utmp -x "/var/lib/gdm/:0.Xservers" -h "" -l ":0"
> "moi"
> /etc/X11/gdm/Xsession: Beginning session setup...
>
> And that's all...
>
> Someone have an idea or an advice ? I'm really clueless !!
This looks like the same problem that I am having at the minute as I am
getting exactly the same error message when I try and login. In think the
problem is to do with the openssh-client segfaulting. My guess is that you
are using ssh-askpass (as I am) to start your kde / gnome session.
The bug that seems to be most relevant is this one:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=328606
only it was filed against 1:4.2p1-3 and the current version that seems to be
in error is 1:4.2p1-5 I suppose the bug might have popped back up. Can anyone
confirm that this is what is causing this bug.
What makes me think this is the problem is whenever I try and use anything
that relies on openssh-client such as ssh or ssh-askpass I get a segfault
message in the syslog like this:
Oct 18 14:07:20 localhost kernel: ssh-agent[6705]: segfault at
0000000114211b2c rip 00002aaaaac40817 rsp 00007fffffdbaa48 error 4
Oct 18 14:13:06 localhost kernel: ssh[6763]: segfault at 000000014a00432c rip
00002aaaaac40817 rsp 00007fffffce6e58 error 4
Anyway that's my best guess. If it's not related I would apprecaite help with
this problem because I too can't log in.
Cheers,
Graham
Reply to: