9 Sep
2008
9 Sep
'08
13:48
https://bugzilla.novell.com/show_bug.cgi?id=398774
User fabien@crespel.net added comment
https://bugzilla.novell.com/show_bug.cgi?id=398774#c25
Fabien Crespel <fabien@crespel.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fabien@crespel.net
Status|RESOLVED |REOPENED
Resolution|INVALID |
Version|RC 1 |Final
--- Comment #25 from Fabien Crespel <fabien@crespel.net> 2008-09-09 07:48:44 MDT ---
I'm reopening this bug as it *is* a regression from an user's point of view. As
andrea said, it did work out-of-the-box in 10.3 and stopped working in 11.0. I
was also affected by this regression on my ASUS laptop, and after going through
the issue, I would say there are multiple problems and multiple solutions. So
read on for a detailed technical explanation and my suggestions to fix this :-)
In 10.3, the hotkey-setup package was used to support multimedia/laptop keys.
>From what I've seen, it did the following:
- use setkeycodes in *.hk files to bind scancodes to keycodes, depending on
the laptop model
- launch a kind of "ACPI-to-INPUT proxy" daemon (acpi-keys) to convert ACPI
notifications from laptop drivers without a proper INPUT subsystem
(like asus-laptop) to actual keys
- provide an xmodmap file to bind keycodes to keysyms (not sure how it was
really applied though)
No matter what keyboard type was selected in SaX2/xorg.conf, hotkeys were
properly recognized (so no need for a personal .xmodmap in the home folder). It
"just worked".
However, this hotkey-setup package was removed in 11.0. I can easily understand
why, as a developer: it's very hackish and would be a burden in the future, and
just doesn't do things the right way:
1. the keycode-to-scancodes conversion should be supported in X out-of-the-box
2. the ACPI proxy is just Bad because the laptop driver itself should act as an
input driver (making maintenance easier because the key mappings would be done
by the driver and/or by HAL).
For 1, I believe the solution was to make the 'microsoftpro' keyboard type the
default in SaX2. This has been done in bug #210881 - BUT not for some
keyboards! indeed, there are still several pc102 keyboards there for French,
Italian, Spanish and other keyboards. This explains why I (fr-latin1 keyboard)
and Andrea (it keyboard) are affected by the problem, but not people with US or
German keyboards for example. I have reopened bug #210881 in hope this will be
fixed for 11.1 (if not already done in Factory).
For 2, there is really no proper solution until someone updates the laptop
driver, AFAIK. For 11.0 the only fix is to install hotkey-setup (even though
the Xmodmap hacks shouldn't be needed with the microsoftpro keyboard). For
11.1, I'm not sure what would be an acceptable solution if laptop drivers are
still not updated: use a temporary solution (acpi-keys) that "just works" for
the User, or purposefully keep it broken to raise attention to the problem?
Anyway, to sum up all this, in openSUSE 11.0 people only have working laptop
hotkeys if they have a microsoftpro default keyboard (depending on language)
AND have a laptop driver using the INPUT subsystem. For any other case, they're
screwed and see it as a regression, as hotkey-setup provided this functionality
in 10.3.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.