Non-US keyboard layout problem with VNC

Hi everyone,
I've got an arch box at work running tigervnc through an ssh tunnel so that I can work from home when I need to.
Everything is great, as long as I'm using and ASCII keyboard layout.
When I switch layouts, the keystrokes just don't get through to the server.
Here's what I use to switch layouts:
setxkbmap -layout us,ru -option 'grp:alt_shift_toggle'
So I need to type in russian, and I hit alt-shift, as usual, and start typing, but nothing is echoed back to me. I can tell that the keystrokes are just not getting to the destination because if I'm at a terminal and I'm switched to the ru layout and I type something and hit enter, I just get a newline, as if there was nothing typed at all.
Any ideas?

Hi,
Why are the characters mixed up in the session?
This issue can occur if the keyboard language has been switched on the remote PC while running a remote desktop session. In the case you would like to switch to a different keyboard
language follow these instructions.
Important:
The remote PC selects the system language of the device running the remote desktop client and not the keyboard language. When switching the keyboard language on your device,
you need to manually switch the keyboard language on the remote PC.
1. Open settings on your device.
2. Tap General and then tap International.
3. Tap Language and select the language running on the remote PC.
4. Open the RD Client and connect to the remote PC and check if the Windows keyboard language matches the language that you selected.
Quote from
Remote Desktop Client on Mac: FAQ
Thanks.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Similar Messages

Dwm and non-english keyboard layouts problem

Hi all,
I am using dwm 5.5. I'm Greek so I change between keyboard layouts all the time,
see the relevant xorg.conf section:
Section "InputDevice"
Identifier "Generic Keyboard"
Driver "kbd"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "us,gr"
Option "XkbVariant" ","
Option "XkbOptions" "grp:alt_shift_toggle,grp_led:scroll"
EndSection
Now the thing is that whenever I switch to Greek (by pressing Alt+Shift) the
dwm tags (1,2,...,9) are not clickable (keyboard shortcuts do work
though, so it's not a very big problem).
Do you have any ideas about how to fix that behavior? I'd go to the dwm irc
channel and ask them, but I'll be a "newbie asking stupid questions" so I
preferred to ask here
Thanks in advance
Last edited by geo909 (2010-01-08 17:23:29)

thayer wrote:Your best bet would be to post your problem to the dwm mailing list:
[email protected]
Will do...
Thanks!

Keyboard Layout Problems with OS X Mavericks on MacBook

My brother and I have a Early 2009 MacBook that received succesive updates on OS X over the past four years: it went from Leopard to Snow Leopard to Lion to Mountain Lion. But this year, we decided to upgrade it from a clean install of Mavericks.
It went fine, but... the keyboard is acting in a terrible way. The layout is bugged! The left shift key enters the "Y" letter, while return enters the "/" key... I've just tried everything to fix this resetting NVRAM and SMC, but nothing has worked.
Somebody else is having this problem? Could a software update fix it?

See if a Safe Mode boot helps...
Startup your Mac in Safe Mode
A Safe Mode boot takes much longer than a normal boot so be patient.
Once you are in Safe Mode, click Restart from the Apple () menu.

[LR2 - SOLUTION] Using Lightroom in englsih with a non-english keyboard layout

Hi, Many of us, non native english speaking LR users, are using LT in english on a system having a non-US keyboard layout. The conseqeunce of this is that we can't reach a lot of keyboard shortcuts because LR doesn't offer any interface for configuring them. However, there's a workaround. I'll explain here what I did for the french language but you can apply this to your own language. For the non english languages, the keyboard shortcuts are defined in C:\Program Files\Adobe\Adobe Photoshop Lightroom 2\Resources\<language>\TranslatedStrings.txt. If you are using LR in english, this file is not used and there's no similar file in C:\Program Files\Adobe\Adobe Photoshop Lightroom 2\Resources\en. But you can create one containing only the shortcuts that you need. I have created a new TranslatedStrings.txt file containing only the keyboard shortcuts defined for the french version. I did this by copying only the lines containing the following sequences: ....Key=... ....KeyShifted=... ...AgPanel/LeftPanelShortcut... ...AgPanel/RightPanelShortcut... ...MenuShortcut/DecreaseRating= ...MenuShortcut/IncreaseRating= (french users can find this file here: http://www.mainsoft.fr/Files/LR/TranslatedStrings.txt . Copy this file to "C:\Program Files\Adobe\Adobe Photoshop Lightroom 2\Resources\en" and relaunch Lightroom. Now you have the same keyboard shortcuts as when using LR in french. Interestingly enough, if you hit ctrl + < , the LR keyboard shortcut panel is displayed and it shows your new shortcuts. Again, you can do the same for your own language by copying the specified strings from the relevant folder. Hope this helps. -- Patrick Philippot MainSoft Consulting Services www.mainsoft.fr

Yes… I would at a minimum contact Apple sales or AppleCare regarding this. You have two options though. You can ask for a new one, given they can't simply swap out a keybaord you need to exchange the whole thing.
Otherwise, you can use it as a bargaining chip and say ask for a free external International English keyboard and a discount on your next Apple Store purchase… for instance.
Regardless, be polite yet firm with them as you did not get what you ordered.

Non-english keyboard layouts work in some programs, not others

In some programs, I can set a non-English keyboard layout and have the appropriate behavior when it comes to diacritics - in, say, the brazilian layout, hitting { then a will give me a á, and so on. It works perfectly fine in Firefox and xchat, for instance. But in other programs, opera and openoffice to name two I've tried, this fails. I either get a garbage character when I hit the first diacritic key or I just get the diacritic by itself and then the accentless vowel: ´a.
Completely non-English characters still work fine; I can get ç in the Brazilian layout and ñ in Latin American and the Georgian one works fine too, since Georgian doesn't have diacritics I presume. It's just diacritics that don't work.
I first noticed this problem after I installed SCIM, so I assume it has something to do with the SCIM installation, but I don't know what I did in the process of installing it that would've messed things up.

thayer wrote:Your best bet would be to post your problem to the dwm mailing list:
[email protected]
Will do...
Thanks!

NCS and non US keyboard layout - Guest - Email ID and @

Problem:
The problem is that we cannot email the Guest Account Details to the guest, because the popup where we fill in the email of the guest - Email ID - Does not recognise the @ when using non US Keyboard layout.
When i use my local keyboard layout (Danish) and press AltGr+2 (this is the keyboard "shortcut" for @) it writes nothing.
When i switch to US keyboard layout and press Shift+2 it writes @ fine.
Version:
Tried this in both 1.0 and I just upgraded to 1.1 and it is still the same.
Does anyone know of a open BugID that addresses the following problem on the NCS Lobby Ambasador page ?

Thomas,
Have you tried it from different machines and different OSes and confirmed that the common denominator is NCS and not your specific KB/OS setup?
Justin
Sent from Cisco Technical Support iPhone App

Screen locked with non-English keyboard layout selected

Hello,
I use two keyboard character sets for keyboard. The switch between them is Command-Space.
I also have password requirement for waking up or going from screen saver.
Now if screensaver starts with non-English layout selected, I'm not able to login:
password is not accepted because keyboard layout is not English and switching
to English layout does not work in unlocking window.
Is there any way to change layout while in the unlock window?
Thanks

Yes you are right, this is not a bug, it's just bad user interface. Just imagine the following scenario...
Writing a paper, switching to Greek to enter a couple of characters and leaving the mac idle for 5 mins.
The lock screen comes up asking for a password, unfortunately the user didn't change the language
before the mac was left idle and there is no option to change the language in the lock screen.
User has to hard reset to access the mac and let's hope that the user was saving his paper frequenlty.
So from a coding point of view this is not a bug, but from a user interface design it is a huge flaw

Some applications don't put accents with non-english keyboard layouts

I'm using a Portuguese keyboard with three different macs running Mac OS Tiger 10.4.8/9. Some applications (like Motion 2 and Swift Publishing 2) don't allow writing some accented characters, like (è) or (ê), that are accessed by Shift+normal key, but they do display correctly other accented letters, for instance (é), witch are accessed directly without the Shift key. This happens only in some applications and with a european keyboard layout (I tried it also with the spanish and french keyboards layouts), but not with other applications (it works all right with Word or iPhoto) and the english keyboards.
Any sugestion as how to solve this? If I create the text in some other application and paste it in Motion it works! But it's a drag.
iMac Core2Duo 20" Mac OS X (10.4.8) MacBook Core2Duo MacPlus

Hey KDCruz,
Thanks for the question. Let's see if we can isolate the issue further, the following article has some great troubleshooting steps:
One or more keys on the keyboard do not respond
http://support.apple.com/kb/TS1381
Thanks,
Matt M.

Keyboard layout problems in Gnome

I'm not sure if it was a recent upgrade that did it or not, but in gnome my keyboard layout is only half right. I checked the keyboard manager in the gnome menu and it was set to Generic 105 key (INTEL).
In xorg.conf the keyboard is listed as pc105. In KDE the keyboard works normally.

bgodea wrote:I changed the Gnome keyboard layout to "104 key PC" and also tried changing my xorg.conf, but I still have the same problem. In non-graphical and KDE it works fine
You also have to setup a valid layout for this kind of keyboard. That is done in the same dialog field. Then, what do you mean with "tried"? First off, if Gnome and X disagree about keyboard layout, Gnome complains loudly. Thus KDE is unilaterally setting the layout to something it likes. Check your Kconfig to find out what it is. Then find the section named InputDevice in /etc/X11/xorg.conf that looks something like this:
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbLayout" "us"
Option "XkbRules" "xorg"
Option "XkbModel" "pc104"
EndSection
Change it to resemble this example, if it doesn't. Check if your ServerLayout actually uses this InputDevice. Finally, is there anything else we should know about your keyboard? Do you run XGL/AIGLX?
Last edited by Captain Spaulding (2007-04-03 16:50:46)

MSI, please stop using non-standard keyboard layouts.

God dam it MSI, why do you insist on messing with layout of the bottom row of the keyboard?
You get everything else right, but for some reason when it comes to the bottom row of keys you want to say "Industry standards? 20 years of tradition? Fack that, we're gonna move things around for no facking reason."
Explain to me why you feel the need to put a superfluous "\" key on the keyboard to the right of the space bar. Nobody wanted that, nobody was asking for that, nobody needs that. Why the hell did you do that?
Explain why the Menu key is missing in action.
Explain why you put the Windows key on the wrong side. And while you're at it, explain why you thought this clusterfack of having that second "\" key there in combination with the missing menu key being not where it is on top of the Windows key being in the wrong place was a good idea.
Bottom row of a standard keyboard layout goes like this:
Ctrl, Fn, Alt, Win, Space bar, Alt, Win, Menu, Ctrl.
MSI layout goes like.
Ctrl, Fn, Alt Space Bar, \, Alt Gr, Win, Ctrl!
WHY?!
MSI seems to think that having the keys in the right place so my fingers will know where they are without having to learn key placement all over again is a horrible idea. Instead they seem to think that my fingers should need to relearn the god dam keyboard all over again for no reason at all.
But hey, at least the kept the numpad the same, right?
GOD DAM IT MSI!
Aparantly MSI logic works like this:
Everyone uses the numpad.
Nobody uses the trackpad to game.
Delete that numpad that everyone uses, insert fancy trackpad that nobody will use.
Profit?
What the hell are you people smoking?
Seriously, when is the last time you gamed on a PC with anything other than a mouse in your right* hand? Do you ever use the trackpad when you game? Ever? I own two laptops and I never, ever use the useless trackpad. I hate trackpads. First thing I do when I buy a new laptop? I plug in a mouse. Second thing I do? Disable the god dam trackpad.
*Some left-handed use of mice can occur. See nearest lefties for details. May contain nuts. For external use only.

I had a Gateway FX years ago that was a great laptop, but the "fn" key was at the bottom left instead of ctrl. I used that laptop for years and I was never able to become accustomed to it for gaming (group select ctrl+# ffs) or word processing, so I feel your pain.
That being said, you should be able to re-bind your keys without any problem, and possibly pop off the keys themselves and move them to their new locations if they're the same size and you like that consistency. You can rebind via the registry, or certain bios, or w/ a third party application.
The track pad is essential if you've got limited space and/or aren't a twitch gamer. For non-real time games, there is hardly any advantage to using a mouse over a good track pad.

E70 Keyboard layout problems

I have a brand-new E70 bought from Expansys a week ago. I have the same problem reported by other here regarding incorrect keyboard layout (e.g. "(" key produces ")" and "/" produces ","). I have not upgraded the firmware, this is the way the phone was shipped.
I haven't found any solution in this forum or on the web yet. Any advice is appreciated. Thanks,
-- Terrence

bgodea wrote:I changed the Gnome keyboard layout to "104 key PC" and also tried changing my xorg.conf, but I still have the same problem. In non-graphical and KDE it works fine
You also have to setup a valid layout for this kind of keyboard. That is done in the same dialog field. Then, what do you mean with "tried"? First off, if Gnome and X disagree about keyboard layout, Gnome complains loudly. Thus KDE is unilaterally setting the layout to something it likes. Check your Kconfig to find out what it is. Then find the section named InputDevice in /etc/X11/xorg.conf that looks something like this:
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbLayout" "us"
Option "XkbRules" "xorg"
Option "XkbModel" "pc104"
EndSection
Change it to resemble this example, if it doesn't. Check if your ServerLayout actually uses this InputDevice. Finally, is there anything else we should know about your keyboard? Do you run XGL/AIGLX?
Last edited by Captain Spaulding (2007-04-03 16:50:46)

Keyboard mapping problem with sunstudio

I'm a new sunstudio user and am having trouble with a setup issue. When I run sunstudio 11 from a sunray with a Sun keyboard all works fine (except the sunray has far too small of screen and it drive me crazy). When I run with my linux desktop being the x-server then none of the special keys (home, end, arrows, backbspace, enter, etc.) work correctly in sunstudio. All other gui apps I've tried (gedit, gvim, staroffice, web browser, etc.) work fine from my linux/pc keyboard.
Using google I discovered xev. It shows the keycode and keysym that is interpreted for each keyboard stroke. When I compare the output from my linux/pc keyboard vs. the sun keyboard connected to the sunray I see the expected differences in keycode, but the keysym and resulting interpretation (e.g. BACKSPACE) is the same. Yet sunstudio ignores any keystroke except normal alphabet characters that come from my linux/pc keyboard.
When using my linux/pc keyboard I'm in one of two configs (both act the same):
- ssh -X hostname
OR
- Xephyr :1 -screen 1250x975 -query hostname &
Thanks for any help.
cb

There is a known problem related to control keys in the netbeans GUI.
http://www.genunix.org/wiki/index.php/Sun_Studio_FAQs#IDE_-TheSun_Studio_IDE_is_ignoring_my_control_keys
It's hard to tell from your message where the programs are
executing from.
Run two X programs next to each other, running on the same machine,
and displaying to the same X server. Verify that one of them can see
ALT keys (for example) and the other one can't. Then you know it's
a problem with the application program, and not due to your keyboard.
The Sun Studio IDE has no idea what physical keyboard you're using.
It only sees the keysyms from the X server.

Non-US keyboard layout in Xorg

Hello,
I have a Belgian keyboard layout and had some troubles with the Alt-Gr key.
We combine this key with other keys to generate special symbols like the Euro sign or the @ character for example.
I found several solutions on several websites but they didn't seem to work for me.
I now added the following line in my /etc/X11/xinit/xinitrc and now it's working:
setxkbmap be
Perhaps it's not a bad idea to add this setxkbmap command to the Xorg package, since I noticed I was not the only
one who was struggling with this problem.
Regards,
Solley

My XORG look like that:
Section "InputDevice"
# generated from default
Identifier "Keyboard0"
Driver "keyboard"
Option "XkbLayout" "us,lt"
Option "XkbOptions" "grp:alt_shift_toggle"
Driver "kbd"
EndSection

[E17] lock and keyboard layout problems when suspend

Hello,
I just installed E17 on my Dell Vostro laptop. The main problem I have is related to the suspend mode.
In settings > screen > screen lock, I enabled the option "lock on suspend" and the keyboard layout is selected to "be (default, basic)" (I have a belgian keyboard).
When I use the menu system > suspend, the screen is locked. But when I suspend my laptop by closing the lid (I see the power light indicator blinking on the side, so it's suspended) the screen is not locked when I open it.
Also related to the suspend mode. The layout is set to belgian (in the screen config as explained above but also in vconsole.conf and in /etc/X11/xorg.conf.d/10-keyboard.conf). When I put the luks decryption key or when E17 starts at boot, I have the right layout. However when I resume the laptop after being suspended, the layout is switched to qwerty (en_us I guess).
Any idea why ?
Thank you
PS: this problem is maybe more related to E17 than to Archlinux but I haven't found any forum about enlightenment. If you think I have better chances somewhere else, let me know.

I was having problems with E17 after a fresh install (mixer problem, key bindings, etc), and I fixed it by deleting the configuration files at
~/.e
as the wiki says.

[SOLVED] Keyboard layout problems

Hi community,
I fresh installed arch linux and I rly like it. After playing a little around and installing the awesome wm I can't set the croatian keyboard layout.
My xorg.config file:
Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
Option "Xinerama" "0"
EndSection
Section "Files"
EndSection
Section "InputDevice"
# generated from default
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/psaux"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
EndSection
Section "InputDevice"
# generated from default
Identifier "Keyboard0"
Driver "kbd"
Option "XkbModel" "logicd"
Option "XkbLayout" "hr"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Unknown"
ModelName "Arnos Instruments F-417"
HorizSync 24.0 - 80.0
VertRefresh 49.0 - 75.0
Option "DPMS"
EndSection
Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce 6600 GT"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
Option "TwinView" "1"
Option "TwinViewXineramaInfoOrder" "DFP-0"
Option "metamodes" "CRT: nvidia-auto-select +1920+0, DFP: nvidia-auto-select +0+0"
SubSection "Display"
Depth 24
EndSubSection
EndSection
My Xorg.0.log file:
[ 2186.778]
This is a pre-release version of the X server from The X.Org Foundation.
It is not supported in any way.
Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
Select the "xorg" product for bugs you find in this release.
Before reporting bugs in pre-release versions please check the
latest version in the X.Org Foundation git repository.
See http://wiki.x.org/wiki/GitPage for git access instructions.
[ 2186.778]
X.Org X Server 1.8.1.902 (1.8.2 RC 2)
Release Date: 2010-06-21
[ 2186.778] X Protocol Version 11, Revision 0
[ 2186.778] Build Operating System: Linux 2.6.34-ARCH x86_64
[ 2186.778] Current Operating System: Linux arch 2.6.34-ARCH #1 SMP PREEMPT Mon Jul 5 22:12:11 CEST 2010 x86_64
[ 2186.778] Kernel command line: root=/dev/sda5 ro
[ 2186.778] Build Date: 21 June 2010 12:01:49PM
[ 2186.778]
[ 2186.779] Current version of pixman: 0.18.2
[ 2186.779] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 2186.779] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 2186.779] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Jul 22 13:23:50 2010
[ 2186.779] (==) Using config file: "/etc/X11/xorg.conf"
[ 2186.779] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 2186.779] (==) ServerLayout "Layout0"
[ 2186.779] (**) |-->Screen "Screen0" (0)
[ 2186.779] (**) | |-->Monitor "Monitor0"
[ 2186.779] (**) | |-->Device "Device0"
[ 2186.779] (**) |-->Input Device "Keyboard0"
[ 2186.779] (**) |-->Input Device "Mouse0"
[ 2186.780] (**) Option "Xinerama" "0"
[ 2186.780] (==) Automatically adding devices
[ 2186.780] (==) Automatically enabling devices
[ 2186.780] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 2186.780] Entry deleted from font path.
[ 2186.780] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
[ 2186.780] Entry deleted from font path.
[ 2186.780] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/100dpi/,
/usr/share/fonts/75dpi/
[ 2186.780] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 2186.780] (WW) AllowEmptyInput is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
[ 2186.780] (WW) Disabling Keyboard0
[ 2186.780] (WW) Disabling Mouse0
[ 2186.780] (II) Loader magic: 0x7ce880
[ 2186.780] (II) Module ABI versions:
[ 2186.780] X.Org ANSI C Emulation: 0.4
[ 2186.780] X.Org Video Driver: 7.0
[ 2186.780] X.Org XInput driver : 9.0
[ 2186.780] X.Org Server Extension : 3.0
[ 2186.786] (--) PCI:*(0:1:0:0) 10de:00f1:0000:0000 nVidia Corporation NV43 [GeForce 6600 GT] rev 162, Mem @ 0xf8000000/16777216, 0xe0000000/268435456, 0xf9000000/16777216, BIOS @ 0x????????/131072
[ 2186.787] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 2186.787] (II) LoadModule: "extmod"
[ 2186.787] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
[ 2186.787] (II) Module extmod: vendor="X.Org Foundation"
[ 2186.787] compiled for 1.8.1.902, module version = 1.0.0
[ 2186.787] Module class: X.Org Server Extension
[ 2186.787] ABI class: X.Org Server Extension, version 3.0
[ 2186.787] (II) Loading extension MIT-SCREEN-SAVER
[ 2186.787] (II) Loading extension XFree86-VidModeExtension
[ 2186.787] (II) Loading extension XFree86-DGA
[ 2186.787] (II) Loading extension DPMS
[ 2186.787] (II) Loading extension XVideo
[ 2186.787] (II) Loading extension XVideo-MotionCompensation
[ 2186.787] (II) Loading extension X-Resource
[ 2186.787] (II) LoadModule: "dbe"
[ 2186.787] (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
[ 2186.787] (II) Module dbe: vendor="X.Org Foundation"
[ 2186.787] compiled for 1.8.1.902, module version = 1.0.0
[ 2186.788] Module class: X.Org Server Extension
[ 2186.788] ABI class: X.Org Server Extension, version 3.0
[ 2186.788] (II) Loading extension DOUBLE-BUFFER
[ 2186.788] (II) LoadModule: "glx"
[ 2186.788] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 2186.813] (II) Module glx: vendor="NVIDIA Corporation"
[ 2186.813] compiled for 4.0.2, module version = 1.0.0
[ 2186.813] Module class: X.Org Server Extension
[ 2186.813] (II) NVIDIA GLX Module 256.35 Wed Jun 16 19:10:31 PDT 2010
[ 2186.813] (II) Loading extension GLX
[ 2186.813] (II) LoadModule: "record"
[ 2186.814] (II) Loading /usr/lib/xorg/modules/extensions/librecord.so
[ 2186.814] (II) Module record: vendor="X.Org Foundation"
[ 2186.814] compiled for 1.8.1.902, module version = 1.13.0
[ 2186.814] Module class: X.Org Server Extension
[ 2186.814] ABI class: X.Org Server Extension, version 3.0
[ 2186.814] (II) Loading extension RECORD
[ 2186.814] (II) LoadModule: "dri"
[ 2186.814] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
[ 2186.814] (II) Module dri: vendor="X.Org Foundation"
[ 2186.814] compiled for 1.8.1.902, module version = 1.0.0
[ 2186.814] ABI class: X.Org Server Extension, version 3.0
[ 2186.814] (II) Loading extension XFree86-DRI
[ 2186.814] (II) LoadModule: "dri2"
[ 2186.814] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
[ 2186.814] (II) Module dri2: vendor="X.Org Foundation"
[ 2186.814] compiled for 1.8.1.902, module version = 1.2.0
[ 2186.815] ABI class: X.Org Server Extension, version 3.0
[ 2186.815] (II) Loading extension DRI2
[ 2186.815] (II) LoadModule: "nvidia"
[ 2186.815] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[ 2186.816] (II) Module nvidia: vendor="NVIDIA Corporation"
[ 2186.816] compiled for 4.0.2, module version = 1.0.0
[ 2186.816] Module class: X.Org Video Driver
[ 2186.816] (II) NVIDIA dlloader X Driver 256.35 Wed Jun 16 18:45:02 PDT 2010
[ 2186.816] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[ 2186.816] (++) using VT number 7
[ 2186.820] (II) Primary Device is: PCI 01@00:00:0
[ 2186.820] (II) Loading sub module "fb"
[ 2186.820] (II) LoadModule: "fb"
[ 2186.820] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 2186.821] (II) Module fb: vendor="X.Org Foundation"
[ 2186.821] compiled for 1.8.1.902, module version = 1.0.0
[ 2186.821] ABI class: X.Org ANSI C Emulation, version 0.4
[ 2186.821] (II) Loading sub module "wfb"
[ 2186.821] (II) LoadModule: "wfb"
[ 2186.821] (II) Loading /usr/lib/xorg/modules/libwfb.so
[ 2186.821] (II) Module wfb: vendor="X.Org Foundation"
[ 2186.821] compiled for 1.8.1.902, module version = 1.0.0
[ 2186.821] ABI class: X.Org ANSI C Emulation, version 0.4
[ 2186.821] (II) Loading sub module "ramdac"
[ 2186.821] (II) LoadModule: "ramdac"
[ 2186.821] (II) Module "ramdac" already built-in
[ 2186.821] (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
[ 2186.821] (==) NVIDIA(0): RGB weight 888
[ 2186.821] (==) NVIDIA(0): Default visual is TrueColor
[ 2186.821] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[ 2186.821] (**) NVIDIA(0): Option "TwinView" "1"
[ 2186.822] (**) NVIDIA(0): Option "MetaModes" "CRT: nvidia-auto-select +1920+0, DFP: nvidia-auto-select +0+0"
[ 2186.822] (**) NVIDIA(0): Option "TwinViewXineramaInfoOrder" "DFP-0"
[ 2186.822] (**) NVIDIA(0): Enabling RENDER acceleration
[ 2186.822] (II) NVIDIA(0): Support for GLX with the Damage and Composite X extensions is
[ 2186.822] (II) NVIDIA(0): enabled.
[ 2188.363] (II) NVIDIA(0): NVIDIA GPU GeForce 6600 GT (NV43) at PCI:1:0:0 (GPU-0)
[ 2188.363] (--) NVIDIA(0): Memory: 131072 kBytes
[ 2188.363] (--) NVIDIA(0): VideoBIOS: 05.43.02.39.00
[ 2188.363] (II) NVIDIA(0): Detected AGP rate: 8X
[ 2188.363] (--) NVIDIA(0): Interlaced video modes are supported on this GPU
[ 2188.363] (--) NVIDIA(0): Connected display device(s) on GeForce 6600 GT at PCI:1:0:0:
[ 2188.363] (--) NVIDIA(0): Arnos Instruments F-417 (CRT-0)
[ 2188.363] (--) NVIDIA(0): ViewSonic VX2433wm (DFP-0)
[ 2188.363] (--) NVIDIA(0): Arnos Instruments F-417 (CRT-0): 400.0 MHz maximum pixel
[ 2188.363] (--) NVIDIA(0): clock
[ 2188.363] (--) NVIDIA(0): ViewSonic VX2433wm (DFP-0): 155.0 MHz maximum pixel clock
[ 2188.363] (--) NVIDIA(0): ViewSonic VX2433wm (DFP-0): Internal Single Link TMDS
[ 2188.363] (**) NVIDIA(0): TwinView enabled
[ 2188.363] (II) NVIDIA(0): Display Devices found referenced in MetaMode: CRT-0, DFP-0
[ 2188.364] (II) NVIDIA(0): Assigned Display Devices: CRT-0, DFP-0
[ 2188.364] (II) NVIDIA(0): Validated modes:
[ 2188.364] (II) NVIDIA(0):
[ 2188.364] (II) NVIDIA(0): "CRT:nvidia-auto-select+1920+0,DFP:nvidia-auto-select+0+0"
[ 2188.364] (II) NVIDIA(0): Virtual screen size determined to be 3200 x 1080
[ 2188.364] (--) NVIDIA(0): DPI set to (95, 96); computed from "UseEdidDpi" X config
[ 2188.364] (--) NVIDIA(0): option
[ 2188.364] (==) NVIDIA(0): Enabling 32-bit ARGB GLX visuals.
[ 2188.364] (--) Depth 24 pixmap format is 32 bpp
[ 2188.365] (II) NVIDIA(0): Initialized AGP GART.
[ 2188.373] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[ 2188.373] (II) NVIDIA(0): may not be running or the "AcpidSocketPath" X
[ 2188.373] (II) NVIDIA(0): configuration option may not be set correctly. When the
[ 2188.373] (II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will
[ 2188.373] (II) NVIDIA(0): try to use it to receive ACPI event notifications. For
[ 2188.373] (II) NVIDIA(0): details, please see the "ConnectToAcpid" and
[ 2188.373] (II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
[ 2188.373] (II) NVIDIA(0): Config Options in the README.
[ 2188.373] (II) NVIDIA(0): Setting mode
[ 2188.373] (II) NVIDIA(0): "CRT:nvidia-auto-select+1920+0,DFP:nvidia-auto-select+0+0"
[ 2188.613] (II) Loading extension NV-GLX
[ 2188.657] (II) NVIDIA(0): Initialized OpenGL Acceleration
[ 2188.659] (==) NVIDIA(0): Disabling shared memory pixmaps
[ 2188.659] (II) NVIDIA(0): Initialized X Rendering Acceleration
[ 2188.659] (==) NVIDIA(0): Backing store disabled
[ 2188.659] (==) NVIDIA(0): Silken mouse enabled
[ 2188.660] (**) NVIDIA(0): DPMS enabled
[ 2188.660] (II) Loading extension NV-CONTROL
[ 2188.661] (II) Loading extension XINERAMA
[ 2188.661] (II) Loading sub module "dri2"
[ 2188.661] (II) LoadModule: "dri2"
[ 2188.661] (II) Reloading /usr/lib/xorg/modules/extensions/libdri2.so
[ 2188.661] (II) NVIDIA(0): [DRI2] Setup complete
[ 2188.661] (II) NVIDIA(0): [DRI2] VDPAU driver: nvidia
[ 2188.661] (==) RandR enabled
[ 2188.661] (II) Initializing built-in extension Generic Event Extension
[ 2188.661] (II) Initializing built-in extension SHAPE
[ 2188.661] (II) Initializing built-in extension MIT-SHM
[ 2188.661] (II) Initializing built-in extension XInputExtension
[ 2188.661] (II) Initializing built-in extension XTEST
[ 2188.661] (II) Initializing built-in extension BIG-REQUESTS
[ 2188.661] (II) Initializing built-in extension SYNC
[ 2188.661] (II) Initializing built-in extension XKEYBOARD
[ 2188.661] (II) Initializing built-in extension XC-MISC
[ 2188.661] (II) Initializing built-in extension SECURITY
[ 2188.661] (II) Initializing built-in extension XINERAMA
[ 2188.661] (II) Initializing built-in extension XFIXES
[ 2188.661] (II) Initializing built-in extension RENDER
[ 2188.661] (II) Initializing built-in extension RANDR
[ 2188.661] (II) Initializing built-in extension COMPOSITE
[ 2188.661] (II) Initializing built-in extension DAMAGE
[ 2188.664] (II) Initializing extension GLX
[ 2188.842] (II) config/udev: Adding input device Power Button (/dev/input/event2)
[ 2188.842] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 2188.842] (II) LoadModule: "evdev"
[ 2188.842] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 2188.842] (II) Module evdev: vendor="X.Org Foundation"
[ 2188.842] compiled for 1.8.0, module version = 2.4.0
[ 2188.842] Module class: X.Org XInput Driver
[ 2188.842] ABI class: X.Org XInput driver, version 9.0
[ 2188.842] (**) Power Button: always reports core events
[ 2188.842] (**) Power Button: Device: "/dev/input/event2"
[ 2188.842] (II) Power Button: Found keys
[ 2188.842] (II) Power Button: Configuring as keyboard
[ 2188.842] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD)
[ 2188.842] (**) Option "xkb_rules" "evdev"
[ 2188.843] (**) Option "xkb_model" "evdev"
[ 2188.843] (**) Option "xkb_layout" "us"
[ 2188.883] (II) config/udev: Adding input device Power Button (/dev/input/event1)
[ 2188.883] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 2188.883] (**) Power Button: always reports core events
[ 2188.883] (**) Power Button: Device: "/dev/input/event1"
[ 2188.883] (II) Power Button: Found keys
[ 2188.883] (II) Power Button: Configuring as keyboard
[ 2188.883] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD)
[ 2188.883] (**) Option "xkb_rules" "evdev"
[ 2188.883] (**) Option "xkb_model" "evdev"
[ 2188.883] (**) Option "xkb_layout" "us"
[ 2188.887] (II) config/udev: Adding input device Logitech USB-PS/2 Optical Mouse (/dev/input/event3)
[ 2188.887] (**) Logitech USB-PS/2 Optical Mouse: Applying InputClass "evdev pointer catchall"
[ 2188.887] (**) Logitech USB-PS/2 Optical Mouse: always reports core events
[ 2188.887] (**) Logitech USB-PS/2 Optical Mouse: Device: "/dev/input/event3"
[ 2188.887] (II) Logitech USB-PS/2 Optical Mouse: Found 3 mouse buttons
[ 2188.887] (II) Logitech USB-PS/2 Optical Mouse: Found scroll wheel(s)
[ 2188.887] (II) Logitech USB-PS/2 Optical Mouse: Found relative axes
[ 2188.887] (II) Logitech USB-PS/2 Optical Mouse: Found x and y relative axes
[ 2188.887] (II) Logitech USB-PS/2 Optical Mouse: Configuring as mouse
[ 2188.887] (**) Logitech USB-PS/2 Optical Mouse: YAxisMapping: buttons 4 and 5
[ 2188.887] (**) Logitech USB-PS/2 Optical Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 2188.887] (II) XINPUT: Adding extended input device "Logitech USB-PS/2 Optical Mouse" (type: MOUSE)
[ 2188.887] (**) Logitech USB-PS/2 Optical Mouse: (accel) keeping acceleration scheme 1
[ 2188.887] (**) Logitech USB-PS/2 Optical Mouse: (accel) acceleration profile 0
[ 2188.887] (**) Logitech USB-PS/2 Optical Mouse: (accel) acceleration factor: 2.000
[ 2188.887] (**) Logitech USB-PS/2 Optical Mouse: (accel) acceleration threshold: 4
[ 2188.887] (II) Logitech USB-PS/2 Optical Mouse: initialized for relative axes.
[ 2188.887] (II) config/udev: Adding input device Logitech USB-PS/2 Optical Mouse (/dev/input/mouse0)
[ 2188.887] (II) No input driver/identifier specified (ignoring)
[ 2188.888] (II) config/udev: Adding input device Logitech USB Multimedia Keyboard (/dev/input/event4)
[ 2188.888] (**) Logitech USB Multimedia Keyboard: Applying InputClass "evdev keyboard catchall"
[ 2188.888] (**) Logitech USB Multimedia Keyboard: always reports core events
[ 2188.888] (**) Logitech USB Multimedia Keyboard: Device: "/dev/input/event4"
[ 2188.888] (II) Logitech USB Multimedia Keyboard: Found keys
[ 2188.888] (II) Logitech USB Multimedia Keyboard: Configuring as keyboard
[ 2188.888] (II) XINPUT: Adding extended input device "Logitech USB Multimedia Keyboard" (type: KEYBOARD)
[ 2188.888] (**) Option "xkb_rules" "evdev"
[ 2188.888] (**) Option "xkb_model" "evdev"
[ 2188.888] (**) Option "xkb_layout" "us"
[ 2188.888] (II) config/udev: Adding input device Logitech USB Multimedia Keyboard (/dev/input/event5)
[ 2188.889] (**) Logitech USB Multimedia Keyboard: Applying InputClass "evdev keyboard catchall"
[ 2188.889] (**) Logitech USB Multimedia Keyboard: always reports core events
[ 2188.889] (**) Logitech USB Multimedia Keyboard: Device: "/dev/input/event5"
[ 2188.889] (II) Logitech USB Multimedia Keyboard: Found keys
[ 2188.889] (II) Logitech USB Multimedia Keyboard: Configuring as keyboard
[ 2188.889] (II) XINPUT: Adding extended input device "Logitech USB Multimedia Keyboard" (type: KEYBOARD)
[ 2188.889] (**) Option "xkb_rules" "evdev"
[ 2188.889] (**) Option "xkb_model" "evdev"
[ 2188.889] (**) Option "xkb_layout" "us"
[ 2188.891] (II) config/udev: Adding input device PC Speaker (/dev/input/event0)
[ 2188.891] (II) No input driver/identifier specified (ignoring)
Xorg.0.log important (I think):
[ 2188.888] (II) config/udev: Adding input device Logitech USB Multimedia Keyboard (/dev/input/event4)
[ 2188.888] (**) Logitech USB Multimedia Keyboard: Applying InputClass "evdev keyboard catchall"
[ 2188.888] (**) Logitech USB Multimedia Keyboard: always reports core events
[ 2188.888] (**) Logitech USB Multimedia Keyboard: Device: "/dev/input/event4"
[ 2188.888] (II) Logitech USB Multimedia Keyboard: Found keys
[ 2188.888] (II) Logitech USB Multimedia Keyboard: Configuring as keyboard
[ 2188.888] (II) XINPUT: Adding extended input device "Logitech USB Multimedia Keyboard" (type: KEYBOARD)
[ 2188.888] (**) Option "xkb_rules" "evdev"
[ 2188.888] (**) Option "xkb_model" "evdev"
[ 2188.888] (**) Option "xkb_layout" "us"
[ 2188.888] (II) config/udev: Adding input device Logitech USB Multimedia Keyboard (/dev/input/event5)
[ 2188.889] (**) Logitech USB Multimedia Keyboard: Applying InputClass "evdev keyboard catchall"
[ 2188.889] (**) Logitech USB Multimedia Keyboard: always reports core events
[ 2188.889] (**) Logitech USB Multimedia Keyboard: Device: "/dev/input/event5"
[ 2188.889] (II) Logitech USB Multimedia Keyboard: Found keys
[ 2188.889] (II) Logitech USB Multimedia Keyboard: Configuring as keyboard
[ 2188.889] (II) XINPUT: Adding extended input device "Logitech USB Multimedia Keyboard" (type: KEYBOARD)
[ 2188.889] (**) Option "xkb_rules" "evdev"
[ 2188.889] (**) Option "xkb_model" "evdev"
[ 2188.889] (**) Option "xkb_layout" "us"
Why is he adding the keyboard 2 times, and why "xkb_layout" "us"? I need hr (croatian).
My first post Sorry, for the bad english.
Last edited by b3no (2010-07-22 23:45:29)

[ 2186.780] (WW) AllowEmptyInput is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
Add this
Section "ServerFlags"
Option "AllowEmptyInput" "no"
EndSection
EditL If the above didn't help, read this http://wiki.archlinux.org/index.php/Xor … d_settings
Last edited by karol (2010-07-22 12:06:04)

Non-US keyboard layout problem with VNC

Similar Messages

Maybe you are looking for