Hide Forgot
Description of problem: After logging in into graphical mode, the mouse works fine for a couple of seconds or minutes then it starts behaving strangely. The pointer keeps moving to the top left of the screen. If I move the mouse, the pointer will move accordingly a bit, but it will still be attracted to the top left of the screen. The computer becomes practically unusable. Version-Release number of selected component (if applicable): xorg-x11-drv-evdev-2.5.0-1.fc14.x86_64.rpm How reproducible: Every time in the last 8 hours. Before this it has happened twice or thrice in the last month. Steps to Reproduce: 1. Login to GNOME. 2. Start some programs, do stuff as usual for a couple of seconds or minutes. Actual results: Mouse pointer/cursor starts moving up and left on its own. The keyboard becomes unresponsive, e.g. the Caps Lock key will stop working. Expected results: The mouse pointer shouldn't move on its own. Even if the mouse is broken somehow, the keyboard should still work. Additional info: This happens with both the nouveau and nvidia X drivers. I also tried two different USB optical mouses: a "Microsoft Comfort Optical Mouse 1000" and a Dell. My keyboard is an old AT model connected to the motherboard with a PS/2 adapter. I don't have any other input devices, e.g. joysticks, mice, trackballs. I am running kernel-2.6.35.13-91.fc14.x86_64. There are other people having similar problems: - https://bugzilla.redhat.com/show_bug.cgi?id=597696 - http://www.fedoraforum.org/forum/showthread.php?t=238388 - http://www.linuxquestions.org/questions/linux-newbie-8/mouse-cursor-keeps-moving-left-by-itself-872754/ - http://ubuntuforums.org/showthread.php?t=1649029
When I said that Caps Lock is not working, I was referring to the fact that the Caps Lock LED is not responding accordingly.
Created attachment 498149 [details] boot.log
Created attachment 498150 [details] dmesg
Created attachment 498151 [details] lsusb -v
Created attachment 498152 [details] Xorg.0.log
Created attachment 498154 [details] Xorg.0.log.old
Created attachment 498155 [details] evtest /dev/input/event2 # AT - PS/2 keyboard
Created attachment 498156 [details] evtest /dev/input/event3 # Dell USB mouse
Created attachment 498158 [details] /var/log/messages Last boot is from May 10 22:03:03
I've changed the PS/2 (AT) keyboard with a Microsoft USB one and quite surprisingly X has been working fine for the last hour or so and it keeps working.
It's been 9 hours and X is still working fine with the new keyboard. I wonder if it's just a coincidence or not.
I disconnected the USB keyboard and reattached the PS/2 keyboard. It worked fine for a few moments then the symptoms reappeared. I detached it and reattached the USB keyboard hoping that the mouse pointer will become responsive again. It didn't, so thinking that the bug might be triggered by some key presses I started pressing all the keys of that keyboard. When I arrived at the numeric keypad, I discovered that some of its keys moved the mouse. At that that moment I realized the cause of the bug. Mouse emulation was somehow turned on and the broken keyboard was controlling the mouse pointer. I started pressing other keys as well and managed to disable mouse emulation and things went back to normal. Now I have two questions. Why is the mouse emulation shortcut working when I haven't activated it under Assistive Technologies -> Keyboard Preferences -> Mouse Keys? If a program changed something somewhere else I'm not aware of this. The second question is how do I disable this shorcut? It's also strange that evtest didn't capture anything else besides the keys I pressed to test that keyboard is still responding.
It has just happened again and I got out of it like this: - plug in the (working) USB keyboard - press the "Home" key from the numeric keypad Pressing Shift+NumLock on the PS/2 keyboard hasn't help at all.
what's the output of "xkbcomp -xkb $DISPLAY -", the output of setxkbmap -print and the output of gconftool-2 --dump /desktop/gnome/peripherals/keyboard
Created attachment 499154 [details] xkbcomp -xkb $DISPLAY -
Created attachment 499159 [details] setxkbmap -print
Created attachment 499161 [details] gconftool-2 --dump /desktop/gnome/peripherals/keyboard
Just for the record, I run all the commands while the computer was working fine and only the PS/2 keyboard was connected.
PointerKeys is the XKB feature that provides mouse emulation. It can be enabled either by a client request (the checkbox) or through an XKB action. F14 ships with xkeyboard-config 1.9, that still has the Enable_PointerKeys action in the keymap by default. So regardless of the checkbox being enabled, Shift+NumLock enables PointerKeys. xkeyboard-config 2.0 removed this and made it an option. xkeyboard-config is noarch, so you should be able to fetch the F15 one and install it. Try if this works around the issue. Not sure why Home fixes the issue, I'd need to see the keymaps from the broken setup. It's possible that a bug offsets the key mapping so they spill over into other keys. I don't see anything obviously wrong in the log files tbh.
I guess I should have been more explicit. The PS/2 keyboard is definitely broken and the Microsoft USB Keyboard is working fine as fair as I know (I haven't had any issues with it), so the previous attachments should enough. On the other hand, if you're talking about running those commands while the mouse pointer goes ballistic, this will have to wait because I can't trigger the bug at will and I haven't had any issues since 2011-05-13 (comment 13). If my memory serves me right, the USB keyboard is Microsoft Wired Keyboard 200 for Business [1]. I don't have at me right now, but I do have this from /var/log/messages: usb 4-1: New USB device found, idVendor=04ca, idProduct=0022 usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 usb 4-1: Product: USB Keyboard usb 4-1: Manufacturer: LITEON Technology input: LITEON Technology USB Keyboard as /devices/pci0000:00/0000:00:1a.1/usb4/4-1/4-1:1.0/input/input2 generic-usb 0003:04CA:0022.0001: input,hidraw0: USB HID v1.10 Keyboard [LITEON Technology USB Keyboard] on usb-0000:00:1a.1-1/input0 [1] http://www.microsoft.com/hardware/en-us/b/wired-keyboard-200-for-business/6JH-00001#overview
This bug was filed against Fedora 14 which is now EOL. Please re-open this bug if you still experience this issue with one of the currently suppported versions of Fedora. Don't forget to update the version field if you do so.