Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#43982 - [xorg-server-common] Updating xorg server from 1.17.1-3 breaks USB mouse handling
Attached to Project:
Arch Linux
Opened by Oleksandr Natalenko (post-factum) - Saturday, 28 February 2015, 11:26 GMT
Last edited by Doug Newgard (Scimmia) - Sunday, 01 March 2015, 15:57 GMT
Opened by Oleksandr Natalenko (post-factum) - Saturday, 28 February 2015, 11:26 GMT
Last edited by Doug Newgard (Scimmia) - Sunday, 01 March 2015, 15:57 GMT
|
DetailsUpdating xorg server from 1.17.1-2 to 1.17.1-3 breaks my USB mouse handling. I have Logitech LX8 wireless mouse with USB receiver. When it is plugged in neither touchpad nor mouse works correctly: I'm unable to select menu items in KDE, left-clicking invokes click somewhere else but not under the mouse pointer, cannot use most of apps controls. Unplugging USB receiver resolves the problem with touchpad.
Downgrading to 1.17.1-2 also fixes the issue. Tried stock 3.18 as well as custom 3.19 kernel with no luck. Using latest KDE 5 packages, but the same behavior is observed in bare SDDM — cannot even click to focus on password field in order to log in. Also tried libinput with no luck as well. |
This task depends upon
Closed by Doug Newgard (Scimmia)
Sunday, 01 March 2015, 15:57 GMT
Reason for closing: None
Additional comments about closing: User requested: Downgrading do not solve the issue. Will investigate more.
Sunday, 01 March 2015, 15:57 GMT
Reason for closing: None
Additional comments about closing: User requested: Downgrading do not solve the issue. Will investigate more.