|
Bugzilla – Full Text Bug Listing |
| Summary: | NX (or knx?) does not recognize AltGr key combinations | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | Joerg Reuter <jreuter> |
| Component: | KDE | Assignee: | Stefan Dirsch <sndirsch> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Enhancement | ||
| Priority: | P5 - None | CC: | dmueller, eich, joe, kpfeifle, ms, sndirsch |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
<!-- SBZ_reproduce --> Start knx, connect and try to create a "@" character with a German keyboard... Marcus, you still remember how you've fixed this problem? I called setxkbmap after the session has been established but that's not a fix just a workaround Thanks. This works. IMHO this is something, which should be handled by knx. Kurt? NX --> knx I think this is a bug (even a recurring one) in a
a) either the NX libraries,
b) or in KDE in general,
not kNX specifically. Because it happened with the !M NX Client too in my former
KDE sessions. I have not yet tracked it down and dont have any time currently
either. What I found as workaround was; go to KDE Control Center ("kcontrol"),
keyboard layout settings (I always use the "Search" tab for fast-finding)
*inside* *the* *NX* *session*, where I then "Enable keyboard layouts". Then
select a 102-key or a 104- or 105-key layout (sorry, can't remember which) and
make that permanent. That is a permanent workaround for me and I am not missing
any key (but then, I am not an Emacs user-fingertwister...).
AFAIR the problem doesnt occur in the "US layout" setting either....
Someone with more time should try to verify if this also occurs in a GNOME
session, or in a GNOME app started inside KDE, or in an Xterm. And then submit
the appropriate bug report to the correct addressee. I didnt.
Thanks, Kurt. Jörg, could you please try this workaround? That works, thanks. I see this one in the log of KNX: knx: receivedFromSSH: startsession --session="baker" --link="modem" --geometry="800x600+0+0" --type="unix-kde startsession --session="baker" --link="modem" --geometry="800x600+0+0" --type="unix-kde" --screeninfo="1152x8 Therefore I think knx should also be able to transfer the current keyboard layout, but I have no idea how to detect the current keyboard layout ... maybe this one can be used:
xkbctrl `cat /etc/sysconfig/keyboard |\
grep ^KEYTABLE | cut -f 2 -d= |\
tr -d \"` | grep Apply | cut -f2 -d:
Thanks. This should work in many cases (in a SuSE environment). But it should be configurable in KNX. --> enhancement *** Bug 66784 has been marked as a duplicate of this bug. *** I don't think there went any kind of work into knx since it's first introduction ;( And I kind of don't see us doing it either. also happens with standard nxclient, not only knx. reassign maintainer . only happens after one suspend/resume cycle. a just freshly started session works fine. So does a "setxkbmap de" help after the resume? yes, it does help. Ok. Stupid question. Are you doing the suspend/resume on the machine on which the nxlcient runs or on the machine, on which the Xsession runs? BTW, if you have any idea how to fix this issue, please let me know. ah, thats not acpi / swsuspend suspend/resume I'm talking about but the NX suspend/resume. therefore, I'm doing this via nxclient (closing the window without ending the session running inside which then pops up a question where you can answer "Suspend"/"Terminate"/"Cancel"). I would assume that after resume the keyboard maps are no longer set correctly. NX does some fancy stuff via xrandr etc to adjust the NX session to the new display, perhaps there is a bug somewhere. the x keyboard mapping stuff is mostly black magic to me. > ah, thats not acpi / swsuspend suspend/resume I'm talking about but the NX
> suspend/resume.
Good to know. :-) This means that NX suspend/resume somewhat works for you. It never did for me. Maybe Kurt can help here.
JFYI. JFYI, Matthias. This is a bugreport, which is assigned to Egbert/me or with Egbert/me in CC or reported by Egbert/me. I can't reproduce this keyboard issue any longer. Check on the machine, on which the NX sessions runs, with "ps" that nxagent is started with the "-kbtype pc105/de" option or the keyboard geometry/layout, which you currently use on your regular Xserver. Even suspend/resume of the NX session works for me now. Use the latest NX/FreeNX packages in our buildservice (project NX) + nxclient (3.0) from nomachine as NX client. knx no longer works. qtnx is still problematic. |
Trying to type any AltGR key combination in an NX session (for example, AltGr-Q) does not produce the desired character ("@") but only the key pressed additionally to AltGr ("q").