This was fixed as of Friday with the running kernel being updated to 3.13.0-23-generic. Now that we're on 3.13.0-24-generic, this is an issue yet again.
This was fixed as of Friday with the running kernel being updated to 3.13.0-23-generic. Now that we're on 3.13.0-24-generic, this is an issue yet again.