On 7/17/24 11:58 PM, Masaru Nomiya wrote:
DCR> The xinput output is:
DCR> $ xinput DCR> ⎡ Virtual core pointer id=2 [master pointer (3)] DCR> ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] DCR> ⎜ ↳ Microsoft Microsoft 3-Button Mouse with IntelliEye(TM) id=9 [slave DCR> pointer (2)] DCR> ⎜ ↳ PS/2 Generic Mouse id=11 [slave pointer (2)] DCR> ⎜ ↳ SynPS/2 Synaptics TouchPad id=12 [slave pointer (2)] DCR> ⎣ Virtual core keyboard id=3 [master keyboard (2)] DCR> ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)] DCR> ↳ Power Button id=6 [slave keyboard (3)] DCR> ↳ Video Bus id=7 [slave keyboard (3)] DCR> ↳ Sleep Button id=8 [slave keyboard (3)] DCR> ↳ AT Translated Set 2 keyboard id=10 [slave keyboard (3)] DCR> ↳ HP WMI hotkeys id=13 [slave keyboard (3)]
DCR> The touchpad (id=12) works perfect. The micrsoft mouse (id=9) DCR> is really flaky under TW.
1. What is th bloody speaker?
Chuckling.... Alright, is this a trick question? What speaker are you looking at? (the broken kmix is another issue :)
2. What's this?
PS/2 Generic Mouse id=11 [slave pointer (2)]
This is the stupid pencil eraser size nub between the 'G' and 'H' keys that you can also use to move the mouse -- quite worthless actually and a PITA to get used to having that thing in the middle of the keyboard. I think they first appeared on IBM laptops years ago, and then HP picked them up too.
Wouldn't these give you hints?
I know what they are, but the detailed info doesn't tell me much, e.g.
1. $ xinput --list-props "Microsoft Microsoft 3-Button Mouse with IntelliEye(TM)"
$ xinput --list-props "Microsoft Microsoft 3-Button Mouse with IntelliEye(TM)" Device 'Microsoft Microsoft 3-Button Mouse with IntelliEye(TM)': Device Enabled (153): 1 Coordinate Transformation Matrix (155): 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000 libinput Natural Scrolling Enabled (283): 0 libinput Natural Scrolling Enabled Default (284): 0 libinput Scroll Methods Available (285): 0, 0, 1 libinput Scroll Method Enabled (286): 0, 0, 0 libinput Scroll Method Enabled Default (287): 0, 0, 0 libinput Button Scrolling Button (288): 2 libinput Button Scrolling Button Default (289): 2 libinput Button Scrolling Button Lock Enabled (290): 0 libinput Button Scrolling Button Lock Enabled Default (291): 0 libinput Middle Emulation Enabled (292): 0 libinput Middle Emulation Enabled Default (293): 0 libinput Rotation Angle (266): 0.000000 libinput Rotation Angle Default (267): 0.000000 libinput Accel Speed (294): 0.000000 libinput Accel Speed Default (295): 0.000000 libinput Accel Profiles Available (296): 1, 1, 1 libinput Accel Profile Enabled (297): 1, 0, 0 libinput Accel Profile Enabled Default (298): 1, 0, 0 libinput Accel Custom Fallback Points (299): <no items> libinput Accel Custom Fallback Step (300): 0.000000 libinput Accel Custom Motion Points (301): <no items> libinput Accel Custom Motion Step (302): 0.000000 libinput Accel Custom Scroll Points (303): <no items> libinput Accel Custom Scroll Step (304): 0.000000 libinput Left Handed Enabled (305): 0 libinput Left Handed Enabled Default (306): 0 libinput Send Events Modes Available (268): 1, 0 libinput Send Events Mode Enabled (269): 0, 0 libinput Send Events Mode Enabled Default (270): 0, 0 Device Node (271): "/dev/input/event4" Device Product ID (272): 1118, 64 libinput Drag Lock Buttons (307): <no items> libinput Horizontal Scroll Enabled (308): 1 libinput Scrolling Pixel Distance (309): 15 libinput Scrolling Pixel Distance Default (310): 15 libinput High Resolution Wheel Scroll Enabled (311): 1
2. $ xinput --list-props "PS/2 Generic Mouse"
$ xinput --list-props "PS/2 Generic Mouse" Device 'PS/2 Generic Mouse': Device Enabled (153): 1 Coordinate Transformation Matrix (155): 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000 libinput Natural Scrolling Enabled (283): 0 libinput Natural Scrolling Enabled Default (284): 0 libinput Scroll Methods Available (285): 0, 0, 1 libinput Scroll Method Enabled (286): 0, 0, 1 libinput Scroll Method Enabled Default (287): 0, 0, 1 libinput Button Scrolling Button (288): 2 libinput Button Scrolling Button Default (289): 2 libinput Button Scrolling Button Lock Enabled (290): 0 libinput Button Scrolling Button Lock Enabled Default (291): 0 libinput Middle Emulation Enabled (292): 0 libinput Middle Emulation Enabled Default (293): 0 libinput Rotation Angle (266): 0.000000 libinput Rotation Angle Default (267): 0.000000 libinput Accel Speed (294): 0.000000 libinput Accel Speed Default (295): 0.000000 libinput Accel Profiles Available (296): 1, 1, 1 libinput Accel Profile Enabled (297): 1, 0, 0 libinput Accel Profile Enabled Default (298): 1, 0, 0 libinput Accel Custom Fallback Points (299): <no items> libinput Accel Custom Fallback Step (300): 0.000000 libinput Accel Custom Motion Points (301): <no items> libinput Accel Custom Motion Step (302): 0.000000 libinput Accel Custom Scroll Points (303): <no items> libinput Accel Custom Scroll Step (304): 0.000000 libinput Left Handed Enabled (305): 0 libinput Left Handed Enabled Default (306): 0 libinput Send Events Modes Available (268): 1, 0 libinput Send Events Mode Enabled (269): 0, 0 libinput Send Events Mode Enabled Default (270): 0, 0 Device Node (271): "/dev/input/event2" Device Product ID (272): 2, 1 libinput Drag Lock Buttons (307): <no items> libinput Horizontal Scroll Enabled (308): 1 libinput Scrolling Pixel Distance (309): 15 libinput Scrolling Pixel Distance Default (310): 15 libinput High Resolution Wheel Scroll Enabled (311): 1 But the important touchpad that DOES work to scroll FF without the GDK_CORE_DEVICE_EVENTS=1 info may be helpful (2-finger scroll): $ xinput --list-props "SynPS/2 Synaptics TouchPad" Device 'SynPS/2 Synaptics TouchPad': Device Enabled (153): 1 Coordinate Transformation Matrix (155): 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000 Device Accel Profile (279): 1 Device Accel Constant Deceleration (280): 2.500000 Device Accel Adaptive Deceleration (281): 1.000000 Device Accel Velocity Scaling (282): 12.500000 Synaptics Edges (312): 1767, 5397, 1649, 4615 Synaptics Finger (313): 25, 30, 0 Synaptics Tap Time (314): 180 Synaptics Tap Move (315): 239 Synaptics Tap Durations (316): 180, 180, 100 Synaptics ClickPad (317): 0 Synaptics Middle Button Timeout (318): 75 Synaptics Two-Finger Pressure (319): 282 Synaptics Two-Finger Width (320): 7 Synaptics Scrolling Distance (321): 108, 108 Synaptics Edge Scrolling (322): 0, 0, 0 Synaptics Two-Finger Scrolling (323): 1, 0 Synaptics Move Speed (324): 1.000000, 1.750000, 0.036704, 0.000000 Synaptics Off (325): 1 Synaptics Locked Drags (326): 0 Synaptics Locked Drags Timeout (327): 5000 Synaptics Tap Action (328): 0, 0, 0, 0, 1, 3, 2 Synaptics Click Action (329): 1, 1, 1 Synaptics Circular Scrolling (330): 0 Synaptics Circular Scrolling Distance (331): 0.100000 Synaptics Circular Scrolling Trigger (332): 0 Synaptics Circular Pad (333): 0 Synaptics Palm Detection (334): 0 Synaptics Palm Dimensions (335): 10, 200 Synaptics Coasting Speed (336): 20.000000, 50.000000 Synaptics Pressure Motion (337): 30, 160 Synaptics Pressure Motion Factor (338): 1.000000, 1.000000 Synaptics Grab Event Device (339): 0 Synaptics Gestures (340): 1 Synaptics Capabilities (341): 1, 1, 1, 1, 1, 1, 1 Synaptics Pad Resolution (342): 81, 40 Synaptics Area (343): 0, 0, 0, 0 Synaptics Noise Cancellation (344): 27, 27 Device Product ID (272): 2, 7 Device Node (271): "/dev/input/event3" I don't see anything that immediately says -- "this /dev/input/eventX is hosed". I'm no expert in the finer points of mouse-hardware, but they seem fine. What is really "bloody" odd about the whole situation is I attached xev to the firefox window and captured the events between the mouse (with and without GDK_CORE_DEVICE_EVENTS=1) and touchpad and the X events captured are for all practical purposes identical. I've literally pulled my hair out trying to figure out how to tell what the difference is between what the FF window sees from the mouse and what it sees from the touchpad. Moreover, why it scrolls with the touchpad, but not with the mouse unless GDK_CORE_DEVICE_EVENTS=1. And further why the mouse scrolls FF fine in fluxbox without it. Do you see anything in the information? Let me know if you want to see the xev event traces and I'll post them on paste.opensuse.org. I basically just created short wrappers to launch FF and TB with the environment variable set, e.g.: $ cat ~/bin/firefox-esr-fix.sh #!/bin/sh GDK_CORE_DEVICE_EVENTS=1 firefox-esr & I'm pretty much out of ideas. This is just bizarre, but without mousewheel scroll after 20 years of using focus-follows-mouse, it will drive you nuts :) -- David C. Rankin, J.D.,P.E.