On Fri, Nov 30, 2007 at 11:51:40AM +0100, Bernhard R. Link wrote:
> * jacob <[EMAIL PROTECTED]> [071130 10:39]:
> > When using C-t !, ratpoison now causes X to spin out of control, using
> > 100% CPU, and causing local keyboard to be unresponsive until killed via
> > ssh. I suspect that C-t : would be similarly affect, but am reluctant to
> > try it, as it is an EXTREMELY annoying breakage. I strongly suspect that
> > this is due to libc6 2.7-1 finally pushing through, since that seems to
> > be when it started.
> 
> In my tests Xorg even keeps at 100% system load after I stop ratpoison
> in the debugger. So I guess there is definitly some bug Xorg. (I don't
> know yet if ratpoison does something illegal to cause this, but Xorg
> should definitly not hang this way).
> 

I agree. To fix the situation, I generally have to kill -9 `pidof X` a
couple of time, then restart the dm.

> Could you tell me the versions of Xorg (and which drivers) you are using,
> so I can properly reassign/clone[1] the bug to xorg?

ii  xorg                                         1:7.3+7                    
X.Org X Window System
ii  xorg-docs                                    1:1.4-2                    
Miscellaneous documentation for the X.Org so
ii  xserver-xorg                                 1:7.3+7                    the 
X.Org X server
ii  xserver-xorg-core                            2:1.4.1~git20071119-1      
Xorg X server - core server
ii  xserver-xorg-input-kbd                       1:1.2.2-3                  
X.Org X server -- keyboard input driver
ii  xserver-xorg-input-mouse                     1:1.2.3-1                  
X.Org X server -- mouse input driver
ii  xserver-xorg-input-synaptics                 0.14.7~git20070706-1       
Synaptics TouchPad driver for X.Org/XFree86 
ii  xserver-xorg-video-sis                       1:0.9.3-6                  
X.Org X server -- SiS display driver

> 
> Hochachtungsvoll,
>       Bernhard R. Link
> 
> [1] depending whether I see anything causing ratpoison being responsible
> for this or not.
> 



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to