Hello Bryce, or anyone else affected, Accepted systemd into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/204-5ubuntu20.16 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: systemd (Ubuntu Trusty) Status: In Progress => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1371403 Title: [PATCH] Please disable USB autosuspend for Avocent SC Secure KVM Status in systemd package in Ubuntu: Invalid Status in systemd source package in Trusty: Fix Committed Status in systemd source package in Utopic: Won't Fix Bug description: My mouse becomes temporarily become unresponsive to drags and clicks, until I right-click or give keyboard input, when it's been idle for a few seconds. The same thing affects the keyboard. In some cases the mouse cursor jumps back to the center of the screen. The mouse and keyboard are connected to a number of different computers via an 8-port Avocent SC Secure KVM. When the mouse and/or keyboard are directly attached to one of the PCs, there is no problem. I've tested with different keyboards and mice as well, and they're similarly messed up. Only the computers running Ubuntu 14.04 are affected. Two of the computers are identical hardware, differing only in Ubuntu versions - the 14.04 one is affected but the one with 13.04 is not. I also have a machine with 12.04 on it connected to the KVM which is fine. I first noticed the problem when I upgraded to 13.10. In powertop I notice that autosuspend is enabled for the Avocent. If I switch that off, then the problem disappears completely. I can also prevent it by issuing: echo 'on' > '/sys/bus/usb/devices/3-10/power/control'; where 3-10 is the Avocent (the number is different on each of my systems). I notice in 42-usb-hid-pm.rules there is a rule for Avocent devices: # Catch-all for Avocent HID devices. Keyed off interface in order to only # trigger on HID class devices. ACTION=="add", SUBSYSTEM=="usb", ATTRS{idVendor}=="0624", ATTR{bInterfaceClass}=="03", TEST=="../power/control", ATTR{../power/control}="auto" However my KVM device doesn't appear to have a bInterfaceClass defined. In any case, the following udev rule corrects the problem for me: ACTION=="add", SUBSYSTEM=="usb", ATTRS{idVendor}=="0624", ATTR{idProduct}=="0013", ATTR{product}=="SC Secure KVM", TEST=="power/control", ATTR{power/control}:="on" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1371403/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
