Bug 246263
Summary: | Mouse wheel not working | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Klaus-Peter Schrage <kpschrage> | ||||||||||
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||||||||
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
Severity: | medium | Docs Contact: | |||||||||||
Priority: | low | ||||||||||||
Version: | 9 | CC: | ajax, gczarcinski, mcepl, xgl-maint | ||||||||||
Target Milestone: | --- | ||||||||||||
Target Release: | --- | ||||||||||||
Hardware: | All | ||||||||||||
OS: | Linux | ||||||||||||
Whiteboard: | |||||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
Doc Text: | Story Points: | --- | |||||||||||
Clone Of: | Environment: | ||||||||||||
Last Closed: | 2009-07-14 18:03:18 UTC | Type: | --- | ||||||||||
Regression: | --- | Mount Type: | --- | ||||||||||
Documentation: | --- | CRM: | |||||||||||
Verified Versions: | Category: | --- | |||||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||||
Embargoed: | |||||||||||||
Attachments: |
|
Description
Klaus-Peter Schrage
2007-06-29 17:20:09 UTC
Created attachment 158225 [details]
X log file
Could you test what happens when you rename /etc/X11/xorg.conf to something else and restart X? (In reply to comment #2) > Could you test what happens when you rename /etc/X11/xorg.conf to something else > and restart X? X wouldn't start (see log). So, as a test, I deleted both Input Device sections for the mouse and the touch pad (Synaptics driver) in xorg.conf, as well as the corresponding lines in the Server Layout section. After restarting X, the behavior of the mouse hadn't noticeably changed - it worked, but no scrolling. Created attachment 158347 [details]
X log file after X had started without xorg.conf
(In reply to comment #3) > X wouldn't start (see log). ajax, does automagic self-configuration work with framebuffer? Update: The bug reported above remains on Fedora 8 ... Additional info: When I plug in a USB wheel mouse (Logitech MX300), it is recognized immediately, with the wheel working as expected. So just a shot in the dark: Is it possible that the bug is not X related but rather a Bluetooth/HID/HCI issue (sorry, don't know much about this stuff)? Still not working as of this date (also does not work on f9-preview so I expect it will not work on Fedora 9 when released). My solution is to add the kernel (cmdline) parameter: psmouse.proto=imps Once added, the whell works fine. The device is a Logitech Trackman Wheel (trackball). With f9's anaconda no longer having the ability top specify kernel parameters, this is a bigger pain. I am raising the priority ... hopefull someone will at least look at this report. Changing version to '9' as part of upcoming Fedora 9 GA. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Gene: can you please provide a log file, I'd like to have a look at the device configuration in F9. Klaus-Peter: sounds like a hw/kernel/... issue. Your input device section points at /dev/input/mice, which means X doesn't actually see that a new mouse is plugged in. If the logitech's wheel works, this indicates that it's the other mouse. Either in the kernel, the hardware or as you said the BT stack. Created attachment 316609 [details]
/var/log/Xlog.0
system is F9 plus all updates as of 12 Sep 2008 ... system is booted with cmdline parameter psmouse.proto=imps
Created attachment 316611 [details]
/var/log/messages
system just booted before grabbing this file ... it goes with the Xlog file above
BTW, it may be a bit of a pain to add this but has worked for me for years now.
In the interest of complete honesty, my systems also include a Belkin 8-port KVM switch between the wheel-trackball and the computer. However, MS Windows does not seem to have any problems with this configuration (wheel works).
Gene: The log indicates nothing out of the ordinary. Your mouse is added to the server through the evdev driver, a driver that relies on the kernel to deal with protocol-specific issues. xorg-x11-drv-mouse on the other hand deals with PS/2 directly. My guess is that the KVM switch confuses the in-kernel driver so that it does not export wheel events to userspace. Reassigning to kernel. This message is a reminder that Fedora 9 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 9. 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 '9'. 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 9'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 9 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 Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 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. |