On 22 September 2012 00:34, Chuck Cook <cmco...@earthlink.net> wrote: > What surprised me was that a usb library was crashing the system. What > does the USB bus have to do with the system login?
Support for fancy non HID or accessibility input devices maybe? brltty seems to rely on libusb. > Yet, the bug was > very repeatable. Somebody that knows a lot more than I, about how Linux > works, should probably investigate that. Considering that you were playing with 64, one way I see to potentially crash the system is if a 32 bit library gets replaced by a 64 bit one. Eg. system login tries to find out if there's a brltty terminal available, using a shared 32 bit libusb library. Finds a 64 bit instead of a 32 bit one due to custom install. System is unhappy. I'd like to see if we have more people reporting a similar problem when installing libusbx on their Linux distros before we commit resources to investigating this issue. Regards, /Pete ------------------------------------------------------------------------------ How fast is your code? 3 out of 4 devs don\\\'t know how their code performs in production. Find out how slow your code is with AppDynamics Lite. http://ad.doubleclick.net/clk;262219672;13503038;z? http://info.appdynamics.com/FreeJavaPerformanceDownload.html _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
