I can confirm that the current iteration of kernel version 3.11.0-2-generic fixed the bug for me as well. Thanks to everyone involved. :)
I can confirm that the current iteration of kernel version 3.11.0-2-generic fixed the bug for me as well. Thanks to everyone involved. :)