Ubuntu 14.04 on Acer TravelMate P253: keyboard lost after resume

[Adalberto]

Hi,
on my new Acer TravelMate P253 notebook, Ubuntu desktop 14.04 looses the keyboard after suspend/resume, thus leaving me locked out of my session, since I can't input the password to unlock!
Note, though, that I can still press Ctrl+Alt+F1 to get to console and login normally in character-mode: if I only knew a command to reload the x11 keyboard driver or something like that, I could avoid shutting everything down with "init 0", which is my usual solution...
Thank you for any suggestion!
Adalberto
---
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: adaca 2036 F.... pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=UUID=2cb12901-c875-489b-9b65-2faa464d351b
InstallationDate: Installed on 2014-06-15 (1 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: Acer TravelMate P253
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-29-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-29-generic N/A
 linux-backports-modules-3.13.0-29-generic N/A
 linux-firmware 1.127.2
Tags: trusty
Uname: Linux 3.13.0-29-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 12/16/2013
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V2.21
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: BA51_HC_CR
dmi.board.vendor: Acer
dmi.board.version: Type2 - Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Insyde Corp.
dmi.chassis.version: V2.21
dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.21:bd12/16/2013:svnAcer:pnTravelMateP253:pvrV2.21:rvnAcer:rnBA51_HC_CR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.21:
dmi.product.name: TravelMate P253
dmi.product.version: V2.21
dmi.sys.vendor: Acer

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1330629

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Adalberto (adaca)]

apport information

[Adalberto (adaca)]

apport information

[Adalberto (adaca)]

apport information

[Adalberto (adaca)]

apport information

[Adalberto (adaca)]

apport information

[Adalberto (adaca)]

apport information

[Adalberto (adaca)]

apport information

[Adalberto (adaca)]

apport information

[Adalberto (adaca)]

apport information

[Adalberto (adaca)]

apport information

[Adalberto (adaca)]

apport information

[Adalberto (adaca)]

apport information

[Adalberto (adaca)]

apport information

[Adalberto (adaca)]

apport information

[Adalberto (adaca)]

apport information

[Adalberto (adaca)]

apport information

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.15 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.15-utopic/

[Adalberto (adaca)]

Sorry for any inconvenience this may have caused, but I've just realized this isn't a bug: I had a VirtualBox virtual machine running, it grabbed the keyboard so locking the host (ubuntu) screen (by just locking it, or also by suspending/resuming) always results in the unability to input the password, since the keyboard remains grabbed by the virtual machine.
There' no easy workaround either: I just need to exit VM full screen (via Right-Ctrl+F), then ungrab the keyboard (via Right-Ctrl); then I can safely close the lid of my notebook!
I will anyway try and post this as a feature inquiry/request on virtualbox.org: since the user can still access a console (via Ctrl+Alt+F*), is there a comand-line util to send a "ungrab keyboard" command to a running VM?
Adaberto