So after the tedious process of backing up all of my data, and doing a
clean install I'm sorry to say that the issue is still there...
I have found that I don't need to completely shut down my system I can
just suspend it to get things working again ... which leads me to
believe that this really
If suspend fixes it, then it would seem that it is a kernel issue. Would
you mind booting into the latest Mainline Build of the kernel, as that
will verify that it is the root cause. Instructions on how to boot into
the mainline build can be found here
Dear Debugging Experts, (most notably Quinn Balazs)
This issue has now transcended the merely annoying, and entered into the
realm of a 'right pain in the ass'. For this reason I'm planning on
doing a clean install to see if the situation is helped any by this...
Before I do so however, is there
You've given all of the relevant information. Let us know if the fresh
install works for you. If it doesn't then we will take a more earnest
look into what might be going on.
Quinn Balazs
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Tried using Ctrl + Alt + F1 after latest failure, to no avail.
Failure logs successfully created via SSH are attached.
There is no integrated keyboard or touchpad on this machine.
** Attachment added: dmesg_boot dmesg_diff Xorg.0.log Xorg.0.log_diff
** Changed in: xorg (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1211207
Title:
Keyboard and Mouse stop working after undefined time
Status
Confirmed that something is seriously wrong here. Are you using any sort
of USB hub, or only the onboard USB ports? But for all intents and
purposes it seems to be an X problem, where evdev isn't loaded along
with the mouse and keyboard, leading to the them being ignored because
an input device
I'm not using any USB hubs except for those built into the machine.
Hope to hear back from you soon with some positive feedback.
On 20 Aug 2013 01:10, Quinn Balazs qtbal...@gmail.com wrote:
Confirmed that something is seriously wrong here. Are you using any sort
of USB hub, or only the onboard
Attached are the first set of log files you requested... the rest to
follow as soon as the issue rears its ugly head again.
** Attachment added: lspci-vvnn lsusb-v uname-a version_signature
Slight issue... while I still own a non-USB keyboard (PS/2) my PC no
longer has a PS/2 socket.
Will the log files after a reboot still be relevant, or are there some
additional steps I need to take to ensure the correct info is logged?
--
You received this bug notification because you are a
Before trying this, attempt to switch to a virtual terminal using the
frozen keyboard on the off chance that that hotkey combo still is
received. If that works just execute the commands there, but if not you
will have to do the following:
They will not contain relevant information after reboot,
Also, just as something that I noticed looking over the logs that you
already provided, is there an integrated keyboard and touchpad included
with the machine? And if there is, do those cease functioning when the
USB keyboard and mouse do. It does however look like everything is
normally detected
Okay, so with USB keyboard and mouse issues there are a few logs that
need to be attached.
Run the following commands one at a time in a terminal window. Just
pasting them from here into it should work fine.
lsusb -v ~/lsusb-v
uname -a ~/uname-a
cat /proc/version_signature
13 matches
Mail list logo
