Ubuntu
xorg-server package

  1. Bug #619403
  2. Comment #13

Comment 13 for bug 619403

Revision history for this message
In , Albert Zeyer (albertzeyer) wrote :

Ok, I am in the middle of a progress here. I am trying to optimise it a bit further. But I will attach my current progress so far so you can review it and give some comments because I actually have the problem that sometimes (mostly after I restart xinit on a running Xserver), somehow the device property names are messed up or at least xinput shows this:

az@acompneu 1275 (~) %xinput list-props 8
Device 'Microsoft Microsoft IntelliMouse® Explorer':
 NumLock (119): 1
 left_ptr (241): ... of unknown type _DBUS_SESSION_BUS_SELECTION_az_9797c07820e7488abd822c644c1f55a4

 _DBUS_SESSION_BUS_ADDRESS (243): 0
 _DBUS_SESSION_BUS_PID (244): 0
 KDE_FULL_SESSION (245): ... of unknown type _DBUS_SESSION_BUS_SELECTION_az_9797c07820e7488abd822c644c1f55a4

 KDE_SESSION_VERSION (246): ... of unknown type _DBUS_SESSION_BUS_SELECTION_az_9797c07820e7488abd822c644c1f55a4

 WM_PROTOCOLS (247): ... of unknown type _DBUS_SESSION_BUS_SELECTION_az_9797c07820e7488abd822c644c1f55a4

 Evdev Reopen Attempts (226): 10
 Evdev Axis Inversion (227): 0, 0
 Evdev Axes Swap (229): 0
 _NET_WM_CONTEXT_HELP (251): "LevelFive" (127), "AltGr" (128)
 _NET_WM_SYNC_REQUEST (252): "Alt" (120), "LevelThree" (121), "LAlt" (122), "RAlt" (123), "RControl" (124), "LControl" (125), "ScrollLock" (126), "_KDE_SPLASH_PROGRESS" (239), "WM_LOCALE_NAME" (240), "_XKB_RULES_NAMES" (238), "_XKB_RULES_NAMES" (238), "_XKB_RULES_NAMES" (238), "_XKB_RULES_NAMES" (238)
 Evdev Middle Button Emulation (230): 2
 Evdev Middle Button Timeout (231): 50
 Evdev Wheel Emulation (232): 0
 Evdev Wheel Emulation Axes (233): 0, 0, 4, 5
 Evdev Wheel Emulation Inertia (234): 10
 Evdev Wheel Emulation Timeout (235): 200
 Evdev Wheel Emulation Button (236): 4
 Evdev Drag Lock Buttons (237): 0

It looks a lot like some memory is messed up. I already tried to debug with valgrind but I didn't see anything related (a whole bunch of other messages show up there, so I also might have missed it).

Another thing which makes the debuggin a bit complicated: Most applications seem to scroll already for one event by multiple pixel; about 20 pixel in Chrome. And I have set it to the minimum possible value in the KDE settings (not sure if Chrome takes those or has its own settings). That makes the debugging quite hard because the scrolling is soon pretty much too fast.