You can kill the session doing CTRL + F2 to open a new terminal, enter with root kill -9 on gdm and CTRL + F7 to back to Screen 1 to start again.
I try to use the gnome 2.20, but the new version of xorg cause me problems because i use geforce 4 and the new xorg(7.3) needs a new version of ABI(2.0i think) and the driver of nvidia dosn't have yet, so i do a rollback, put gnome 2.20 and use the old xorg and works. But this is for me... but affects xf86-input-keyboard and xf86-input-mouse so i dont know if this is the problem for all of you, just speculating. regards Allen 2007/10/1, Jason Chu <[EMAIL PROTECTED]>: > > On Mon, Oct 01, 2007 at 10:16:57PM +1000, James Rayner wrote: > > On Mon, October 1, 2007 21:45, Greg Meyer wrote: > > > On Monday 01 October 2007, RedShift wrote: > > >> Jason Chu wrote: > > >> > I've got this weird problem that I think is caused by X. > > >> > > > >> > I've been following testing for a while now (so I have gnome, db, > and > > >> > heimdal). > > >> > > > >> > Every so often, and apparently randomly, X will stop taking any > input > > >> > except for mouse movement. But the mouse movement doesn't even > > >> trigger > > >> > the focus follows mouse. > > >> > > > >> > The panel will still update and so will windows, but my input just > > >> > totally doesn't work. > > >> > > > >> > The only thing that I can do to fix it seems to be sshing in and > > >> killing > > >> > X. I run xfce4 so it might be the gnome/gtk updates that aren't > > >> working > > >> > well with it... > > >> > > > >> > Has anyone heard anything about problems with X or is it just me? > > >> > > > > > > > Been going on a long time. > > > > > > http://bugs.archlinux.org/task/7513 > > > > That sounds like a different problem. There's subtle differences. > > > > With this one, we get full input lock, but mouse still moves, and X can > > still be killed with ctrl-alt-backspace. That exact symptom has only > > appeared in the last few days/week. > > I can't kill X with ctrl-alt-backspace... > > > The other one listed there is a hard lock requiring hardware reset. > > > > They could be related... I don't know. Both are difficult to debug. > Until > > something convincingly links them I'd keep them separate otherwise we'll > > be making it impossible to debug. > > Jason > > _______________________________________________ > arch mailing list > [email protected] > http://archlinux.org/mailman/listinfo/arch > > >
_______________________________________________ arch mailing list [email protected] http://archlinux.org/mailman/listinfo/arch
