Bug 484654 - keyboard scroll wheel is not working in X Window
Summary: keyboard scroll wheel is not working in X Window
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: hal
Version: 10
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Richard Hughes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-02-09 10:20 UTC by Kirill Kolyshkin
Modified: 2014-10-20 17:13 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-12-18 07:51:48 UTC
Type: ---
Embargoed:
kolyshkin: needinfo-


Attachments (Terms of Use)
hal-device output (137.93 KB, text/plain)
2009-02-09 10:23 UTC, Kirill Kolyshkin
no flags Details
lsusb -v output (29.61 KB, text/plain)
2009-02-09 10:24 UTC, Kirill Kolyshkin
no flags Details
/var/log/Xorg.0.log (12.88 KB, text/plain)
2009-02-09 18:01 UTC, Kirill Kolyshkin
no flags Details

Description Kirill Kolyshkin 2009-02-09 10:20:12 UTC
> Description of problem:

After upgrade to Fedora 10, my scroll wheel (the one on the keyboard) stopped working. Keyboard is BTC8193C, scroll wheel is working fine since kernel 2.6.25 (see kernel.org bug #9385, http://bugzilla.kernel.org/show_bug.cgi?id=9385)

I see that kernel input layer produces correct output by running evtest /dev/input/event5.

I checked that /dev/input/mouse1 (usual USB mouse w/scroll), /dev/input/mouse2 (the keyboard's scrollwheel), and /dev/input/mice (a multiplexed device combining every mouse available) produce similar output.

So the scroll wheel is working by itself, apparently the problem is X Window does not know about it. I think this is because of switching to HAL.

hal-device doesn't know anything about mouse2:
$ hal-device  | grep mouse2; echo $?
1

My wild guess is this is because (a) HAL tells X about every separate mouse device (but not /dev/input/mice like it was before HAL) (b) in my case a single device combines kbd and mouse and HAL just can't understand that.

> Version-Release number of selected component (if applicable):

$ rpm -qf `which hal-device`
hal-0.5.12-14.20081027git.fc10.x86_64

$ rpm -q xorg-x11-drv-evdev xorg-x11-server-Xorg
xorg-x11-drv-evdev-2.1.1-1.fc10.x86_64
xorg-x11-server-Xorg-1.5.3-6.fc10.x86_64


> How reproducible:
Always


> Steps to Reproduce:
1. Attach BTC8193C keyboard to a Fedora 10 system
2. Try to use scroll wheel on the keyboard while in terminal or browser window which is scrollable.
  
> Actual results:
Nothing happens

> Expected results:
System should react to scroll wheel motion

Comment 1 Kirill Kolyshkin 2009-02-09 10:23:30 UTC
Some more info

> [root@kir ~]# ls -l /dev/input/
total 0
drwxr-xr-x  2 root root     140 2009-02-09 12:29 by-id
drwxr-xr-x  2 root root     160 2009-02-09 12:29 by-path
crw-r-----  1 root root 13,  64 2009-02-09 12:29 event0
crw-r-----  1 root root 13,  65 2009-02-09 12:29 event1
crw-rw----+ 1 root root 13,  66 2009-02-09 12:29 event2
crw-rw----+ 1 root root 13,  67 2009-02-09 12:29 event3
crw-r-----  1 root root 13,  68 2009-02-09 12:29 event4
crw-r-----  1 root root 13,  69 2009-02-09 12:29 event5
crw-r-----  1 root root 13,  70 2009-02-09 12:29 event6
crw-r-----  1 root root 13,  63 2009-02-09 12:29 mice
crw-r-----  1 root root 13,  32 2009-02-09 12:29 mouse0
crw-r-----  1 root root 13,  33 2009-02-09 12:29 mouse1
crw-r-----  1 root root 13,  34 2009-02-09 12:29 mouse2
crw-------  1 root root 10, 223 2009-02-09 12:29 uinput

> [root@kir ~]# ls -l /dev/input/by-id/
total 0
lrwxrwxrwx 1 root root 9 2009-02-09 12:29 usb-0518_USB-compliant_keyboard-event-kbd -> ../event4
lrwxrwxrwx 1 root root 9 2009-02-09 12:29 usb-0518_USB-compliant_keyboard-event-mouse -> ../event5
lrwxrwxrwx 1 root root 9 2009-02-09 12:29 usb-0518_USB-compliant_keyboard-mouse -> ../mouse2
lrwxrwxrwx 1 root root 9 2009-02-09 12:29 usb-Logitech_USB-PS.2_Optical_Mouse-event-mouse -> ../event3
lrwxrwxrwx 1 root root 9 2009-02-09 12:29 usb-Logitech_USB-PS.2_Optical_Mouse-mouse -> ../mouse1

> [root@kir ~]# ls -l /dev/input/by-path/
total 0
lrwxrwxrwx 1 root root 9 2009-02-09 12:29 pci-0000:00:1a.2-usb-0:1:1.0-event-kbd -> ../event4
lrwxrwxrwx 1 root root 9 2009-02-09 12:29 pci-0000:00:1a.2-usb-0:1:1.1-event-mouse -> ../event5
lrwxrwxrwx 1 root root 9 2009-02-09 12:29 pci-0000:00:1a.2-usb-0:1:1.1-mouse -> ../mouse2
lrwxrwxrwx 1 root root 9 2009-02-09 12:29 pci-0000:00:1a.7-usb-0:6.1.4:1.0-event-mouse -> ../event3
lrwxrwxrwx 1 root root 9 2009-02-09 12:29 pci-0000:00:1a.7-usb-0:6.1.4:1.0-mouse -> ../mouse1
lrwxrwxrwx 1 root root 9 2009-02-09 12:29 platform-pcspkr-event-spkr -> ../event6

> [root@kir ~]# lsusb
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 006: ID 046d:c03e Logitech, Inc. Premium Optical Wheel Mouse
Bus 001 Device 005: ID 0424:2228 Standard Microsystems Corp. 9-in-2 Card Reader
Bus 001 Device 004: ID 0424:2602 Standard Microsystems Corp. 
Bus 001 Device 003: ID 0424:2502 Standard Microsystems Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 002: ID 0518:0002 EzKEY Corp. EZ-9900C Keyboard
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Will attach lsusb -v and hal-device output in a moment.

Comment 2 Kirill Kolyshkin 2009-02-09 10:23:57 UTC
Created attachment 331295 [details]
hal-device output

Comment 3 Kirill Kolyshkin 2009-02-09 10:24:24 UTC
Created attachment 331296 [details]
lsusb -v output

Comment 4 Kirill Kolyshkin 2009-02-09 10:25:07 UTC
> # cat /etc/sysconfig/hw-uuid 
5440f56f-93f2-4228-8588-e097819bbd3c

Comment 5 Kirill Kolyshkin 2009-02-09 17:59:17 UTC
Also
[kir@kir ~]$ hal-find-by-capability --capability input.mouse xinput list
/org/freedesktop/Hal/devices/computer_logicaldev_input_1
/org/freedesktop/Hal/devices/usb_device_46d_c03e_noserial_if0_logicaldev_input

Comment 6 Kirill Kolyshkin 2009-02-09 18:01:56 UTC
Created attachment 331340 [details]
/var/log/Xorg.0.log

Comment 7 Kirill Kolyshkin 2009-02-09 18:04:08 UTC
Please disregard comment #5. Here's what I wanted to show:

> [kir@kir ~]$ hal-find-by-capability --capability input.mouse
/org/freedesktop/Hal/devices/computer_logicaldev_input_1
/org/freedesktop/Hal/devices/usb_device_46d_c03e_noserial_if0_logicaldev_input

> [kir@kir ~]$ xinput list
"Virtual core keyboard"	id=0	[XKeyboard]
	Num_keys is 248
	Min_keycode is 8
	Max_keycode is 255
"Virtual core pointer"	id=1	[XPointer]
	Num_buttons is 32
	Num_axes is 2
	Mode is Relative
	Motion_buffer is 256
	Axis 0 :
		Min_value is 0
		Max_value is -1
		Resolution is 0
	Axis 1 :
		Min_value is 0
		Max_value is -1
		Resolution is 0
"Logitech USB-PS/2 Optical Mouse"	id=7	[XExtensionPointer]
	Num_buttons is 32
	Num_axes is 2
	Mode is Relative
	Motion_buffer is 256
	Axis 0 :
		Min_value is -1
		Max_value is -1
		Resolution is 1
	Axis 1 :
		Min_value is -1
		Max_value is -1
		Resolution is 1
"Macintosh mouse button emulation"	id=6	[XExtensionPointer]
	Num_buttons is 32
	Num_axes is 2
	Mode is Relative
	Motion_buffer is 256
	Axis 0 :
		Min_value is -1
		Max_value is -1
		Resolution is 1
	Axis 1 :
		Min_value is -1
		Max_value is -1
		Resolution is 1
"USB-compliant keyboard"	id=5	[XExtensionKeyboard]
	Num_keys is 248
	Min_keycode is 8
	Max_keycode is 255
"Power Button (FF)"	id=4	[XExtensionKeyboard]
	Num_keys is 248
	Min_keycode is 8
	Max_keycode is 255
"Sleep Button (CM)"	id=3	[XExtensionKeyboard]
	Num_keys is 248
	Min_keycode is 8
	Max_keycode is 255
"USB-compliant keyboard"	id=2	[XExtensionKeyboard]
	Num_keys is 248
	Min_keycode is 8
	Max_keycode is 255
	Num_buttons is 32

Comment 8 Kirill Kolyshkin 2009-02-16 09:29:22 UTC
Could someone please take a look?

Comment 9 Scott Glaser 2009-09-09 13:07:30 UTC
Have you tried with the latest hal package in Fedora 10, Fedora 11 or tried Rawhide? In either case, can you let us know whether the issue is still happening, and give the current version of the HAL packages you're using?

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 10 Bug Zapper 2009-11-18 11:03:31 UTC
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '10'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 10's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 10 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 11 Bug Zapper 2009-12-18 07:51:48 UTC
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.