Good. Could you please provide a direct URL to your post specifically, not just the archive in it's entirety?
>"I originally posted to <email address hidden>, but the response I received was "Care to explain how this is a usb issue." I was busy with school and work, and just reposted to <email address hidden> today."
While linux-usb seems logical, the developer view of it is not as straight forward. If it is a scancode issue, linux-input may be a better place, as the issue is an "input" issue with a USB device, not with the USB protocol stack (i.e. linux-usb). It's silly for whoever responded to you with "care to explain..." when it would have been clear you aren't in a position to do that as you posted a input-input issue into linux-usb. :D
Ari Fogel, regarding your comments https:/ /bugs.launchpad .net/ubuntu/ +source/ linux/+ bug/1168224/ comments/ 36 : www.spinics. net/lists/ linux-input/ maillist. html"
"@Christopher per your comment on 2013-08-22: http://
Good. Could you please provide a direct URL to your post specifically, not just the archive in it's entirety?
>"I originally posted to <email address hidden>, but the response I received was "Care to explain how this is a usb issue." I was busy with school and work, and just reposted to <email address hidden> today."
While linux-usb seems logical, the developer view of it is not as straight forward. If it is a scancode issue, linux-input may be a better place, as the issue is an "input" issue with a USB device, not with the USB protocol stack (i.e. linux-usb). It's silly for whoever responded to you with "care to explain..." when it would have been clear you aren't in a position to do that as you posted a input-input issue into linux-usb. :D
Regarding https:/ /bugs.launchpad .net/ubuntu/ +source/ linux/+ bug/1168224/ comments/ 37 :
>' I suppose I could try a true Saucy environment..."
A Saucy live environment test would be fine.