I wonder if this is related to Bug #99755
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/450504
Title:
Keyboard and trackpad occasionally unusable after suspend
To manage notifications about this
This bug report was marked as Incomplete and has not had any updated
comments for quite some time. As a result this bug is being closed.
Please reopen if this is still an issue in the current Ubuntu
development release http://cdimage.ubuntu.com/daily-live/current/ .
Also, please be sure to
Hi Bryan,
This bug was reported a while ago and there hasn't been any activity in it
recently. We were wondering if this is still an issue? Can you try with the
latest development release of Ubuntu? ISO CD images are available from
http://cdimage.ubuntu.com/releases/ .
If it remains
On Fri, Apr 2, 2010 at 20:56, Jeremy Foshee jeremy.fos...@canonical.com wrote:
Hi Bryan,
This bug was reported a while ago and there hasn't been any activity in it
recently. We were wondering if this is still an issue? Can you try with the
latest development release of Ubuntu? ISO CD
It seems that it is related to evdev - please see
http://bugs.archlinux.org/task/14046 (reloading AT interface works for
me, at least) and they state that this issue is fixed as of xserver-
xorg-input-evdev 2.3.1 - you could test eg. lucid package for evdev
Here is a log of the suspend/resume cycle when the keyboard locked up.
The log starts at the beginning of the suspend cycle, and continues
until I perform a hard reboot.
** Attachment added: suspend-kern.log
http://launchpadlibrarian.net/33598802/suspend-kern.log
--
Keyboard and trackpad
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/33598767/AlsaDevices.txt
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/33598768/AplayDevices.txt
** Attachment added: ArecordDevices.txt
http://launchpadlibrarian.net/33598769/ArecordDevices.txt
Here is a full kernel log of the boot in question. As you can see, it
was not the first time the system had been suspended that boot; however
the number of suspensions does not seem to correlate with occurences of
the bug.
** Attachment added: full-kern.log
