On Monday 01 October 2007, 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. > > The other one listed there is a hard lock requiring hardware reset. >
That bug started out based on what you are talking about, a bunch of other people started adding the hardlock stuff, but everything I reported in that thread, as well as the initial report relates to what you are talking about. Anyway, on my system at least, I traced it down to something that superkaramba was doing to trigger some kind of bug in the xserver, but only when using the nvidia driver. After trying a bajillion combinations of apps, turning off beryl, I discovered that if I didn't load superkaramba, the problem went away. -- Greg _______________________________________________ arch mailing list [email protected] http://archlinux.org/mailman/listinfo/arch
