AltGr not working properly on VMware

Multi tool use
I'm working on Fedora 18 on a VMware VM. Until yesterday my keyboard was OK, but I was trying with my boss to get the extended ASCII code activating the composed keys with so many ways (and all of them failed). The thing is that now I don't need it and while I was programming I found the next problem: I can't type the "{". (NOTE: I'm using a Spanish keyboard:
so I need the AltGr key to type "{" and "}".)
The thing is that I've undone everything I touched yesterday, BUT there was a short time that my boss touched my PC and I wasn't in front of it and today he is out so I can't ask him what did.
If I try to type "}" it works (so AltGr is working in some way), BUT if I try to type "{" then it prints a bold tile " ´ " so I can't open any loop which is a very annoying problem.
I've see some other posts like this: Alt-Gr key is not working in Ubuntu 13.10
cause I know that my boss deleted the English option that was there (by default) and left the Spanish one alone. I've set two more English options: US International with AltGr and US international with AltGr (alternative), but the result is the same (I've applied the changes and reset the computer). And now I don't know what else can I try to fix that problem, so any idea or hint would be very appreciated.
I also looked at /etc/X11/xorg.conf.d/
to see if it is as before and it seems that is OK.
This file was generated by the Anaconda installer
Section "InputClass"
Identifier "anaconda-keyboard"
MatchIsKeyboard "on"
Option "XkbLayout" "es,us"
Option "XkbVariant" "cat,"
Option "XkbOptions" "grp:alt_shift_toggle"
EndSection
keyboard vmware keyboard-layout localization fedora-18
add a comment |
I'm working on Fedora 18 on a VMware VM. Until yesterday my keyboard was OK, but I was trying with my boss to get the extended ASCII code activating the composed keys with so many ways (and all of them failed). The thing is that now I don't need it and while I was programming I found the next problem: I can't type the "{". (NOTE: I'm using a Spanish keyboard:
so I need the AltGr key to type "{" and "}".)
The thing is that I've undone everything I touched yesterday, BUT there was a short time that my boss touched my PC and I wasn't in front of it and today he is out so I can't ask him what did.
If I try to type "}" it works (so AltGr is working in some way), BUT if I try to type "{" then it prints a bold tile " ´ " so I can't open any loop which is a very annoying problem.
I've see some other posts like this: Alt-Gr key is not working in Ubuntu 13.10
cause I know that my boss deleted the English option that was there (by default) and left the Spanish one alone. I've set two more English options: US International with AltGr and US international with AltGr (alternative), but the result is the same (I've applied the changes and reset the computer). And now I don't know what else can I try to fix that problem, so any idea or hint would be very appreciated.
I also looked at /etc/X11/xorg.conf.d/
to see if it is as before and it seems that is OK.
This file was generated by the Anaconda installer
Section "InputClass"
Identifier "anaconda-keyboard"
MatchIsKeyboard "on"
Option "XkbLayout" "es,us"
Option "XkbVariant" "cat,"
Option "XkbOptions" "grp:alt_shift_toggle"
EndSection
keyboard vmware keyboard-layout localization fedora-18
add a comment |
I'm working on Fedora 18 on a VMware VM. Until yesterday my keyboard was OK, but I was trying with my boss to get the extended ASCII code activating the composed keys with so many ways (and all of them failed). The thing is that now I don't need it and while I was programming I found the next problem: I can't type the "{". (NOTE: I'm using a Spanish keyboard:
so I need the AltGr key to type "{" and "}".)
The thing is that I've undone everything I touched yesterday, BUT there was a short time that my boss touched my PC and I wasn't in front of it and today he is out so I can't ask him what did.
If I try to type "}" it works (so AltGr is working in some way), BUT if I try to type "{" then it prints a bold tile " ´ " so I can't open any loop which is a very annoying problem.
I've see some other posts like this: Alt-Gr key is not working in Ubuntu 13.10
cause I know that my boss deleted the English option that was there (by default) and left the Spanish one alone. I've set two more English options: US International with AltGr and US international with AltGr (alternative), but the result is the same (I've applied the changes and reset the computer). And now I don't know what else can I try to fix that problem, so any idea or hint would be very appreciated.
I also looked at /etc/X11/xorg.conf.d/
to see if it is as before and it seems that is OK.
This file was generated by the Anaconda installer
Section "InputClass"
Identifier "anaconda-keyboard"
MatchIsKeyboard "on"
Option "XkbLayout" "es,us"
Option "XkbVariant" "cat,"
Option "XkbOptions" "grp:alt_shift_toggle"
EndSection
keyboard vmware keyboard-layout localization fedora-18
I'm working on Fedora 18 on a VMware VM. Until yesterday my keyboard was OK, but I was trying with my boss to get the extended ASCII code activating the composed keys with so many ways (and all of them failed). The thing is that now I don't need it and while I was programming I found the next problem: I can't type the "{". (NOTE: I'm using a Spanish keyboard:
so I need the AltGr key to type "{" and "}".)
The thing is that I've undone everything I touched yesterday, BUT there was a short time that my boss touched my PC and I wasn't in front of it and today he is out so I can't ask him what did.
If I try to type "}" it works (so AltGr is working in some way), BUT if I try to type "{" then it prints a bold tile " ´ " so I can't open any loop which is a very annoying problem.
I've see some other posts like this: Alt-Gr key is not working in Ubuntu 13.10
cause I know that my boss deleted the English option that was there (by default) and left the Spanish one alone. I've set two more English options: US International with AltGr and US international with AltGr (alternative), but the result is the same (I've applied the changes and reset the computer). And now I don't know what else can I try to fix that problem, so any idea or hint would be very appreciated.
I also looked at /etc/X11/xorg.conf.d/
to see if it is as before and it seems that is OK.
This file was generated by the Anaconda installer
Section "InputClass"
Identifier "anaconda-keyboard"
MatchIsKeyboard "on"
Option "XkbLayout" "es,us"
Option "XkbVariant" "cat,"
Option "XkbOptions" "grp:alt_shift_toggle"
EndSection
keyboard vmware keyboard-layout localization fedora-18
keyboard vmware keyboard-layout localization fedora-18
edited Feb 5 at 12:19
Scott
15.9k113990
15.9k113990
asked Jun 23 '15 at 9:51


Megasa3Megasa3
1062
1062
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f931405%2faltgr-not-working-properly-on-vmware%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f931405%2faltgr-not-working-properly-on-vmware%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
UfHquEqB S,bYh8wT8tneJo,btD4URNP6JgBN4 fcU IZcCg0NQqOAElld1yB91,FOQHTTLELdg1,Jf,cTrl0,XXXvbfwKE