- This topic is empty.
-
AuthorPosts
-
June 20, 2011 at 2:22 pm #6696
Hello!
I’m about to set up some X50L devices connected via WLAN to our Citrix XenApp 4.5 farm. Almost everything works with one exception: The Caps/Caps Lock keys behave weird. At first, the Shift key doesn’t work, but if I release it, all letters are typed in capital letters (as if Shift Lock has been pressed instead), if I press Shift Lock, the typed letters are in lowercase again. To get back upper-case letters, I have to press Shift twice (!) – really strange.
This behaviour does only occur unter the following circumstances:
-
* It’s an ICA session. In Control Center, an xterm windows, a local Firefox or even a RDP session, the keys work as they should.
* No Ethernet cable is connected to the device at boot time (i.e. the first connection is done via WLAN). If an Ethernet cable is connected at boot time, the keys work fine, even if I pull it afterwards and the ICA session will be reconnected via WLAN.
So it looks like an ICA problem, but why does it only occur with WLAN connections? Are there any ICA parameters that should be changed?
The versions:
SUSE Linux Enterprise: 11.0.112
SLETC: 1.4.1115
OS Version: 2.6.27.42-0.1-pae
ICA client module: ica-11.100-01.09Thank you!
June 21, 2011 at 7:58 am #20626This is a known issue. Upgrade your X50L unit to either SLETC11 Build 11.0.139 or SLETC11 SP1 Build 11.1.012.
CG
June 21, 2011 at 10:53 am #20628@ConfGen wrote:
This is a known issue. Upgrade your X50L unit to either SLETC11 Build 11.0.139 or SLETC11 SP1 Build 11.1.012.
Thank you for this hint, unfortunately, it hasn’t solved the problem. After the upgrade, the symptoms are exactly as before. Now the following version is installed (it’s the most recent from the Wyse website):
SUSE Linux Enterprise: 11.1.015
SLETC: 1.4.1115
OS Version: 2.6.32.12-0.7-pae
ICA client module: ica-11.100-01.28Any more ideas?
June 21, 2011 at 11:24 am #20629Looks like the firmware version was wrong. Should be fixed in 11.1.031. Wyse is going to post this the next days.
CG
June 21, 2011 at 11:24 am #20630Looks like the firmware version was wrong. Should be fixed in 11.1.031. Wyse is going to post this the next days.
CG
July 1, 2011 at 10:26 am #20697Just want to tell everybody that the recently released firmware 11.1.031 indeed seems to have fixed this issue.
-
AuthorPosts
- You must be logged in to reply to this topic.