Xgl crashes and restarts if using Mouse Keys

Thanks for your bug report.

I can say that I was shocked to find that I can confirm this bug when (while trying to reproduce it) XGL died and the my X session disappeared : )

Steps to reproduce:
1. Go to System -> Preferences -> Keyboard .
2. Select the Accessibility... button at the bottom.
3. Tick "Enable keyboard accessibility features".
4. Select the "Mouse Keys" tab and tick "Enable Mouse Keys"
5. Press 8 on the numeric keypad.

Expected results:
Mouse pointer to move up.

Actual results:
XGL crashes (and bizarrely is not restarted by GDM)

Version information:
Ubuntu Feisty
xserver-xgl 7.2.0.git.20070224-0ubuntu3

Confirming

Backtrace was very small and only contained the following:

#0 0x0818d9bc in XkbDDXFakePointerMotion (flags=<value optimized out>, x=Cannot access memory at address 0xbffcce04
)
    at ddxFakeMtn.c:114
        oldX = Cannot access memory at address 0xbffccde8

Wow. This is still the case with the latest Xgl package in Gutsy.

I can confirm this bug in current Hardy. Mouse Keys were activated automatically (I don't know exactly why) and I found this bug report while trying to find the cause. Turning off Mouse keys and using the number pad no longer crashes Xgl.

IMHO, this is a major bug if users are going to have Xgl by default. Are the upstream developers aware of this bug?

Thanks for the ping. Now filed upstream.

Incidentally, we don't have Xgl by default. XGL is enabled by default if you install it, but it's not installed by default.

My situation is the exact same as Philippe's. Why was Mouse Keys enabled during upgrade? Shouldn't user prefs be honored? (ok, this is probably another bug, but stil).

I can confirm that disabling Mouse Keys works around the problem while keeping Xgl. Thanks for this info. I don't even remember for how long I've had Xgl installed, but since it's not used by default I'll just remove it for now.

Just for completeness: I consistently crashed Xgl with all numbers except 0 and 5. No other keys in the numpad (/*-+., and numpad-Enter in an brazillian ABNT2 keyboard) crashed Xgl.

Bug still exists in Hardy Heron

I have also confirmed this in two cases. Does anyone know why Mouse Keys was enabled by default?

Bug #227698 is a duplicate of this bug.
I got a resolution to this in the forum: https://bugs.launchpad.net/ubuntu/+source/xserver-xgl/+bug/31907
Resolution in hardy is to remove the package xserver-xgl which seems obsolete, and optionally switch to normal numeric keypad using System/Preferences/Keyboard/MouseKeys tab and unselect "Allow to control the pointer using the keyboard".

link to forum should be: http://ubuntuforums.org/showthread.php?p=5025680#post5025680

Unfortunately, the resolution to remove xserver-xgl also kills the ability to use compiz. I reinstalled xserver-xgl and kept mouse-keys disabled. Now it does not crash anymore and I can use compiz to its max!
btw. I have a nvidia-legacy card.

(I just posted this on the Ubuntu forum. This is very annoying. I changed my mind about reporting it. Since this is happening on upgrade, you can be sure many more will encounter it. I MUST use windows style numpad, and it's instant death to do that when this bug reappears. It'[s just done it a third time).

I just installed Hardy, and encountered this bug almost immediately. I have now disabled Preferences > Keyboard > Mouse keys > "Allow to control the pointer using the keyboard" TWICE, and both times, it reset itself after a period of time (less than an hour) and the problem reappeared again. I THINK it's Firefox3 resetting it, but cannot be sure yet. This damn bug seems to be years old, according to launchpad, and still not fixed, so I am not going to bother reporting it. But this resetting constantly may force me to scream a little.

Anyone know what is going on here, and how to make this more stable?

I have a fairly new nvidea G8600 card, if that's relevelant.

How to make it more stable is easy. Just remove the xserver-xgl package. Almost no-one needs to be using it anymore (I think the only people who might benefit are the ones with the nvidia-glx-legacy drivers).

I think I'll make a new Xgl upload which makes it refuse to start on anything but nvidia-glx-legacy. That should prevent some of this accidental usage.

Lowering importance due to known workaround.

xserver-xgl has been deprecated upstream, and removed from Intrepid. Closing the bug as won't fix.