presario - some hotkeys not working

[Matthew East]

Model: Compaq Presario 2100
Latest Breezy

Some hotkeys aren't working. full report is on
https://wiki.ubuntu.com/LaptopTestingTeam/CompaqPresario2100. Hotkeys that are a
problem are:

Function and backspace (mute); separate mute button - these seem to do something
weird to gnome: I can't type anything and I can't open any of the menus with the
mouse until I Ctrl Alt Backspace kill gnome and restart gdm. Then I can log in
and type normally.

Application hotkeys: the envelope (open email) and magnifying glass (open
browser) work fine, but the others don't do anything: i (no idea), padlock (lock
screen) and question mark (help application?) don't do anything.

All other hotkeys seem to be tip top. :)

To be honest, this is not a big deal (hence the low severity), but mute would be
nice.

Matt

https://wiki.ubuntu.com/LaptopTestingTeam/CompaqPresario2100: https://wiki.ubuntu.com/LaptopTestingTeam/CompaqPresario2100

[Matthew East (mdke)]

(In reply to comment #0)
> Model: Compaq Presario 2100
> Latest Breezy

snip

> Function and backspace (mute); separate mute button - these seem to do something
> weird to gnome: I can't type anything and I can't open any of the menus with the
> mouse until I Ctrl Alt Backspace kill gnome and restart gdm. Then I can log in
> and type normally.

I'm not seeing this problem anymore. However the missing hotkeys are still the
same ones.

Matt

[Matthew East (mdke)]

(In reply to comment #1)
> (In reply to comment #0)
> > Model: Compaq Presario 2100
> > Latest Breezy
>
> snip
>
> > Function and backspace (mute); separate mute button - these seem to do something
> > weird to gnome: I can't type anything and I can't open any of the menus with the
> > mouse until I Ctrl Alt Backspace kill gnome and restart gdm. Then I can log in
> > and type normally.
>
> I'm not seeing this problem anymore. However the missing hotkeys are still the
> same ones.

I AM still seeing this problem still. Even if it can't be fixed I would really
appreciate a workaround to disable this hotkey from doing this! It doesn't mute
so I'd rather have it turned off than a hotkey which crashes gnome. Bumping
severity up to normal.

[Matthew East (mdke)]

Update on this. The mute hotkey does not crash Gnome anymore in current dapper.

The hotkeys not working on this machine are therefore:

mute
"i"
lock screen
help application

[Matthew East (mdke)]

oh, and hibernate (dapper only)

[Matthew East (mdke)]

Damn, sorry for spam, but the "mute hotkey crashes GNOME" bug is still there: argh!!

[Matthew Garrett (mjg59)]

The crash should be fixed in the latest X upload. Could you possibly attach the
output of

sudo dmidecode

and let me know what keycodes (if any) are generated by the keys? You can check
that by running xev, focusing the window and pressing the keys. If they produce
nothing, is anything logged in dmesg?

[Matthew East (mdke)]

(In reply to comment #6)
> The crash should be fixed in the latest X upload.

Afraid not :( It's so annoying!!!

> Could you possibly attach the
> output of
>
> sudo dmidecode

Will attach it now.

> and let me know what keycodes (if any) are generated by the keys? You can check
> that by running xev, focusing the window and pressing the keys. If they produce
> nothing, is anything logged in dmesg?

Nothing in xev or dmesg.

[Matthew East (mdke)]

Created an attachment (id=5592)
output of dmidecode

[Matthew Garrett (mjg59)]

Ok. Can you switch to the console, run showkey, press each key in turn and
record what they generate?

[Matthew East (mdke)]

(In reply to comment #9)
> Ok. Can you switch to the console, run showkey, press each key in turn and
> record what they generate?

The mute key (which produces the crash), generates 0x71.

The other keys which don't do anything, don't generate anything.

[Matthew Garrett (mjg59)]

Right. 0x71, and then nothing on keyup? We may be able to work around that. The
other keys are going to be more difficult. Can you try using omke.pl (I'm just
about to attach it) as follows:

./omke.pl -k 1

and see if the keys now generate events? If so, which events?

[Matthew Garrett (mjg59)]

Created an attachment (id=5601)
omke.pl

[Matthew East (mdke)]

(In reply to comment #11)
> Right. 0x71, and then nothing on keyup? We may be able to work around that.

Yes, just 0x71. i'd really appreciate something which just disables it to
prevent the crash, but if you can have it working mute, then so much the better ;)

> The
> other keys are going to be more difficult. Can you try using omke.pl (I'm just
> about to attach it) as follows:
>
> ./omke.pl -k 1
>
> and see if the keys now generate events? If so, which events?

Still nothing in showkey after loading that I'm afraid.

[Paul Sladen (sladen)]

Googling around a bit I found:

  http://lists.debian.org/debian-laptop/2003/04/msg00375.html

Could you check if there is an option:

  Legacy USB Support

in the BIOS and try to disable it. Does this help?

[Darryl Clarke (dclarke)]

I have issues with my presario keys too.

the Search glass, Lock, and '?' keys do not work for me.

Also, Fn-F12 (Hibernate?) doesn't appear to work.

Everything else works - although I had to use the okme.pl script to get the mute button on the side to work.

[Brian Hartvigsen (tresni)]

I'm also experiencing this issue. The okme.pl script does enable the mute button. I get no output from the other buttons, same as everyone else.

Mute is not crashing anything in Feisty Fawn.

[Brian Hartvigsen (tresni)]

Just noticed something in dmesg:

[ 4470.236000] atkbd.c: Use 'setkeycodes e073 <keycode>' to make it known.
[ 4470.248000] atkbd.c: Unknown key released (translated set 2, code 0xf3 on isa0060/serio0).
[ 4470.248000] atkbd.c: Use 'setkeycodes e073 <keycode>' to make it known.
[ 4472.656000] atkbd.c: Unknown key pressed (translated set 2, code 0xf1 on isa0060/serio0).
[ 4472.656000] atkbd.c: Use 'setkeycodes e071 <keycode>' to make it known.
[ 4472.668000] atkbd.c: Unknown key released (translated set 2, code 0xf1 on isa0060/serio0).
[ 4472.668000] atkbd.c: Use 'setkeycodes e071 <keycode>' to make it known.
[ 4473.732000] atkbd.c: Unknown key pressed (translated set 2, code 0xf0 on isa0060/serio0).
[ 4473.732000] atkbd.c: Use 'setkeycodes e070 <keycode>' to make it known.
[ 4473.740000] atkbd.c: Unknown key released (translated set 2, code 0xf0 on isa0060/serio0).
[ 4473.740000] atkbd.c: Use 'setkeycodes e070 <keycode>' to make it known.

That is what happens for the Search (e073), Lock (e071), and Question (e070) keys respectively after using omke.pl. Without omke.pl the keys do not register at all. Stumbled on this by accident, hope it helps!

tresni@ubbylappy:~$ sudo dmidecode -s system-manufacturer
Hewlett-Packard
tresni@ubbylappy:~$ sudo dmidecode -s system-product-name
Presario 2100 (DA722AV)
tresni@ubbylappy:~$ sudo dmidecode -s system-version
KAM1.59

[Martin Pitt (pitti)]

Fixed upstream in commit 04c6b22 according to Brian's data.

[Launchpad Janitor (janitor)]

This bug was fixed in the package udev - 146-1

---------------
udev (146-1) karmic; urgency=low

  * New upstream release:
    - udevadm trigger "--retry-failed" replaced by "--type=failed"
    - RUN "ignore_error" option replaced by "fail_event_on_error"
    - Added HP Presario 2100 keymap. LP: #20223.
    - Added more keymap coverage for Compaq Evo models. LP: #35382.
    - Added Fujitsu Amilo M keymap. LP: #48547.
    - Added Compal Hel80i keymap. LP: #198530.
    - Added Zepto ZNote keymap. LP: #400252.
    - Added Everex Stepnote XT5000T keymap. LP: #400921.
    - Added rules to switch mode of Huawei E1550 GSM modem. LP: #401655.
    - Various other keymap and modem updates.

  [ Martin Pitt ]
  * debian/control: Add missing Breaks: casper (<< 1.174) to avoid breaking
    upgrades from jaunty in wubi installations. (LP: #400138)

 -- Scott James Remnant <email address hidden> Tue, 25 Aug 2009 13:45:17 +0100