|
Bugzilla – Full Text Bug Listing |
| Summary: | Caps Lock, Num Lock & Scroll Lock LED Problem | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | Andrea Colangelo <warp10> |
| Component: | Other | Assignee: | E-mail List <bnc-team-screening> |
| Status: | RESOLVED WONTFIX | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Minor | ||
| Priority: | P5 - None | CC: | cyberorg, suse-beta |
| Version: | Beta 1 | ||
| Target Milestone: | --- | ||
| Hardware: | i686 | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
/etc/sysconfig/keyboard
/etc/sysconfig/keyboard Output of hwinfo --keyboard Output of ls -al from /var/log/YaST2 |
||
|
Description
Andrea Colangelo
2006-01-29 00:41:46 UTC
Maby your keymap is wrong or messed up. Please attach your /etc/sysconfig/keyboard and check out what keycodes are getting produced by pressing the corresponding keys. Created attachment 65746 [details]
/etc/sysconfig/keyboard
The keycodes, as displayed by showkey in a console, are: Caps Lock: 58 (press/release) Num Lock: 69 (press/release) Scroll Lock: 70 (press/release) This looks right... Which keyboard-definition did you select in YaST during the installation? Please attach the yast logfiles. I don't know where are yeast logfiles, if you could tell me how, I'll attach here. Anyway, by Yast2, I see my keyboard mapping is "Generic 104-key PC" with Italian Layout. Hope this can help. This might explain it. Before we go on, try selecting another keyboard-definition using YaST and see if the problem still exists. Are the keys really swapped (do they work as they should?). Italian layout should be choosable. If it doesn't work: Please attach the output of `hwinfo --keyboard', the file /etc/sysconfig/keyboard and the logfiles, which you can find in /var/log/YaST2. Which keyboard did you select during the installation? The keyboard selected during installation was Generic 102 keys. I tried many other (Generic 101, 102Intl, 104, 105Intl and ACPI Standard) without any result. I'm not sure that my poor english (sorry!) let you understand that keys work well. The problem is just with Leds, and especially with Caps Lock Led. They don't correspond to the real activation of the three Locks, but the Locks work well (on Caps Lock switched on I can write capitalized, on Num Lock I can use embedded numeric keyboard, and so on). I am attaching the files, but I'm not sure which are the right YaST2 logfile. I attached the output of ls -al, so please tell me which files to attach, and I'll do it immediately. Created attachment 66338 [details]
/etc/sysconfig/keyboard
Created attachment 66339 [details]
Output of hwinfo --keyboard
Created attachment 66340 [details]
Output of ls -al from /var/log/YaST2
After all this does not look like a YaST problem to me, nut to mis-interpreted keyboard-events. Juergen: Can you provide a clue here? If this is nothing for you, just assign it back to us. On 10.1 Beta 8, LED for NUM LOCK is OFF when NUM LOCK is actually turned ON, and turns on when NUM LOCK is switched off. Jürgen, would you mind responding to the question and potentially assign this back? The LEDs are normally handled at kernel level. The kbd package has /bin/setleds, which can show you the state of the locks, and the state of the LEDs separately. I cannot say much ore here. Back to mgross. I'm closing this for now. If this problem still exists in the current release (RC3), please reopen. And please don't assign bugs directly to me. see last comment Problem seems to have been fixed today.(5 May). Anyway the problem I had reported would have been cause by Xgl and that seems fixed at least. see http://webcvs.freedesktop.org/xorg/xserver/xorg/ChangeLog?rev=1.199.2.69&only_with_tag=xgl-0-0-1&view=markup -J |