[i945gme] Keyboard not working after upgrade to Lucid

[David Planella]

After having successfully upgraded from Karmic to Lucid through update-manager, my keyboard does no longer respond to keypresses on the graphical session. That is, whenever GDM is started I can no longer type anything.

By using onBoard I can switch to a virtual tty, where the keyboard does work.

I'm attaching all relevant log files, if you need any more info, just let me know or ping me any time. Thanks!

ProblemType: Bug
Architecture: i386
Date: Thu Jan 28 19:56:46 2010
DistroRelease: Ubuntu 10.04
DkmsStatus: Error: [Errno 2] No such file or directory
EcryptfsInUse: Yes
MachineType: MICRO-STAR INTERNATIONAL CO., LTD U90/U100
Package: xorg 1:7.5+1ubuntu2
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-11-generic root=UUID=7dbe6d5d-36e0-4eae-b527-d3983ebcc7a4 ro quiet splash
ProcEnviron:
 LANGUAGE=ca_ES.UTF-8
 LANG=ca_ES.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-11.15-generic
RelatedPackageVersions:
 xserver-xorg 1:7.5+1ubuntu2
 libgl1-mesa-glx 7.7-0ubuntu8
 libdrm2 2.4.17-0ubuntu2
 xserver-xorg-video-intel 2:2.9.1-1ubuntu1
SourcePackage: xorg
Uname: Linux 2.6.32-11-generic i686
dmi.bios.date: 12/01/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.3
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: U90/U100
dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
dmi.board.version: Ver.001
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 10
dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO., LTD
dmi.chassis.version: Ver.001
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.3:bd12/01/2009:svnMICRO-STARINTERNATIONALCO.,LTD:pnU90/U100:pvrVer.001:rvnMICRO-STARINTERNATIONALCO.,LTD:rnU90/U100:rvrVer.001:cvnMICRO-STARINTERNATIONALCO.,LTD:ct10:cvrVer.001:
dmi.product.name: U90/U100
dmi.product.version: Ver.001
dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD
system:
 distro: Ubuntu
 architecture: i686kernel: 2.6.32-11-generic

[lspci]
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GME Express Integrated Graphics Controller [8086:27ae] (rev 03)
     Subsystem: Micro-Star International Co., Ltd. Device [1462:0110]

Workaround: Using an on-screen keyboard with Ubuntu Software Center or Terminal, uninstall the "mouseemu" package. (Don't try using Synaptic: the on-screen keyboard won't work with Synaptic's initial password prompt.)

[David Planella (dpm)]

I've noticed that removing the mouseemu package solves the issue (I can now use the keyboard). I'm leaving the xorg task open, as I'm not sure which one of the tw is the cause of the bug. Feel free to mark it as invalid if appropriate.

[Victor Ashik (vashik+)]

I confirm the bug. I met it on MacBook 2.1. Removing mouseemu helps to solve the issue. Xorg.0.log is full of messages:

"Mouseemu virtual keyboard": dropping event due to full queue!
"Mouseemu virtual keyboard": dropping event due to full queue!

[hemant (hemant-egroups)]

I can confirm this too. I am using macbook pro. My Keyboard does not respond on the login screen, so I enable the virtual keyboard, enter the password, and then everything works fine.

[wilbur.harvey (wilbur-harvey)]

I just upgraded my karmic to lucid on my gen2 macbook pro. Same problem.
Removing mouseemu also solved it for me.

[Bryce Harrington (bryce)]

The mouseemu task is probably sufficient for this bug. Certainly it's not a video driver bug. ;-)

[David Hedberg (david-hedberg)]

This also affects my old iBook G4 (ppc with radon mobility), so I don't think the i945gme-part in the bug name is particularly relevant.

[YvanWenger (yvan-wenger)]

Removing mouseemu also solved my problem on my macpro with slim alu keyboard

[unchiujar (vasile-jureschi)]

Removing mouseemu solved the problem for me too.

[Reece (reece)]

same here, but running in VMWare Fusion 3. I booted in recovery mode, removed mouseemu, and the problem vanished.

[Edwin Grubbs (edwin-grubbs)]

Removing mouseemu also fixed this problem for me in VMWare Fusion 3.

[nitrofurano (nitrofurano-3t)]

now a new bug was found: the conflict between mouseemu and xorg must be solved, since macbooks got completelly unusable with Ubuntu when used without mouse... :|

[Barry Warsaw (barry)]

Interesting. I'm running several Ubuntu versions under Fusion 3 and have never (to my knowledge) installed the mouseemu package. I'm even typing this from Lucid in a F3 VM.

ctrl-click works for me as a right button click straight out of the box w/o mouseemu.

The only thing that works on native OS X that doesn't work on Lucid is horizontal two-finger scrolling. I've just chalked that up to a Fusion bug, but maybe not.

[D J Eddyshaw (david-eddyshaw)]

The lastest upgrade of mouseemu fixed this.

[Benoit Grégoire (benoitg)]

This also affects me (using kdm, macbookpro 2.1) and I didn't have mouseemu installed at all. Installing it made no difference.

Booting in lucid with the karmic kernel and my keyboard works!

[Neil_C (neil-chesh)]

Keyboard not working after upgrade but only in GDM login screen. Entered password via onscreen keyboard and keyboard was fine once logged in.

No mouseemu installed.

[Sennaista (sennaista)]

Same problem here, keyboard not working in login screen but it's fine after that.

[sachin (sacsha30)]

Hi All

I am having a worse condition here. I am using Logitech wireless mouse and keyboard. Mouse is working fine in the login screen if I select something. But keyboard is not working at all.

And also when I select vitual keyboard it flashes keyboard and then dissappears. So now I am not able to login by anyway in my ubuntu :-(

I dont have mouseemu installed.

Any suggestions?

Regards
Sac

[sachin (sacsha30)]

Hi All

Can anybody please reply to my problem if anybody has some suggestion/solution.

I am really not able to work on my system for 2 days since I upgraded my system.

Regards
Sac

[mcwolf (mcwolf)]

to me it also has this bug

after starting Xorg keyboard stops working

my video card
03:00.0 VGA compatible controller: nVidia Corporation G84 [GeForce 8600 GT] (rev a1)
I tested the machine with the 3 driver: nv, nouveau, nvidia (195.36.15) with kernel 2.6.32-19

[sachin (sacsha30)]

Ok, I have just disable the password by switching in recovery mode and then logged in to the OS. Keyboard works absolutely fine in OS. So for me the problem is only with the login screen.

[mcwolf (mcwolf)]

at least my problem is not only in gdm / kdm (I tested both with manager)

in gdm has the option of entering a password with "virtual keyboard" (using the mouse) but even after releasing the desktop environment (Gnome / KDE) keyboard is dead

on stopping Xorg (via ssh) keyboard revives

[Sennaista (sennaista)]

My problem disappeared after a fresh install. I had originally upgraded from Karmic.

[Mahdi Fattahi (mfat)]

I did a fresh install of lucid using the alternate CD and my keyboard doen,t wok in GDM login screen. The on-screen keyboard also dissapears after 1 second. I chrooted into lucid using karmic and tried to remove mouseemu but no such package was installed. Please help me my system is now unusable.

[Mahdi Fattahi (mfat)]

I solved the problem by booting into recovery mode and typing:
sudo dpkg-reconfigure console setup
This time I selected US region and keyboard. Last time I had selected Iran region and keyboard layout. Seems like a bug.

[helmuthdu (helmuthdu)]

also, work for me:
sudo dpkg-reconfigure console-setup

[T[m] (t-w-sch)]

found the solution for me:

1. have no mouseemu installed and the reconfigure didn't work either...
2. go to "System>Preferences>Keyboard
3. use the "Accessibility" tab and untick "Only accept long keypresses"

that's it! I'm using my keyboard in the moment....obviously

[T[m] (t-w-sch)]

also found that:" http://communities.vmware.com/thread/263410"

[Benoit Grégoire (benoitg)]

sudo dpkg-reconfigure console-setup does NOT work for me. Keyboard works in grub, but when selecting recovery mode, keyboard is dead at the recovery console. Trackpad does work however.

Macbook pro gen 2, xorg-edgers.

Effect seems kernel dependent:
2.6.32 (stock lucid) keyboard doesn't work.
2.6.33 (kernel mainline) keyboard works.
2.6.34 (kernel mainline) keyboard doesn't work.

[Shon (shonlh)]

I am having a similar problem. mouseemu was never installed onto my system. I was able to get the keyboard working by reinstalling VMware-Tools onto my image. But it only works after login. I still have to use the onscreen keyboard to log in from the login screen. Since this is a vmware image I set autologin but it only bypasses the problem not fix it.

[adam.g.pullen (adam-g-pullen)]

sudo dpkg-reconfigure console-setup worked for me
Using:
* kubuntu
* MacBook Pro
* VMWare Fusion 3.0.2
* Swiss German keyboard

Reconfigured keyboard to generic 104 intl keyboard and worked fine to get through login
command from Keyboard layout - System Settings: setxkbmap -model pc104 -layout ch -variant

[Chris Halse Rogers (raof)]

 status incomplete

It seems likely that this is a duplicate of bug #548891.

If there are any people here who haven't already worked-around this by
running dpkg-reconfigure console-setup, what does the
file /etc/default/console-setup contain?

[J. McDonald (mcdonald-joseph)]

I upgraded to Lucid on a dual-G4 PowerPC Mac. I have no functioning keyboard. Without the USB keyboard, I had to enable the on-screen keyboard to log into X. Running dpkg-reconfigure console-setup does not fix the keyboard. I have the following lines in /etc/default/console-setup:

VERBOSE_OUTPUT=no
ACTIVE_CONSOLES="/dev/tty[1-6]"
CHARMAP="UTF-8"
CODESET="Lat15"
FONTFACE="VGA"
FONTSIZE="16"
XKPMODEL="macintosh"
XKBLAYOUT="us"
XKBVARIANT="mac"
XKBOPTIONS=" "

I think this bug may be more of an issue with PowerPC machines.
See https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/532114

[Benoit Grégoire (benoitg)]

dpkg-reconfigure console-setup still does NOT fix it for me (tried several different layouts). Intel based macbook pro. Always works with kernel 2.6.33, never works with kernel 2.6.32 or 2.6.34. Here is my current /etc/default/console-setup:

# A configuration file for setupcon

# Change to "yes" and setupcon will explain what is being doing
VERBOSE_OUTPUT=no

# Setup these consoles. Most people do not need to change this.
ACTIVE_CONSOLES="/dev/tty[1-6]"

# Put here your encoding. Valid charmaps are: UTF-8 ARMSCII-8 CP1251
# CP1255 CP1256 GEORGIAN-ACADEMY GEORGIAN-PS IBM1133 ISIRI-3342
# ISO-8859-1 ISO-8859-2 ISO-8859-3 ISO-8859-4 ISO-8859-5 ISO-8859-6
# ISO-8859-7 ISO-8859-8 ISO-8859-9 ISO-8859-10 ISO-8859-11 ISO-8859-13
# ISO-8859-14 ISO-8859-15 ISO-8859-16 KOI8-R KOI8-U TIS-620 VISCII
CHARMAP="UTF-8"

# The codeset determines which symbols are supported by the font.
# Valid codesets are: Arabic Armenian CyrAsia CyrKoi CyrSlav Ethiopian
# Georgian Greek Hebrew Lao Lat15 Lat2 Lat38 Lat7 Thai Uni1 Uni2 Uni3
# Vietnamese. Read README.fonts for explanation.
CODESET="Lat15"

# Valid font faces are: VGA (sizes 8, 14 and 16), Terminus (sizes
# 12x6, 14, 16, 20x10, 24x12, 28x14 and 32x16), TerminusBold (sizes
# 14, 16, 20x10, 24x12, 28x14 and 32x16), TerminusBoldVGA (sizes 14
# and 16), Fixed (sizes 13, 14, 15, 16 and 18), Goha (sizes 12, 14 and
# 16), GohaClassic (sizes 12, 14 and 16).
FONTFACE="Fixed"
FONTSIZE="16"

# You can also directly specify nonstandard font and ACM to load:
# FONT=/usr/local/share/funnyfonts/sarge16.psf
# ACM=/usr/local/share/consoletrans/my_special_encoding.acm

# The following variables describe your keyboard and can have the same
# values as the XkbModel, XkbLayout, XkbVariant and XkbOptions options
# in /etc/X11/xorg.conf.
XKBMODEL="pc104"
XKBLAYOUT="ca"
XKBVARIANT="multix"
XKBOPTIONS="lv3:ralt_switch"

# Do not update the following md5 sum if you change
# /etc/console-setup/boottime.kmap.gz and Debconf will not overwrite
# your custom keymap. Do not update it even if you want to make
# Debconf overwrite it. Instead simply specify the empty string as
# a md5 sum.

BOOTTIME_KMAP_MD5=""

[David D Miller (justdave)]

Intel/nVidia Mac Mini, dpkg-reconfigure console-setup did not fix. Keyboard works fine in console but not in X.

I ended up resolving this by going into the keyboard setup preferences window from Gnome, going to the Layouts tab, and clicking on the keyboard model button where it said "Macintosh". I then clicked on Apple for manufacturer, and picked "Macintosh" again for the keyboard model, and saved it. Then my keyboard worked again. Yes, this is the same thing it was supposedly already set for. Probably just needed to be re-saved somewhere or something.

[David D Miller (justdave)]

I spoke too soon, my workaround did not survive a reboot. However, changing the keyboard layout from Apple:Macintosh to Apple:Apple *did* survive a reboot, and did solve the problem for me.