Good evening list, I'm having a reproducible issue with the X when using "vmg" ( <a href="http://magnifier.sourceforge.net/">http://magnifier.sourceforge.net/</a> ). It will systematically make the Xorg process use 100% cpu and basically locks the machine. I just start it, move it around and I hit the issue. I tried the following in order to track the issue : Tried it with my first version of X on mandriva 2009.1 : X.Org X Server 1.6.1 I then tried with a newer version of X : X.Org X Server 1.6.4 Finally, I compiled another version of X : X.Org X Server 1.7.6 A little bit more information on the modules I run. (II) Module extmod: vendor="X.Org Foundation" compiled for 1.7.6, module version = 1.0.0 -- (II) Module dbe: vendor="X.Org Foundation" compiled for 1.7.6, module version = 1.0.0 -- (II) Module glx: vendor="X.Org Foundation" compiled for 1.7.6, module version = 1.0.0 -- (II) Module dri: vendor="X.Org Foundation" compiled for 1.7.6, module version = 1.0.0 -- (II) Module dri2: vendor="X.Org Foundation" compiled for 1.7.6, module version = 1.1.0 -- (II) Module intel: vendor="X.Org Foundation" compiled for 1.7.6, module version = 2.9.1 -- (II) Module vgahw: vendor="X.Org Foundation" compiled for 1.7.6, module version = 0.1.0 -- (II) Module fb: vendor="X.Org Foundation" compiled for 1.7.6, module version = 1.0.0 -- (II) Module evdev: vendor="X.Org Foundation" compiled for 1.7.6, module version = 2.4.0 I'm looking for some more information on how I could track the issue and find why the X process takes 100% of cpu and locks the machine like that. I looked into the debugging section of the X using gdb but it seems to cover crashes more than my current case. Let me know what additional information would be needed to help anwser the question. Thank you. Phil.