Mailinglist Archive: opensuse-bugs (6264 mails)

< Previous Next >
[Bug 562090] New: SLES 11: Xvnc doesnt handle Caps lock
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Thu, 10 Dec 2009 08:47:51 +0000
  • Message-id: <bug-562090-21960@xxxxxxxxxxxxxxxxxxxxxxxx/>
http://bugzilla.novell.com/show_bug.cgi?id=562090

http://bugzilla.novell.com/show_bug.cgi?id=562090#c0


Summary: SLES 11: Xvnc doesnt handle Caps lock
Classification: openSUSE
Product: openSUSE 11.1
Version: Final
Platform: All
OS/Version: SLES 11
Status: NEW
Severity: Normal
Priority: P5 - None
Component: X.Org
AssignedTo: bnc-team-xorg-bugs@xxxxxxxxxxxxxxxxxxxxxx
ReportedBy: nice@xxxxxxxxxxxxxxx
QAContact: xorg-maintainer-bugs@xxxxxxxxxxxxxxxxxxxxxx
Found By: ---
Blocker: ---


User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; hu-HU; rv:1.9.1.5)
Gecko/20091103 SUSE/3.5.5-1.1.2 Firefox/3.5.5

https://bugzilla.novell.com/show_bug.cgi?id=400520 is basically solved in SLES
11, but Xvnc is still totally unaware of caps lock. So, it seems to me that you
added some own patches to Xvnc to solve the problem of accentuated characters
(why don't you send it to upstream and to openSUSE?), but caps lock is still
unsupported.

However, I realized that giving the -kb commandline option to Xvnc (by editing
/etc/xinet.d/vnc) eliminates this problem, and makes Xvnc to be seem to as
perfect as in the good old days. Why does Xvnc the xkb extension anyway?
Changing the keyboard layout on the server side seems to be senseless for me.

Reproducible: Always

Steps to Reproduce:
1. Enable VNC management on a SLES box
2. Try to connect to it.
3. Use caps lock
Actual Results:
It won't have any effect

Expected Results:
It should work

--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >
Follow Ups